SIG Reports 2024-09-19

Acquisitions SIG

App Interaction SIG

Consortia SIG

Documentation Working Group

ERM SIG

Metadata Management

• Magda presented the results of the Bulk edit UAT.
  • Bulk edit of FOLIO Instance’s notes UAT showed that the existing implementation is confusing as most participants attempted update instance with source MARC using Instance fields option. Proposed new UI options contain the label "Instances with source FOLIO" and "Instances with source MARC". What that acutally means is ~"Instance with source FOLIO = instance with no underlying SRS", because the instance source is just a string field and can contain any value other than FOLIO. Magda will work more on this.
  • With Ramsons the Bulk edit app supports editing instance administrative notes and all instance notes types.
  • The Bulk edit roadmap has been shared with the SIG.
• UXPROD-4746: Sort, filter, and mapping changes for Dates
  
  • Decission that the instance fields publicationPeriod.start and publicationPeriod.end will be removed from the instance schema. These fields are not surfaced in the UI and will be replaced by new fields:
    • Date type: Controlled list, included in MARC mapping rules
    • Date 1: Text box - allows for four characters (alphanumeric) - no validation on UI; validation on backend and if data does not pass validation, it should be considered as 0000
    • Date 2: Text box - allows for four characters (alphanumeric) - no validation on backend and if data does not pass validation, it should be considered as 0000
  • The dates will be displayed in the Inventory result list in a new column calles Date after the Publishers column.
  • A new filter for the date data is added to the search & sort pane.
• UIIN-2889: Spaces entered in Call number field are not saved; trailing and leading spaces are removed and the call number will be found in Browse. White spaces before the call number is also removed. Only impacts newly entered data, not existing/legacy data. Existing data has to be fixed separately.
• Version History / Change Tracker
  
  • We're currently in the process of collecting use cases. This has to be done by September the latest.
  • Kimie has created mockups (WIP) how the change tracker would look like in Inventory.
  • The SIG agrees that the list of fields is good.
  • For privacy reasons there has to be a setting to turn off what user made changes.
  • We also talked about how long to store version logs or how many version logs should be stored. There has not been overall agreement but a feeling that having the latest 10-15 versions or 2-3 years of logs available in the UI would be okay for the beginning. Fetching older logs via the API could be okay for some users, but not the general librarian.
  • We also have to define what an update is that triggers an entry in the history. We added a section on the wiki page for what should not be considered an update, e.g. checking out an item.

Open Access SIG

Reporting SIG

Resource Access

User Management