Skip to content

Conversation

@gregoriopellegrino
Copy link
Contributor

The note was written by Christopher Carr

@clapierre clapierre requested a review from chrcarr June 5, 2025 14:02
@clapierre
Copy link
Collaborator

In light of recent changes @gautierchomel @madeleinerothberg should we adjust this aside note? At te very least I think we need to change the name of the column which is changing from "MARC21" to "“MARC Fields”

Thoughts?

@gautierchomel
Copy link
Collaborator

I think we should say MARC21.

@madeleinerothberg
Copy link
Collaborator

We may need other text edits as well since we are enhancing the Information and Resources sections but streamlining the crosswalk column for MARC21.


<aside class="note">
<p>Best practices and procedures for recording accessibility metadata in MARC21 using the Schema.org Accessibility Properties for Discoverability Vocabulary (sapdv) and ONIX are still under development. Please be aware that future work may result in changes to the crosswalk, though it is expected such changes will be minimal and backwards compatible.</p>
<p>The MARC21 columns provide recommendations for recording accessibility metadata for digital publications in MARC21. These recommendations can be used by cataloguing agencies who acquire accessibility metadata directly from an ePUB, through ONIX, or who will catalogue manually, using the sapdv vocabulary and free text notes. Crosswalks can be made from the EPUB and ONIX columns to the MARC21 column where equivalents are available. This document will be updated to reflect any future changes to the MARC21 341 - Accessibility Content and 532 - Accessibility Note fields.</p>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This paragraph has to be updated to reflect that MARC 21 mapping gives information about the field to use, not the vocabulary to use in those fields.

@madeleinerothberg
Copy link
Collaborator

The first paragraph seems fine to me and the third paragraph could be removed ("Onix under development"). Currently the second paragraph reads:
The MARC21 columns provide recommendations for recording accessibility metadata for digital publications in MARC21. These recommendations can be used by cataloguing agencies who acquire accessibility metadata directly from an ePUB, through ONIX, or who will catalogue manually, using the sapdv vocabulary and free text notes. Crosswalks can be made from the EPUB and ONIX columns to the MARC21 column where equivalents are available. This document will be updated to reflect any future changes to the MARC21 341 - Accessibility Content and 532 - Accessibility Note fields.

Suggested replacement paragraph but please review and suggest improvements:
This crosswalk provides recommendations for MARC21 fields appropriate for each accessibility metadata term. Each organization will use their current cataloging practice to determine the correct syntax for expressing the metadata in that field.

@chrcarr
Copy link
Collaborator

chrcarr commented Aug 27, 2025

Cataloguing agencies can determine the correct syntax for expressing the metadata in that field.

@madeleinerothberg
Copy link
Collaborator

Cataloguing agencies can determine the correct syntax for expressing the metadata in that field.

Thank you -- that's helpful.

MARC 21 not presented everywhere with a space.
@clapierre clapierre merged commit 570dfd1 into main Sep 4, 2025
1 check passed
@clapierre clapierre deleted the note-marc branch September 4, 2025 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants