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.
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 context diagram
Map: Barcode is required for request and check out mod-user-import needs externalSystemId and username to not duplicate users (checks) User anonymisation Brooks: if only display, no problem but search and sort 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 FOLIO needs this as well Brooks: pub-sub like func for users (more pubsub approach) Theo: could we meet this needs with having a atron and librarian schema; 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
.png?version=1&modificationDate=1619770661000&cacheVersion=1&api=v2&width=1000&height=693)