...
Discussion items
| Time | Item | Who | Notes | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30min | Managing department field name changes in automated user import | Patty | If the department numerical ID stays the same, but the name changes, what do we want to happen? Do we want locking of the old name and creation of a new department with ID? Or just keep the ID and update the name? Duke uses department designation to determine the user's status as, say, a medical student, law faculty, etc. Cornell mostly uses department information for reporting purposes; patron status is matched to patron group (undergrad, grad, alum, staff, faculty etc) as imported via the enterprise directory feed. FOLIO only allows one patron group per user, so to deal with people in multiple groups, U of Alabama creates new combined patron groups. | ||||||||||||||||||||||||
Handling department update errors -
| Patty | Requirement to be able to change a user from one department to another, or from one patron group to another, and protect the change from being updated by the nightly load. References:
|