| 60 min | mod-user-import module documentation | KhalilahNatalia Zaitseva | - Walk through of changes to documentation for user records
- mod-user-import API demonstration (https://s3.amazonaws.com/foliodocs/api/mod-user-import/p/import.html)
- preferred first name
- custom field
- request preferences (connected to circulation-storage)
- "Hold Shelf" always true; "Delivery" true requires Default Delivery Address specified
- validation for requestPreference based on requirement logic
- departments
- department list
- can include multiple departments in array
- must be indicated by UUID; skips invalid IDs → Requirement: must accept plaintext entry AND new departments should be created as they appear in feed
- mapping issue: plaintext name vs. UUID when translating data from campus identity provider
- import issue: silent "failing" for non-valid field entries (patron group, address type ID, patron group ID)
- import issue: should import support "create" function for newly represented department names
- should "bad data" kill the entire job? write to an error job?
- different levels of errors needed for minor errors like a mismatched department name versus a mismatched patron group
- should errors be handled in the UI (as needed at the Circulation desk) or at the API level (must contact Systems or external identity provider)?
- what level of database maintenance are libraries willing to accept to clean up unused departments?
- Discussion of requirements and acceptance will continue in Slack (possible topic for meeting on )
|