-
Recent posts
Recent comments
- Kathy Glennan on Expanding RDA 6.29.1.3, Laws Governing More Than One Jurisdiction
- Amanda Ros on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary
- Amanda Ros on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary
- Amanda Ros on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary
- Amanda Ros on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary
Archives
Comment policy
Only current CC:DA members and liaisons are authorized to comment on posts. Others who wish to contribute to CC:DA's discussions are invited to provide input by contacting the Chair, a member of the Committee, or their appropriate liaison.
New CC:DA members and liaisons will be assigned an account for the CC:DA Blog during the month of their initial appointment. For assistance with an account contact the CC:DA Webmaster.
All first-time comments on this site are moderated. We ask that all comments be relevant to the post to which they are directed and maintain professional courtesy.
All categories
Tag cloud
agenda ALA2012 ALA2013 ALA2014 ALA2015 ALA2016 ALA proposal Annual 2012 Annual 2013 Annual 2014 Annual 2015 Behrens Bourassa British Library Canadian Committee on Cataloguing Chair's report corporate bodies Dunsire European Regional Representative Glennan Iseminger JSC JSC rep Lapka Leonard Library of Congress McGrath Midwinter 2012 Midwinter 2013 Midwinter 2014 Midwinter 2016 minutes music Music Working Group (JSC) Myers OLAC PCC Rendall Reser response Robare Rolla RSC Shrader SnyderLinks
Seems sensible.
I note a typo in the clean copy; it should be e-ISBN, not e-ISSN.
This accords with current cataloging practice. Nonetheless, on my first reading it felt wonky and circular. Presumably, in a fully linked bibliographic data-verse, this kind of information would be passed through from the data associated with the related manifestation.
I agree with this.
I think part of the dissonance I perceive is that I’m getting used to thinking of identifiers as actionable URIs rather than text strings. I could wish for more precise terminology to distinguish those two concepts.
I agree as well.
As I undertand it 6JSC/TechnicalWG/6 Recommendation 1 attempts to address the problem Tina mentions. But I agree with John, too.
OK by me. Thanks to Matt for catching that typo!
This seems reasonable.
Would you ever want to record an identifier for a related manifestation that is *not* of the same expression?
From Adam Schiff:
I see two issues with this proposal that could be raised:
1. It doesn’t explain why a qualifier isn’t used after the identifier: e.g. would this format be equally valid in the example?:
978-3-11-023500-5 (e-book)
2. Does it work with other instructions that are in 2.15? For example the third example in 2.15.1.7 shows print and electronic ISBNs being recorded with qualifiers. Does this example need to be changed in any way? Deleted?