The following fields on accessiblty was added to MARC21 in November, 2018.
In order for the above fields to be actually used among libraries, RDA (Resource Description and Access) ‘s support is required. This is because RDA is the major standard for cataloging for libraries.
Current status of RDA
RDA does not support 341and 532 fields both of which were added in 2018 yet because RDA”s offical latest version is 2017 version. With regards ot accessiblity, RDA 2017 version provides accessibility content as content element of Expression as follows.This element corresponds 500 fields (General Note) and 546 fields (Language Note) of MARC21 as of now.
7.14 Accessibility Content
7.14.1 Basic Instructions on Recording Accessibility Content
7.14.1.1 Scope
accessibility content: An indication of content that provides alternative sensory modes to perceive the primary content of an expression.
Accessibility content includes accessible labels, audio description, captioning, image description, sign language, and subtitles. Accessibility content does not include subtitles in a language different from the spoken content.
7.14.1.2 Sources of Information
Take information on an accessibility content from any source.
7.14.1.3 Recording Accessibility Content
Record information about an accessibility content if the information is evident from the manifestation or is readily available from another source.
EXAMPLE
Closed captioning in German
Includes subtitles
Open signed in American Sign language
Discussion of changing RDA and accessibility content
RDA Steering Committee (RSC) is developing new RDA in 3R Project. And, RDA updates after 2017 version are continuing as beta version at RDA Toolkit beta site. RSC plans to switch over from the beta site to official RDA status at December 15, 2020.
Changing accessibility content was also the topic of discussion among RSC. RSC decided the policy of changing ‘accessibility content’ as belows in January 2020 meeting (see also “210 RDA Content Elements Follow-up” of PDF MINUTES OF JANUARY 2020 MEETING in detail).
accessibility content
Recommendation 2.2: Redefine Expression: accessibility content as a Manifestation shortcut
Shortcut:
- Manifestation: expression manifested [for an expression that is aggregated]
- Expression: category of expression [for a category of accessibility content taken from an unspecified VES]
Definition: An indication of the kinds of expression that provide alternative sensory modes to perceive the main expressions that are embodied by an augmentation aggregate.
Scope note: Accessibility content includes accessible labels, an audio description, captioning, image descriptions, sign language, and subtitles. Accessibility content does not include subtitles in a language different from the spoken content.
This is an element sub-type of Manifestation: supplementary content.
This shortcut allows information about accessibility of content and carrier to be recorded for a manifestation.
Future modified version of accessibility content
We can see the modified version of accessibility content according to the above policy at paper for discussion at the January 2020 “Appendices: Clean versions of new and amended Toolkit pages” as belows.
This version describes the element as a shortcut that uses an unspecified VES. This is consistent with other elements that are shortcuts or that use an unspecified VES. The content is complete.
accessibility content
Definition and scope
An indication of the kinds of expression that provide alternative sensory modes to perceive the main expressions that are embodied by an augmentation aggregate. Accessibility content includes accessible labels, an audio description, captioning, image descriptions, sign language, and subtitles. Accessibility content does not include subtitles in a language different from the spoken content.
Prerecording
This element applies to a manifestation that is an aggregate.
This element is a shortcut for the following chain of relationships:
- Manifestation: expression manifested for an expression that is aggregated
- Expression: category of expression for a kind of accessibility content
The element does not identify any expression that is aggregated.
For general guidance on shortcuts, see Guidance: Introduction to RDA. Relationship shortcutsRecording
Recording an unstructured description
OPTION: Record an uncontrolled term or a term that is transcribed from a source of information.
OPTION : Record details or other unstructured information.
For general guidance on unstructured descriptions, see Guidance: Recording methods. Recording an unstructured description.Recording a structured description
OPTION: Record a term from a suitable vocabulary encoding scheme.
OPTION: Record a vocabulary encoding scheme that is used as a source of information for a term. For general guidance, see Guidance: Data provenance. Recording a source of metadata.
CONDITION: None of the terms in a vocabulary encoding scheme is appropriate or sufficiently specific.
OPTION : Record a suitable uncontrolled term as an unstructured description.
Record a term from a suitable vocabulary encoding scheme. Appendix 5 For general guidance on structured descriptions, see Guidance: Recording methods. Recording a structured description.Recording an identifier
OPTION: Record an identifier or notation for a term from a suitable vocabulary encoding scheme.
OPTION: Record a vocabulary encoding scheme that is used as a source of information for an identifier. For general guidance, see Guidance: Data provenance. Recording a source of metadata.
For general guidance on identifiers, see Guidance: Recording methods. Recording an identifier.Recording an IRI
OPTION: Record an IRI for a term or concept as a real-world object selected from a suitable vocabulary encoding scheme.
For general guidance on IRIs, see Guidance: Recording methods. Recording an IRI.Related elements
Main points of modification is as follows:
- Redfined as a Manifestation element.
- “Recording a structured description”,”Recording an identifier” and “Recording an IRI” which say “This recording method is not applicable to this element.” at current RDA Toolkit beta are changed to applicable items.
Is Change 2 supposed that accessibility content support ‘341’ fields of MARC21 ?
Future plans of accessibility content
From PDF MINUTES OF JANUARY 2020 MEETING .
ACTION ITEM: Dunsire will adjust the RDA text in the CMS to accommodate these recommendations in time for the next Toolkit release.