Page Comparison

No meeting December 22 and 29 2022

MM SIG Release Note & Other Highlights

I will be out of town and cannot attend this week. The PC agenda items are mostly updates from:

• Bugfest
• Update on the Evaluation Process for new FOLIO modules
• Prioritization and Roadmap working group- need some more members-volunteers
• Update on cross council meeting and onboarding working group

Instance	Instance

Holdings	Item Current display	UX proposal

Decision: 

• Add "mark as" subheading to the item actions button
• Don't add "actions" subheading, as this is a duplicate to the button label
• Remove "actions" subheading in the Inventory result list action button as well
• see

  Jira Legacy
  server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-2263

Slide deck

Owen PO for Serials Management development, funded by GBV and Duke (presentation done in PC and Acq SIG previously)

Scope (not an exhaustive list)

• LC definition of serials. FOLIO context - anything with Order Type = Ongoing
• Orders and Invoices
• Predictions
• Receiving/Check-in
• Claims
• Tracking/Reminders
• Transfers/Binding etc.

See diagram of current FOLIO functionality and where the new Serials functionality may fit in

First release aim

• Subscription based serials with predictable pieces and invoicing/payment separate to piece receipt
  • To support this - serial record that describes and links to existing order and existing inventory
    • Add new period to serial
    • Add new prediction pattern
    • Generate predicted pieces
    • Ensure predicted pieces can be received (either in Receiving App or separate)

Out of scope

• Non-subscription/non-predictable based serials publications, e.g. standing orders/mono series/loose leafs
• Automated claiming
• Collection management

Current work

• Talking with sponsors, Orders PO, and dev team
• JIRA projects - MODSER and UISER
• Lots of decisions still, discussions with SIGs, not trying to reinvent and want to make best use of existing functionality

Discussion

• Will there be an Item Status for claimed?
  • Unknown currently, not sure we would always have an item at point of claiming
  • Different libraries operating differently, e.g. Duke vs. GBV
  • Questions around Item States - no PO currently
• Receiving and public display - are you considering the relationship between this and the Receiving History in Inventory? Currently functionality is a bit off because of the way display to public functions.
  • Options per Owen
    • Make use of current Receiving App functionality and make use of predictions in existing context, then we can ALL focus on how this interacts with Inventory
    • This might not be possible, so other option is something outside of Receiving App
  • From Chat: What if receiving history for serials was passed through OAI-PMH for discovery display?  Item records could be for issues fully bound into bound items? for fully received issues
  • Ultimately if you receive an item it may or may not create Inventory and if it does, it all works as it currently does
    • Subtleties around bindery and predicting etc.
• Predictions - nothing currently in system around this and noone else working on it
  • Need to support all varieties of patterns, e.g. built-in or MARC holdings stored
• Hoping for feedback on use of volume, enum, chron etc.
  • Receiving app options vs. Inventory options and trying to understand how these would be used a part of predictions
  • Chat: Would Inventory Item records have to have Year, Caption separated into 2 separate fields for ease of data mapping?
  • Some modeling done in snapshot on ABA Journal, includes enum and chron, no year,caption (combined in inventory) info
  • Owen: seems like captions are included in enumeration, e.g. v. and no.
    • Fills patron needs?
    • Could it be formulated differently?
  • Chat: Ann-Marie: Keep in mind the more libraries that adopt FOLIO and that create FOLIO holdings, the more challenging to change the data elements of the FOLIO holdings record and revise libraries' existing data, especially if one field is broken into multiple fields.'
  • Chat: Rita: In Germany we have an orientation on RDA rather than MARC 21 when it comes to caption and numeration
  • See chat for suggestions on resources to reference
  • Owen: if we create items on basis of predictions, where would the readable statements go?
  • Need to carefully consider the interactions between receiving and inventory in regards to these fields
  • How is year, caption being used?
    • Many not using. Not being passed through OAI/PMH
    • What do these exist for?
      • Critical for Chalmers, Charlotte can grab examples
  • SIG will gather real life examples of these for wiki in Tips and Tricks
• Owen will follow up in Slack with further questions
  • Insert here