Skip to end of banner
Go to start of banner

SIG Reports 2024-09-19

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Reports should include:

  • Discussion of specific development areas. Including Jira issues for both features and bugs is helpful.
  • Work related to the FOLIO Roadmap or work that occurred that is not well-represented on the FOLIO roadmap.
  • Information about demos, user discussions, or future functionality for FOLIO.
  • Spins-ups or wind-downs of specific subgroups or working groups in a particular area.
  • Ideas or issues that came up feel outside the scope of the SIG but need commenting.

When you click on Submit Request, this will create a new wiki page that will need to be published.


SIG NAMESIG Convenor(s)PC LiaisonReport and Include any relevant JIRA issuesAny updates to the roadmap?Submit a Request for PC

Acquisitions SIG

Dung-Lan Chen Kristin Martin 

App Interaction SIG

Martina Schildt & Tara BarnettMartina Schildt 

Consortia SIG

Lucy Harrison

Documentation Working Group

Katharina Jung Martina Tumulla The Documentation Working Group discussed documentation workflow questions and Jira use for tracking documentation issues. In addition the WOLFcon presentation "Best practice - FOLIO Documentation in institutions" was discussed and prepared.

ERM SIG



Implementers SIG

Charlotte Whitt

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

Björn Muschall Alexis Manheim

Reporting SIG

Jennifer Eustis 

Resource Access

Jana Freytag 

SIG Conveners

Martina Schildt Meetings are held twice a year. Next meeting will take place in March 2024.

System Operations and Management SIG

Ingolf Kuss Ingolf Kuss 

Support SIG



User Management

Maura Byrne Maura Byrne 

Workflow SIG

Ian Walls Lisa McColl

Dormant SIGDormant Since
Accessibility

 

Privacy SIG

 

Public Library SIG


  • No labels