SIG Report 2024-05-23

Acquisitions SIG

@Dung-Lan Chen 

@Kristin Martin 

Acquisitions SIG meetings agenda and notes wiki here for more details -

• Dennis and Joe presented Quesneslia Release Highlights

• Discussed Implementers Topics #120-123

• Had conversations/discussions about toasts and inconsistency in Acq modules (April 26th & May 10th)

• Reviewed Ramson UAT schedule (Joe Reimers)

• Discussed Inventory Item record Make item material type optional (ini.  App Interaction SIG)

• Clean and prioritize feature backlog & discussed when more information is needed (Joe Reimers)

• Planned the first FYRO session this time around to take place on Friday, May 24th, at 9 am Eastern

App Interaction SIG

@Martina Schildt 

@Martina Schildt 

App Interaction SIG discussed ways to create links between Inventory and Agreements:

1. Charlotte Whitt and Sara Colglazier presented mock-ups on how to create relationships between Holdings in Inventory and Agreements, Agreements Lines and Licenses in Agreements and Licenses.

   1. https://folio-org.atlassian.net/browse/UXPROD-4785

2. As another option the group discussed the use of custom fields in Inventory.

   1. https://folio-org.atlassian.net/browse/UXPROD-2211

No

Consortia SIG

@Noah Brubaker  & @Corrie Hutchinson (Unlicensed) 

@Paul Moeller 

Still working on a survey to send out to the community regarding consortial support in FOLIO.  @Dennis Bridges presented the features planned for ECS in the Ramsons release.

Documentation Working Group

@Former user (Deleted) 

@Martina Tumulla 

The Documentation Working group welcomed new members Emily (Inventory), Alissa (data import/export) and Lisa (ERM comparisons together with Nadja). In addition there will be new writers for Serials and Local KB Admin.

The documentation release for Quesnelia is worked on and will include the FOLIO terminology page in the about FOLIO section.

The WG discussed possible feedback to Jenn Colt’s requests around apps and applications and to archive older documentation releases on a section of https://docs.folio.org/docs/.

The Documentation WG talked about the “install FOLIO” sections on https://docs.folio.org/docs/ and if there is a better place for this information, which has a different audience than all other content on the website. There would be links from https://docs.folio.org/docs/ to refer to the sysops information.

ERM SIG

@Martina Tumulla & @Martina Schildt 

@Martina Tumulla & @Martina Schildt 

ERM SIG:

• Martina Tumulla stepped down as convener of ERM SIG.

• Owen Stephens gave a development update and presented on Quesnelia functionality across ERM apps.

Agreements Local KB subgroup (Martina Schildt):

• Owen Stephens gave a development update

• The subgroup discussed an implementers topic and related requirements: "Import only local packages for my institution/curator group in the Local KB"

eHoldings subgroup (Zorian Sasyk):

In our last meeting we discussed a user story idea brought by Zorian concerning the display of additional Agreement metadata fields in the eHoldings Package record view: https://folio-org.atlassian.net/browse/UIEH-1418
Led to larger discussion of how to improve Agreements/Agreement Lines/eHoldings integration and display
In addition, two other user stories discussed by the group possible are candidates for inclusion in Ramsons:
Clarify button language in eHoldings app for "Unassigning" as Agreement Line https://folio-org.atlassian.net/browse/UIEH-1420
Insert clarifying info text for Add and New buttons in eHoldings package/title view Agreement section https://folio-org.atlassian.net/browse/UIEH-1424

-

Implementers SIG

@Thomas Trutt 

Members of implementers were encouraged to attend the architectural change discussions offered by TC. We discussed concerns and reflected on these meetings during our 4-23 meeting. 

Metadata Management

@Felix Hemme  & @Raegan Wiechert 

@Jennifer Eustis & @Charlotte Whitt 

MM discussed null barcodes in items destined for remote storage. Currently, transferring items to remote storage with null barcodes does create a feedback loop within mod-remote-storage. The proposal is to prevent sending an item to remote storage if it has no barcode. No major concerns have been identified and the work has been scheduled for Ramsons.

We've also revisited multiple graphical representations. Christine presented some slides to confirm SME's requirements. She will now talk with the developers and will come back to MM with any questions, concerns or ideas they might have.

Christine also discussed the need for a place of publication facet in Inventory. The discussion lead to the result that MM is in favor for creating indexes for publisher and place of publication instead of a facet, but a facet to filter on date (of publication, distribution etc). 

A discussion took place about change tracker requirements of the FOLIO community and also the LoC. Khalilah presented on the development plans (https://folio-org.atlassian.net/browse/UXPROD-4125 and https://folio-org.atlassian.net/browse/UXPROD-910).

Open Access SIG

@Björn Muschall 

@Owen Stephens 

Reporting SIG

@Sharon Markus  & @Scott Perry 

@Jennifer Eustis 

Current topics for the Reporting SIG are:

• preparing for the WolfCon 2024 conference

• managing changes to derived tables as institutions move to FOLIO Poppy

• restructuring LDP and Metadb support with a new product owner and the transition of the principal software developer to new projects

• BibControl presentation with FOLIO data for reporting 

Resource Access

@Jana Freytag  and @Cornelia Awenius 

@Jana Freytag 

• Users / UI / Check-out - Costum fields display - Pronouns field display

• Remote storage allows null barcodes: https://folio-org.atlassian.net/browse/MODRS-121

• Fee/fine from previous loan is blocked from actions when item is checked out again and claimed returned

• Reading Room Circulation --> Smallgroup

SIG Conveners

@Martina Schildt 

@Martina Schildt & @Jana Freytag 

The SIG conveners held one of their two meetings per year.

• The group prepared the next meeting at WOLFcon in London.

• SIG conveners agreed on a way to replace the meeting calender: https://folio-org.atlassian.net/wiki/x/PgAVCw.

• There were discussions around "How to get committed volunteers". It was agreed that one action is to strengthen the SIG section on the following wiki page: FOLIO Governance Model | FOLIOGovernanceModel Membership.

System Operations and Management SIG

@Ingolf Kuss 

@Ingolf Kuss 

• SysOps SIG and Documentation SIG propose to move Installation Documentation from docs.folio.org to github.com/folio-org/folio-install. That latter site needs to be restructured.

• SysOps SIG to discuss Eureka Deployment model on WolfCon; invited quests. FOLIO Architectural PoC Review was the main topic in all meetings this month.

Support SIG

@Anya & @Debra Howell 

@Charlotte Whitt 

User Management

@Maura Byrne 

@Maura Byrne 

Leipzig is funding a Number Generator project. Initially it will focus on five kinds of numbers:

• Vendor Code

• User Barcode

• Accession Number

• Call Number

• Item Barcode

The plan is to link documentation directly in the UI.

The SIG contributed to a spreadsheet describing what we needed in custom fields (use cases, accordion vs. visible at checkout). Work is being done on "cleaning up" the appearance of custom fields, as well as the Extended Information section of the User record. It will be available in the Sunflower release.

There is work being done on an app called "Reading Room," and we discussed printing library cards as the "Registration" part of the app.

Pronouns are being developed as a separate field in the User record. It will be available in the Sunflower release.

Workflow SIG

@Ian Walls 

@Owen Stephens