Page Comparison

• When working with customers, it is difficult to identify all the necessary user data that the various apps require. It's hard to know whats required or not.
• Questions:
  • What user data is needed by which apps?
  • Which fields are required by FOLIO modules?
  • How things stick together?
• Theodor presents his (draft) context diagram (copy from Slack)

Map: 

• Barcode is required for request and check out
• mod-user-import needs externalSystemId and username to not duplicate users

• Also discussion with regard to user anonymisation
• Brooks:

• it's no problem to display data cross-app but for search and sort data must be stored in the database of respective apps
  -
  • • problem of updates
  -
  • • Patty: useful to document/list user data stored in other apps? maybe to make aware?
  -
  • • other
  parts of
  • • domains in FOLIO needs this as well
    • Brooks: pub-sub like func for users (more pubsub approach)
    • Theo:
  could
  • • Could we meet
  this
  • • these needs with having
  a atron
  • • separate patron and librarian/staff schema
  ; in
  • • ? In order to understand what ist needed to FOLIO to work?
    • Björn: could more documentation in the schema help?
      • Brooks: requirements comes from the respective apps and not from users, difficult to document

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

• Maura spoke with her library SysOps, which were very interested in this topic because it relates to them
• Björn: to add the PIN field to the user record is already in Leipig sprint (backend only):

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODUSERS-254

  • after implementation, Leipzig asks in #folio-implementer whether libraries using/want to use PIN auth are okay with changing SIP implementation
  • if okay, Leipzig contacts Magda for changig SIP auth to PIN field
• Maura: should we also bring user deletion (problems, fragments etc.) to Sysops?
  • Sysops as architects and for platform wide issues
  • Phil offers to bring topics to SysOps (if wanted)

• postponed
• Brooks mentioned last Thursday’s (22 April) RA meeting (watch recording) where they discussed the permissions management app.

Proposal:

• proposal was also discussed in PC 29/04/21 (see minutes)