/
2018-03-14 User Management Meeting Notes

2018-03-14 User Management Meeting Notes

Mar 23, 2018

Date

Zoom info:

OLE4 Meetings is inviting you to a scheduled Zoom meeting.
 
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/325274656
 
Or iPhone one-tap :
    US: +16699006833,,325274656#  or +14086380968,,325274656# Or Telephone:
    Dial(for higher quality, dial a number based on your current location):
        US: +1 669 900 6833  or +1 408 638 0968  or +1 646 876 9923
    Meeting ID: 325 274 656
    International numbers available: https://zoom.us/zoomconference?m=RS1sJiYhuELjv0esrFhItAzPR4vp8cwN
 
 

Attendees

Goals

Discussion items

TimeItemWhoNotes
Administration
Chris Manly
  • Note taker for this meeting - Chris
  • Meeting time check in - is this still a good time? Yes, but Chris will check with the mailing list since attendance was small.
 

Review and kickoff Users UAT

 Khalilah Gambrell

 
  • The purpose of the UAT is to get feedback from the folks who will use the product/service/system.  For this UAT, we'll want a small group of 5-7 participants who can give geedback by Wed, March 28
  • There is a spreadsheet of scenarios to be tested and give feedback.
  • The testing is all done through a particular instance of the app (linked in the spreadsheet).
  • We start ASAP, in hopes of having feedback by the 28th.
  • We need to identify folks from various institutions who work with users on a regular basis.
  • Khalilah Gambrell sent a note to UM-SIG with the details
  • Participants duplicate the spreadsheet, add their initials, and fill in their copy with their responses.
  • There is a list of current known issues listed on the spreadsheet.

Validate username field as required decision & passwords

Last discussed in August, 2017: 2017-08-09 User Management Meeting Notes

  • We concluded that both username and password should not be required fields
  • There is an issue of consistency of what is listed as required (the users API, the bulk user import API, and the UI all differ).

Additional Unique identifier fields

We currently have the external system ID and the Barcode. We discussed examples of possible additional fields:

  • Chalmers has a PIN
  • Special collections may need to store drivers license and/or passport numbers (has security implications)
  • Separate IDM for Duke in China
  • Folks from other universities
  • Question: Do we need multiple match points for a single patron?
  • Chicago has a student ID that is separate from the institutional ID.
  • Could we make the external System ID field a multiple field, like addreses?

Discuss possible future topics


Action items

  •