Problem statement

Currently, requests for multivolume series and continuing resources can only be made at the item level. Patrons should be able to request a volume or issue of a series or title without having to specify or select a particular copy. This is highly valued by public libraries and consortia that serve both public and academic libraries.

Related information

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

• https://docs.folio.org/docs/access/check-out/checkout/

• https://www.loc.gov/marc/bibliographic/bd490.html

• https://s3.amazonaws.com/foliodocs/api/mod-inventory-storage/p/instance-storage.html

• https://s3.amazonaws.com/foliodocs/api/mod-inventory-storage/p/item-storage.html

Requirements and Expectations

Stakeholders

• PO(s) - Tim Auger, Steph Buck

• Dev team - Volaris

• .

Architectural design

Analysis and considerations

Assumptions

1. No item without barcode support

2. No free-text field support

Questions

1. What fields can we use for series identification?
   Item contains the following fields: copyNumber, volume, enumeration, chronology, numberOfPieces, descriptionOfPieces
   The instance already contains series fields with value and authority

2. Does FOLIO need support for the functionality being analyzed in

   1. single tenant,

   2. ECS OpenRS DCB,

   3. ECS with mod-tlr enabled?

3. Should it work via Locate as well?

4. Which series cataloging approach from the picture below do we need to follow?

5. LC will handle the representation of any uninventoried items on our side (likely using stub item records)
   Does this mean that LC will use Folio's generated item records or generate its own items for data importing?

Open