Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Item

Presenter

Notes

Announcements


UAT results

Christine Schultz-Richert & Ryan Taylor

  • Results of UAT: Pub place index, related titles navigation, updates to 035 normalization, and bulk edit of FOLIO instance notes

  • Results of Q call number browse UAT

Data import sorts protected fields out of order after update

Ryan Taylor

https://folio-org.atlassian.net/browse/MODDICORE-358 will be discussed during the DI WG on Wednesday, August 7th and Ryan will provide updates to the MM SIG today.

Bulk Update UAT results

Jennifer Eustis

Lref gdrive file
urlhttps://drive.google.com/drive/folders/1welOcpdl1GwTuaivPavCA2oBgoTXnL3b

Lref gdrive file
urlhttps://docs.google.com/presentation/d/1KHgGB0guiUTskJRLHkEkzUjniKFB__UU/edit#slide=id.p5

Lref gdrive file
urlhttps://docs.google.com/spreadsheets/d/1sVHMyKNnr4SQmPyCkV30eAlecqajcn1l/edit?gid=1421128647#gid=1421128647

PC updates

Charlotte Whitt

2024-08-08 Product Council Agenda & Meeting Notes

Announcements:

Developer Advocate Update:

Ideas for tracking, and maintaining the FOLIO Roadmap:

BELA (Bulk Edit and Lists App)

Jennifer Eustis

2024-08-06 BELA Meeting Notes

We reviewed upcoming features for Ramsons and followed up on the work on editing MARC instances.

We also covered the UAT feedback. The results can be found in this Google drive:

Lref gdrive file
urlhttps://drive.google.com/drive/folders/1welOcpdl1GwTuaivPavCA2oBgoTXnL3b
.

Data Import Working Group

Jennifer Eustis

2024-8-7 Data Import Subgroup meeting

The working group worked on 2 Jira issues.

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODDICORE-358

The proposal agreed on is that the protected field of the existing record should be placed either ahead or behind the same field number in the incoming record. Ryan is bringing this proposal to the development team.

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODDATAIMP-879

The proposal agreed on is If an existing and incoming record has duplicate fields for any repeatable fields, the system should dedupe. If an existing and incoming record don't have duplicate fields for any repeatable fields, then the system should not dedupe. Ryan will bring this to the team.

quickMARC Subgroup update

Raegan Wiechert

...