2022-09-07 Meeting notes

Date

Attendees

Goals

  • Post WOLFcon discussion
  • Updates on JIRA tickets
    • UIU-2651 - Users app allows creation of broken user record
    • MODUSERS-212 - Make "addresstypeid" property required for addresses
    • MODUSERS-320 - User with invalid date value will break /users/expire/timer API
    • UIU-2669 - HTTP 500 Internal Server Error occurs when saving a new User record with empty

Discussion items

TimeItemWhoNotes
5 minNote takerMatt

UIU-2651 and MODUSERS-320 (related issue)
  • if you add a date instead of using the date picker, you can add an invalid date
  • should be format YYYY-MM-DD (easier to recognize error in date format than error in date data)
    • tested:  07-06-2022 and 0000=01-01 (created the record but did not populate dates)
    • issue wasn't noticed because many institutions use a patron loading program instead of manually entering users
    • should a popup appear when date is added or should it appear when a record is accessed through the UI?
      • Patty - error should pop up when user is created with malformed date

UIU-2669 and MODUSERS-212 (related issue)
  • if you don't select an address type but you add an address through the UI, an error pops up
  • addresstypeid is required by the front end but not the back end (MOD USER IMPORT accepts null addresstypeid)
  • this should be on the agenda for future meeting (it is a breaking change)
  • MOD USER IMPORT should use validation rules (e.g. must have an addresstypeid selected)
    • other apps do have some types of validation
  • should we have a story about user validation?  
    • we need to define what is the required data/format for users for both UI creation and MOD USER IMPORT
  • also, some are adding users directly to MOD USERS instead of using MOD USER IMPORT (different issue)

UIPFU-58
  • Middle name is not searched in keyword search for users

Action items

  •