Date

??25 Sep 2023 

Housekeeping

• Convener and notes: Martina Schildt 
• Next meeting: 04 Oct 2023 

Discussion items

Minutes

Review UX/UI for buttons 

...

UI options for "Save & ..."

...

Responsive text fields

...

Free text boxes are quite narrow in display and can then be extended. Sometimes the extendability may not be as obvious as needed. It would be helpful to have the free text boxes be responsive.

Example use case:

Inventory holdings: The URI box in the holdings record is really small. It does expand, but I can imagine someone not noticing a URL was really long and only editing part of it and mangling it all up.

...

1. Demo on possible solution for parts of container use case line 7 | Sara Colglazier
2. Demo on package handling in Agreements app | Owen Stephens

Minutes

Sara demos possible solutions for the use cases listed in line 7

Martina to separate those use cases

• Ability to manage a set of records for resources. It would be great if information could be managed at the container level such as:
  • for eResources, an end date when these eResources won't be available.
    • Sara: we add a code in MARC records (035 9) - it comes up as an identifier → system control number
    • it consist of a code and end dates (e.g. MHebSPR22* → for MH ebooks that end in Spring 2022)
    • a local ID could be created if this shoukd be a separate ID
    • the identifier is searchable
    • overlays by OCLC records may happen → then the ID would be gone
    • rather than adding the package titles in orders, they are batch loaded to Inventory → the URL to the Inventory search for all relevant resources can then be linked
    • the URL fro the Inventory search can be added to supplementary documents in Agreements
    • rather than an own record, we need to be able to manage the data
  • For eResources, ability to manage the prefix, link text, and public note for holdings records at the container level
    • reference data
    • when in INventory → Electronic access → relationship : resource → would be good to have a drop down to choose a link text
    • could be set up in settings
    • Laura in chat: I wonder if the URL prefix management might also be a Lists and/or Bulk Edit thing? (rather than a need for a Container record per se)
      that's a really interesting idea, Sara, of expanding the Electronic access block even more -- it's a good time to talk about this, as we're needing to make other changes to that data already (to accommodate additions to the MARC standard)
  • For any resources, ability to add information such as donor or gift history and bookplate information.
    • we should talk to Dennis, there is work going on related to these requirements
• it seems we do not necessarily need container records, but the possibility to add data that is additionally needed
• Sara: we have added item administrative notes - is also avalable for holdings
• Laura: information is not needed in Inventory, but we need to be able to get there from Inventory

Package handling in Agreements app

• in local KB: concept of package and title in a package (=Package Content Item or PCI)
• each PCI has access start and access end date (this is not coverage!) - date when title joins or leaves a package
• even if a journal ceased publication, a library may still have access to the title in the package
• → a package can change over time, packages are not static
• Packages in eHoldings: similar concept of packages
• packages and titles can be selected or unselected, but no dates associated with titles in package
• Agreements and Agreement lines
• Agreement lines (AGL) can be for:
  • a package of resources in local KB or in eHoldings
  • a particular title in local KB or eHoldings
  • not linked to a resource (use a textual description)
• each AGL has an active from and to date
• challenges fro agreements
  • active from/to dates not clear enough
  • lack of integration between AGL active/inactive dates and eHoldings selected statuses
  • differences in package content management (local KB vs. eHoldings)
  • POLs are linked to AGLs
  • Orders and Agreements cannot be linked
  • Agreements is focussed on ERM use cases
  • no integration between Agreements and Inventory - come back to in next meeting
    • better integration between electronic and physical
  • capture history over a long time - this is what we had expected from containers and we is still needed in FOLIO
  • Sara: system has no capability for large amounts of data
  • many areas are lacking memory as well as scalability (FOLIO s trying to get rid of scaling issues)

Chat

18:03:00 From Martina Schildt | VZG To Everyone:
    Agenda for today: AppInt:2023-09-25 Meeting notes: Container records
18:24:19 From Laura Daniels To Everyone:
    I wonder if the URL prefix management might also be a Lists and/or Bulk Edit thing? (rather than a need for a Container record per se)
18:25:50 From Laura Daniels To Everyone:
    that's a really interesting idea, Sara, of expanding the Electronic access block even more -- it's a good time to talk about this, as we're needing to make other changes to that data already (to accommodate additions to the MARC standard)
18:39:27 From Laura Daniels To Everyone:
    E-books behave a lot like serials in many ways
18:53:21 From Laura Daniels To Everyone:
    apologies, I need to drop off a little early today -- thank you so much Sara & Owen for these demos
18:53:31 From Martina Schildt | VZG To Everyone:
    Reacted to "apologies, I need to..." with 👋
18:53:36 From Martina Schildt | VZG To Everyone:
    Reacted to "apologies, I need to..." with 🙏

Attendees

Action items