Meeting URL https://zoom.us/j/488543197
Date 12 Aug 2020
Attendees Agenda A discussion of new documentation in mod-user-import module, led by Natalia Zaitseva from Khalilah Gambrell 's team. A quick catch-up of JIRA tickets related to user record fields. Discussion items Time Item Who Notes 5 min Assign note taker Catherine 60 min mod-user-import module documentation
Natalia Zaitseva Walk through of changes to documentation for user recordsmod-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 departmentsdepartment 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 19 Aug 2020 )
Action items