Page Comparison

...

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

Chat

Attendees

Action items