2018-07-11 User Management Meeting Notes
Date
Jul 11, 2018
Attendees
@Chris Manly
@Khalilah Gambrell
Douglas Hahn
@Julian Ladisch
@Michelle Suranofsky
@Kimie Kester
@Todd Wallwork
@Maura Byrne
Goals
Discussion items
Time | Item | Who | Notes |
|---|---|---|---|
Identifier fields | Khalilah | Confirm with Michelle from Lehigh regarding additional identifier fields. For the gap analysis, Lehigh stated additional identifier fields were required to go-live. I want to make sure that custom fields will address their needs or if we need these additional identifier fields. We discussed, and confirmed that Lehigh's identifier needs will be met by the current set of IDs in FOLIO. | |
| Password UI screen requirements |
|
Change Password UI screen requirement reviewhttps://drive.google.com/drive/folders/1PhWtSifsTExqSziRoi-Z3_AIV7A3519O |
| Data Migration - additional user fields needed. |
| Discuss data migration – additional user fields needed. Is this list of fields to add complete? Who are the Early Implementer contacts, I should contact to get a final list? |
> Who are the Early Implementer contacts, I should contact to get a final list?
I believe Auburn University's needs on user fields are similar to the other listed universities. To be precise:
Banner ID (links to external people/hr system)
Barcode (as scanned from cards)
Auburn GID (global user/pass used across our systems)
Possibly we could also use a field to store VoyagerID (key ID field inside Voyager) if we plan to run parallel systems during migration. But that field can be inferred from the others.