2022-06-02 CDL Sub-group Meeting Notes

Owned by Andrea Loigman
Last updated: Jun 16, 2022 by Jana Freytag
2 min read

Date


Zoom

https://zoom.us/j/337279319 (pw: folio-lsp)

Attendees



Discussion Items

TimeItemWhoDescriptionGoals/Info/notes
2minAdministrivia



Note taker:   Peter



Defining record requirements

This is the MVP requirements Document



An outside system needs to communicate with FOLIO to trigger the sequestration of an item.  Do we need a representation of the digital item in FOLIO to be the target of an action to sequester the physical item?  Do we retain the record of the digital item after the loan is complete?  Complication: dealing with serials and multivolume sets, for which we need to take into account what is happening at the item level when making the digital loan.  Also, a digital file that encompasses all five volumes of a 5-volume set; where is the reference to that stored?

One way to implement this is to use inheritance of the digital item's identifier at the holdings and items levels.


Next steps


Meeting Notes

  • Suggestion - ongoing metadata management person for this group

New notes:

Representation of digital files in inventory - needs to be able to occur at instance, item and/or holding level.  Possibility of an ID number to represent digital file that would be placed in inventory.  If at the item or holding level, ID would be inherited by the 'lower' components.  If at the item level (e.g. multivolume, special collections) it would remain there.  - Sebastian will take this idea to NISO group.

If you have 2 physical copies and permanently sequester one as a CDL surrogate, could you set a preference for CDL from that item since it wouldn't require extra work?  Could you set preference for loaning files from select locations (e.g. off-site) so that physical sequestration doesn't need to happen?

Circ rule application - at what level?  is it in the repository where files are stored? in FOLIO?  What about renewals and recalls? Behavior of Overdrive vs. Hoopla.

______________________________________________________________________________________________

Further requirements and scope see also last meetings