2019-10-23 User Management Meeting notes

Meeting URL

https://zoom.us/j/488543197

Date

Oct 23, 2019

Attendees

• @(OLD ACCOUNT) Erin Nettifee

• @Maura Byrne

• @patty.wanninger

• @Uschi Klute Klute

• @Philip Robinson

• @Jana Freytag

• @Michelle Suranofsky

• @Stefanie Sußmann

• @Edd Merkel

• @Thomas Paige

Goals

Notetaker: MS

1. We will wrap up the discussion about statistical fields: https://discuss.folio.org/t/additional-fields-vs-custom-fields-for-statistical-fields-and-codes/

   1. How are statistical fields tracked and audited?

   2. Would the existing Statistical Fields structure coded into the Inventory module work for any of us?

   3. What kind of statistics do we all need to keep?  Would it make sense to have a communal solution for those statistics that we all keep?

2. Patty can give us an update on things she has been working on, such as

   1. UXPROD-1295 - Users App: Add additional fields to user records,

   2. UIU-1255 - Changing user status to inactive requires expiration date change but no error message appears to tell you that

   3. And any other things she’s been doing.

3. We should discuss Patron Notes.

If we have additional time:

• Multiple Phone numbers https://folio-org.atlassian.net/browse/UIU-254 (Erin)

• multiple e-mail addresses - There is no JIRA for this? (Uschi)

• More topics from the Open Topics list

Notes

• User Notes on the checkout page:

  • Emma   will write a feature for patrons notes on the checkout page.  We are not sure when it will be implemented

• Statistical fields:

  • Anonymized loans: 

    • Concern is when you anonymize a loan the information that is user identifiable is removed.  We need the statistical category (and a 2nd more specific statistical category) to remain with the loan record after it is anonymized for reporting purposes.

      • This is a really typical use case.  Many libraries will use it.

    • We discussed the possibility of tags filling this need.  Concerns about this:

      • no permission control for tags in MVP

      • patron tags will not be available on anonymized loans

    • We looked at a FOLIO item record (after it was loaned, checked in and anonymized) to try to determine what information stays with an anonymized loan

    • Requirements we decided on:

      • anonymized loans need to retain statistical information about the user

        • patron group

        • statistical information (which we currently do not have)

      • If there are multiple statistical codes for a patron, they all have to be linked to the loan

      • Patty will reach out to Emma about the user story for anonymizing loans/patron info on anonymized loans

        • there is a jira: https://folio-org.atlassian.net/browse/UXPROD-2062

        • Patty will also ask about item loan history.  We wondered what is going on with that feature?

  • Patty demo'd screen shots of what the department and external system ids (3 of them) will look like in the user interface

    • The first of the three external IDs will default to 'external system id'.  It will show up on the UI whether we use it or not.  We can rename all of them.

    • Department name is a repeatable field

  • Patty will ask about the status of the card sorting exercise

  • During our discussion a concern about the size of the fields on the user edit screen surfaced

    • often values are cut off

    • another example is values in drop down boxes that start with the same value and differentiate at the end...hard to see the actual value with smaller fields

    • Patty will work with Edward Merkel to create screen shots.  Patty will report this as a bug.

  • Khalilah Gambrell is reviewing our existing tickets...getting them ready for the dev teams.

  • Patty cannot attend next weeks meeting.

Action items from last meetings

10-23-2019 Action Items

Open Topics