Page Comparison

Acquisitions SIG

Acquisitions SIG meetings agenda/notes wiki link

• Kim Wilianen presented Michigan State Univ. Library's workflow using Data Import to create orders with MARC records for various types of orders - (Nov. 21st meeting)
• Discussed Implementers Topics # 110 - #112 - (Nov. 28th meeting)
• Product Owner Dennis Bridges reviewed new development re: prediction pattern for serials and where to enter data such as vol. issue, year for journals in relation to Serials App deployment in Quesnelia release (Serials Publication Patterns wiki) & currently working to form a sub-group focusing on discussing alignment of Item>piece>serial checkin data, Dennis reached out to POs after the SIG meeting and received feedback they are open to Friday meeting slot to meet/discuss.  Dennis will prepare a post to be shared with different SIGs and in Slack channels and he will work with Owen to decide on the meeting time (alternating Fridays that are not Acq SIG scheduled Friday meetings)- (Dec. 5th & Dec. 12th meeting)
• Product Owner Joe Reimers announced in Dec. 8th meeting two Acquisitions UATs, first one "Organizations - Banking information" UAT runs thru Friday (Dec. 15th); second one, "Organizations - Donor information" UAT to start Jan. 8 (Joe will share the details when available)
• German Acquisitions community feature request presentation (further integration of "e-mail" in the integration details in the Organization app)  (Dec. 8th meeting)
• Acquisitions SIG discussed the round-robins questions PC proposed for SIG Reports meeting today (Dec. 12th meeting)
• Convener is coordinating with Owen Stephens to plan for a more detailed demo of serials prediction pattern in Serials App for Quesnelia release

App Interaction SIG

Consortia SIG

Documentation Working Group

The Documentation WG discussed

• the upcoming Poppy documentation release
• external links from https://docs.folio.org/docs/ to the Information and User Guides for FOLIO Apps pages in the FOLIO wiki
• integration of Terminology document content to the page About FOLIO
• glossary on documentation website (will be discussed further)

ERM SIG

• ERM SIG continued to discuss "Adding column customisation options to multi-column lists in Agreements".
• Feedback was collected via this form as well as during the meetings.

Metadata Management

• Demonstrations of new features in Poppy
• Discussion the future of entity management (both as a group and with PC)
• Discussion of MM and does some of the structure need to change
• Discussion of how LCCNs should be handled in search (UIIN-2245)

Working groups:

Bulk Edit has joined with List App to form 1 group called Bela. The slack channel has been renamed. Bulk Edits and Lists Apps Home - BELA.

Data Import has asked for feedback on these issues:

UXPROD-2742: MARC-MARC matching enhancements: Narrowing multiple matches & Bug work

UIDATIMP-1521: Not able to use system generated Match profiles

MODSOURMAN-1094: The number of created invoices is displayed when all invoices have errors with invoice lines

Open Access SIG

    
New release for OA App includes:

for mod-oa:

• Upgraded to Grails 5 (including Hibernate 5.6.x for Poppy)
• Implemented undertow servlet and enable scheduling annotation to application.groovy
• MODOA-57 Fixed error on attempting to render a charge
• MODOA-51 Added primary keys to database Schema (for reporting in metadb)
• web-toolkit-ce to 8.1.4
• dependencies for commons-io, spring-webmvc and kafka-clients Refs MODOA-53/54/55

for ui-oa:

• Upgraded ui-oa to React v18
• Added okapi interface dependency on new erm interface 6.0
• UIOA-220 Updated dependencies to their react v18-/stripes v9-compatible versions
• UIOA-219 Fixed Incorrect id for formatted message in charge form
• UIOA-218 BREAKING bump react-intl to v6.4.4

Discussed improved Funder and Publisher information

Privacy SIG

Reporting SIG

FOLIO Data Model updates needed

• Reporting SIG needs to know about data model changes before they are released (Change Management)
• When we cannot anticipate changes, reports break because they are looking for data fields that have been moved/deleted/updated

Resource Access

• Gap list working session continuation (we decided to continue with next topics from our list, since it is a good way of enriching the features and make them development ready)
• Break our meeting for the topic of automatic renewals https://issues.folio.org/browse/UXPROD-2375
• WOLFCon 23 Topic: Talk about helper features. Talk about the Checklist Feature that was thought up by the Open Access SIG. Do we have use cases for this in 'our' Apps? The other is the history tracking feature that was just added to invoices could be used in other areas.
• Last meeting of the year will be on the display of bound withs in the circ apps
• We are planning to have another SIG survey to improve our work  for the next year

User Management

UM SIG has been filled in on discussions within Crossapp SIG, and we've shared our opinions on them.  The short version:

1. We are in favor of Crossapp SIG's proposal to have responsive text in each module
2. We are wary of including RTF or HTML in user loads.

Also, we've been revisiting a couple of issues that have been deprioritized.  Specifically, adding a pronoun field in the User record. Maura has been tasked with setting up a meeting with RA-SIG to discuss.

There has also been some discussion of whether we should advocate for validating user records.  There are different required fields in the API and the UI, and the loads via API can't enforce required fields in the UI.  This has been a concern for some time for UM SIG, but we've let it sit.  We'd be interested to know if others have similar data validation concerns.