Versions Compared

Old Version 3

changes.mady.by.user Björn Muschall

Saved on

compared with

New Version Current

changes.mady.by.user Björn Muschall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

 


Attendees

...

  • Theodor Tolstoy will give a presentation discussing what user data is needed by which apps.  There is a diagram, and more context, in the Slack channel.
  • Update on UXPROD-1811.
  • Discuss requirements of a proposed Permissions app.

...

TimeItemWhoNotes
5 minNote takerBjörn
30 minWhat user data is needed by which apps?Theodor Tolsto1221pxy
  • 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
(checks)
User
  • Also discussion with regard to user anonymisation
  • Brooks:
if only display,
  • 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
    5 min

    Update on UXPROD-1811

    PIN field

    		Maura Byrne
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUXPROD-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
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODUSERS-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)
    20 minDiscuss requirements of a proposed Permissions appMaura Byrne
    • postponed
    • Brooks mentioned last Thursday’s (22 April) RA meeting (watch recording) where they discussed the permissions management app.

    Proposal (restricted): https://docs.google.com/document/d/1FPErp93UQufL4CajapcYoDXXm2NT9-gmRJzOI54Kcrc/edit


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