Import Users Instructions

[caseywatts]

When importing users there are a few questions that come up. We should include more details on what the uploaded spreadsheet requires. We can be strict in the code as long as we're specific on the view page.

To get to this screen for testing:
Go to Reservations => Users. Click the "Import Users" button.

Some instructions we might include:

1. The format must be csv, you can choose this in Excel under "Save As...".
2. The first row (headers) have to be exactly as listed on the page. (can we copy-paste into excel?)
3. It must have the login field present (or it must have all of them even if they're blank?)
4. If "update existing users' data" is checked then ___. If not then ___
5. Will blanks overwrite data? What about " "?

[orenyk]

This all sounds reasonable, it shouldn’t be too hard to update the view with clearer instructions. The same thing should probably be done for the Equipment Import page (see #494).

[orenyk]

This should also implement the changes from #301 which related to the instructions on the Import Users page. I'm closing the older issue and "merging" it into this one.

[orenyk]

I've updated the import user view, fixing the error identified in #301 and incorporating the suggestions above. I'm not 100% about the order of columns mattering but I can test that this week. I'm also pretty sure that all fields of a user will be overwritten if the checkbox is checked, but I can test that as well.

[mnquintana]

This looks implemented.

[orenyk]

No changes were actually made... reopening but this should basically be done already.

[dgoerger]

@orenyk, you have a branch for this. Did you want to try rebasing this, or else re-branching off development? The changes look fairly minor / cosmetic, and should not be hard to push over current development (if there's a merge conflict on your April branch). :)

[orenyk]

I haven't looked back to see what was going on. If someone wants to just jump on this, checkout my branch, and rebase / finish up that would be great. Thanks!

[dgoerger]

Per modular code and #2, we should make sure the instructions are clear which fields cannot be empty in the CSV if LDAP service does not exist.

[orenyk]

I'd say we should have a basic set of instructions on the actual page and link to a page on the github.io site with more extensive instructions about import, etc. This should also include information about the LDAP dependency.

[orenyk]

Assuming that #897 is merged in, we should revamp the documentation for importing both users and equipment simultaneously.

[orenyk]

The current documentation is decent and we're short on time, bumping to the Wish List.

[caseywatts]

@orenyk check this out!
https://github.com/BrewhouseTeam/csv-importer

(Maybe also related to #1271 and #899 ?)

[orenyk]

@caseywatts This looks amazing, thanks for pointing it out!