2025-12-09 Acquisitions Meeting notes - Synchronizing item and piece fields, Bulk edit for orders and order lines

Ann Crowley

Joe Reimers

Sara Colglazier

Daniel Huang

Julie Stauffer

Scott Perry

Dennis Bridges

Kimberly Pamplin

Shay Swindlehurst

Dung-Lan Chen

Kimberly Wiljanen

Stephanie Larrison

Dwayne Swigert

Kristin Martin

Susanne Gill

Heather McMillan

Lisa Maybury

Suzette Caneda

Heiko Schorde

Lucinda Williams

Sylvia Hamann

Jackie Magagnosc

Masayo Uchiyama

Tim Nelson

Jean Pajerek

Okay Okonkwo

Jessica Scheel

Peter Sbrzesny

Housekeeping

Heather McMillan

• Folio serials subgroup meeting this Friday (Dec.12)

• Our next meeting is Friday: Dec.19th. I would like to cancel the meetings scheduled for Tuesday, Dec.23. and Friday Jan.3.

  • Agreement from group for cancelling.

• First meeting of 2026 will be Tuesday Jan.6

https://folio-org.atlassian.net/browse/MODORDSTOR-494

Dennis Bridges

• Whether to synchronize just Barcode or also the Call number and accession number.

• Does it simplify things to just say these data points will be identical in those records at all times?

  • Yes as long as it is clear which fields we’re talking about. Should be clear to everyone always which fields are in sync and which fields can be different.

  • Barcode is identical in both piece & item.

  • Susanne Gill (BVB) 12:12 PM
    If I'm not mistaken some libraries put Barcodes on the pieces. ( I'm Always struggling with Item and piece)

• ~:15 demonstration

Open

• Currently changes to item barcode will not go back the other way to the piece.

• Why do people go back to the piece at that point in time?

  • Relevant for serials - spend a lot of time in receiving

• Display Summary, Copy number, Enumeration, and Chronology are also item record fields.

• At this point in time, when things are bound in FOLIO, a new item record is created.

  • If you had item records for the pieces, they are suppressed and disconnected. Still traceable, but effectively decoupled.

• May not be of benefit to synchronize other fields at this time.

• For now focus on Barcode, Call Number, and Accession Number.

• Maintain distinction between piece details and item details. Item details will fully synchronize with item record and piece details or not.

• Feel free to make additional comments on the Jira story.
  
  

:33

Bulk editing orders and order lines

Joe Reimers

• UAT for sequence number next week. Watch Slack Channel for details.

• https://folio-org.atlassian.net/browse/UXPROD-868

• https://folio-org.atlassian.net/browse/UXPROD-4014

• https://folio-org.atlassian.net/browse/UXPROD-5631

• https://folio-org.atlassian.net/browse/UIBULKED-728

• Given that cancelling an order is simply a flavor of closing an order, planning to use closing an order because you can always cancel through there.

• :38 - Display of columns within bulk edit app

• https://folio-org.atlassian.net/browse/UIBULKED-735

• UUIDs not necessary as defaults, take up a lot of space in the columns.

• Will keep the UUIDs available though, since they are the best match points for everything.

• Added Notes, Subscription, Renewal, Renewal date, Review interval

Will come back to: https://folio-org.atlassian.net/browse/UIBULKED-736

Julie Stauffer 12:53 PM
Apologies if this has already been addressed, but does a check happen before a batch update occurs? Using an example from the current discussion, if an order is already closed with a specific note, will the bulk edit replace with bulk edit note, or does the already closed order be excluded from the update?

• There are checks.

• Gives warnings, though they do not block you from running it. Logs will also tell you what failed.

Kristin Martin 12:56 PM
Will the Order and the Order Line information appear together?

• Will have to do them separately.

Dung-Lan Chen 12:58 PM
Can you bulk edit vendor in PO & POL at the same time? Right now we have to change in both places separately.

• Not planned for the first go through.