2025-02-19

5 mins

Note taker

• Catherinne Tuohy helpfully took notes today.

Version history for Users as it’s implemented in Orders

UXPROD-5171

Bjorn Muschall

• Version history has already been implemented in organizations and orders.  There has been a wish to develop version history in Users.

• It would be good to have the same kind of version history across all apps, but it’s not certain that is being discussed.

• There is one request from GBV which wants not to allow a library to exclude user info.

  • This will be in consideration as we progress.

  • The source (The user making the change) would not be stored. 

• Version history might be good for assigning permissions if one is asked to add permissions to a person who left, and had their permissions removed.   

• What personal information included/excluded?The Jira ticket refers to staff information in ticket. Other info about user would be kept. 

• How many change records should be kept?

  • There is no limit in the apps that currently have this version history.

  • The feature does not seem to be very scalable.  Maybe a maximum number of version records would be good to have.

  • We should discuss how long the version history should be.

• The version history needs to be deleted when a user is deleted, to meet GDPR user data deletion requirements. 

  • Khalilah shared mockups for Inventory record version history

    • One is a modal that lists changes, the other presents an additional pane on the right.

    • The extra pane matches version history in other apps, and we can request that changed fields be highlighted in the record.

    • There is still some debate about the modal, and more input would be welcomed.

• Is it possible to bring versions together? So you can see the previous info and the changed info? Unlikely. in other apps where version history exists, those apps retain the entire record.

• Amelia will talk with people working in Inventory.

• There should be special permissions for viewing version history in Users.

• What kinds of changes will count as updates to the user record specifically?

  • Do permissions/service points count?

  • Do proxy users count?

  • Blocks?

  • Service points and permissions might cause extra work.

  • What about the circulation data?

    • That appears on the user record, but isn’t really part of the user record. That could create a lot of updates.

    • We should not include that, because it’s kept in the Circulation Log.

15 mins

Prioritizing UM Jira tickets

Amelia Sutton

• Priorities we have for Trillium development for UM.  Right now we are still trying to confirm which Library of Congress features will be developed.  One will be their patron pic capture from within UM app.

• We have set what we will otherwise work on yet.  We have discussed custom features-cleanup steps:

  • https://folio-org.atlassian.net/browse/UXPROD-4723

  • https://folio-org.atlassian.net/browse/UXPROD-4735

  • https://folio-org.atlassian.net/browse/UXPROD-5028

  • https://folio-org.atlassian.net/browse/UXPROD-2491

• Are these still our priority?

• GBV libraries will never use photos.

• For orders custom field project it’s a bit hard to reuse them from other apps.  It would be great to have these tickets solved.

• Björn will send these tickets to Amelia.

• We want these custom fields to be used by others. Some tickets affect UI some do not. 

• Display of checkout custom fields only one fleshed out:

  • https://folio-org.atlassian.net/browse/UXPROD-4712

We can schedule a meeting time to help with this. 

Eureka

Maura

Eureka will be changing how permissions are structured and assigned. Maura will set up meetings for the second and fourth Wednesdays of each month, so we can experiment and learn about it.