Page Comparison

...

•  Patty will create a feature to add validation to the (required) e-mail field
  (see also

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key LIBAPP-94

  - but these proposals do not appear to have been implemented.)
•  Patty will file a bug or feature to have Expiration date and Status actually decoupled from each other. (also refering to

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIU-1255

  )
•  Patty creates a JIRA issue: The field Birth date is not validated, you can enter a date in the future.
•  Patty suggests that Theodor Tolstoy presents the Chalmers SSO solution to us at one of the next meetings. Patty will reach out to Theodor to see about scheduling a time.
•  Patty will file a feature to work on password rules. It's difficult to find out which character combinations are allowed → It's not userfriendly. Proposal: make the password strength configurable
•  

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-242

  Patty will ask the CAP plan group for feedback. Erin will work with Patty to write a user story for a "thin thread" v.1 of this - a flag or checkbox on record, that if checked, would cause a record to not be updated.
•  Patty will write a feature about Improving Search in the Users App so that it can be ranked. - It's UXPROD-2092
•  Patty will work on a story for preferred name/preferred pronouns

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1790

  ("New feature")
•  Patty will write a Feature Request for the enhancement os User search (for exact match like "Li")
•  Patty will create a feature request for deleting user data.
•  Patty will ask Magda (the reporter on 

  Jira Legacy
  server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1811

  ) for a status.  It may not be a UM-SIG issue.

...

• Welcome to Catherine Smithfrom University of Alabama
• Barcodes
  • Do we want to keep a list of unique barcode numbers in FOLIO?
  • What should FOLIO do with a barcode  when a user loses their ID? 
  • What if the user then finds their ID? (added by Maura Byrne)
  • The user record has all the loans and fees - only the barcode would be changed on the record. You don't need to move any other loan records.
  • Catherine - in Voyager, it will save the barcodes that have been added.
  • Is there a need to retain old IDs, or discard old IDs, on the user record?
• Notes- Steffi's discussion about patron notes and whether they should pop up.
  • Steffi was not able to join us.
  • Discussion about whether blocks would function - can we get an information block? Or something on the notes with a flag?
  • Patty will reach out to Holly to get a sense of what might be possible.
• Custom Fields
  • Patty will ask Khalilah just to confirm what's being planned since the main UXPROD has no custom label.
• Overly Strict Password Rules

  • Jira Legacy
    server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODLOGIN-38

  • Were these rules actually discussed with UM SIG? No one knows.
  • References mentioned in the comments:
    • NIST - https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-63b.pdf

    • German Federal recommendations: https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Grundschutz/International/GSK_15_EL_EN_Draft.html?nn=6604828 pages 1404-1405.

    • US government password standards? Same as NIST?
  • NIST prefers long passwords, with less strict password controls
  • To-Dos:
    • Patty will talk to Khalilah
    • Can group decide on changes we would like to see?
    • Was password strength covered by the Security Audit - were there requirements there that they were trying to meet?
    • We need password strength checking through the New User process - right now, the new user creation allows any password, and the rules kick in with password change.
      • But, if you create a new user with an empty password, you can then send them a link to create a password and that does follow the rules
    • Do we know where the feature is for tenant level control / customization?
  • Simpler character requirements, the ability to use words / long phrases — perhaps with a trade off to have a longer minimum password
• Statistical Categories
  • We had discussed as part of departmental field - ended up deciding for that as a default field with its own Jira
  • Sense that we would use custom fields for these needs? 

Open Topics

...