|
DRAFT - part of the MM-SIG PARKING LOT review.
Current situation or problem: Discussion at MM-SIG 1/19/2023.
When we original designed list of data properties in the the instance record, the decision was to create a small set of data properties, and not replicate MARC format. That lead to the data property Resource type, was implemented as a not repeatable, required data element.
Changing this now will be a major breaking change, but several MM-SIG members has raised this as something we must fix.
In scope: Change Instance Resource type to be a repeatable, required data element. Resource type is the RDA Content Type (https://www.rdaregistry.info/termList/RDAContentType/#:~:text=Concepts%20for%20a%20categorization%20that,is%20intended%20to%20be%20perceived.), and this data element is repeatable in the MARC21 schema (MARC tag 336 - https://www.loc.gov/marc/bibliographic/bd336.html)
Out of scope:
Use case(s):
Use case 1: Book with audio CD (media combination):
- In cases where a book comes with an included audio CD, this is a so-called media combination. Content (336), media (337) and carrier (338) type are repeated in this case. The instance is able to store the repeated media and carrier types as multiple formats, but only the first content type is set as instance resource type. Here an example of such a MARC 21 record: https://unapi.k10plus.de/?id=gvk:ppn:1046092391&format=marcxml Note the repeated fields 336, 337, and 338. Only the first 336 (text) is stored as resource type and the second 336 (spoken word) is not included in the instance.
Use case 2; Book with music scores
- A book is published with music scores. Content (336) type is repeated and media (337) and carrier (338) type are not repeated. The instance is able to store the media and carrier types as format, but only the first content type is set as instance resource type. Here an example of such a MARC 21 record: https://unapi.k10plus.de/?id=gvk:ppn:882262882&format=marcxml Note the repeated field 336. Only the first 336 (text) is stored as resource type and the second 336 (still image) is not included in the instance.
Use case 3: Using the Filter: Resource Type to narrow ones search
- Various things in Inventory are not just one type of thing [= Resource Type = 336 RDA content]. The 336 RDA content is repeatable to account for this. In FOLIO currently, only the first 336 is utilized and shown in the Instance record and therefore only the one Resource Type can be filtered on/limited to, and so one inadvertently and most likely without realizing one is doing so, filters away records when using the filters.
For example-and this is just one type of an example that I could find relatively easily and quickly-art books often have two 336s: text and still image, as do other types of books that are heavily illustrated. Most of the time 'text' is first 336 and 'still image' second, but not always, so that when attempting to narrow ones search by using the filters, one cannot do so to find books with text that are also illustrated or include photographs that warrant the additional 336 of 'still image'. Examples, 100 plants to feed the bees, OR, Allen Ruppersberg : drawing / essay by Leslie Jones. .... Books with a 336 for 'notated music' also often include textual essays or introductions etc and so also often have a 336 of 'text'. .... Then there are the DVDs etc with booklets. Etc.
Proposed solution/stories
Links to additional info
Questions
Notes
- When/if this is developed, check with Ann-Marie Breaux about modifying the default MARC Bib-to-Inventory Instance map
- Consider if any additional effects on Data Import, Data Export, Bulk Edit, mod-inventoy-update
|