LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  January 2009

CODE4LIB January 2009

Subject:

Re: multimedia carrier vocabulary?

From:

Jonathan Rochkind <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 26 Jan 2009 17:52:33 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (173 lines)

Phew, that's very confusing, I'm going to have to read it over a couple 
times, but I think it does help, thanks for the info Diane.

Diane Hillmann wrote:
> Jonathan:
>
> I asked Gordon your question, and here's his reply:
>
>    /The RDA/ONIX framework itself 
> (http://www.collectionscanada.gc.ca/jsc/docs/5chair10.pdf) provides 
> information about how the RDA carrier terms have been derived (see 
> Appendix D in particular).  The RDA carrier type vocabulary (as in the 
> metadata registry) is an example of what the RDA/ONIX framework refers 
> to as a <base carrier category> vocabulary, which uses only three of 
> the underlying attributes identified in the ontology 
> (StorageMediumFormat, HousingFormat, IntermediationTool). The 
> vocabulary does not incorporate any of the other framework ontology 
> attributes such as EncodingFormat. As the framework says, these other 
> attributes do not have a closed, controlled set of instances which is 
> generally applicable across a wide range of communities. In order to 
> gain the best interoperability potential from the framework, RDA has 
> chosen to create separate vocabularies incorporating some or all of 
> the non-base carrier categories, rather than, say, augmenting the base 
> carrier !
> categories (the RDA carrier type vocabulary) - because these are 
> guaranteed to interoperate with base categories from non-RDA 
> communities. For example, RDA has a vocabulary for EncodingFormat (see 
> section 3.19.3.3 in Chapter 3 of the RDA final draft 
> (http://www.rdaonline.org/constituencyreview/Phase1Chp3_11_2_08.pdf); 
> examples of the terms are <DVD audio>, <DVD-R>, <DVD video>, <HD-DVD>, 
> etc.
>
>    In RDA, a full description/label for the carrier of a specific 
> resource is created from a combination of terms from several of these 
> vocabularies, by following the guidance given in Chapter 3. See the 
> examples given in Appendix M of the RDA draft 
> (http://www.rdaonline.org/constituencyreview/Phase1AppM_11_10_08.pdf).
>
>    Unfortunately, it looks as if the example for a DVD on page 26 
> might be a source of confusion. The Carrier type (videodisc) does not 
> appear in the vocabulary of Carrier types in Chapter 3 of RDA, but 
> this is probably an oversight because it is given as an example base 
> category in the RDA/ONIX framework. The Extent (2 DVD-videos) 
> presumably invokes RDA 3.4.1.5b (because videodisc is missing from the 
> carrier type vocabulary) or 3.4.15c (<DVD-video> is the term preferred 
> by the agency creating the example record - and not to be confused 
> with the Encoding format <DVD video>). The Extent in this example 
> should probably be <2 videodiscs>.
>
>    Although some of the terms in this (flawed) example may appear to 
> be redundant, in fact only Media type (video) and Carrier type 
> (videodisc) have genuine redundancy for general metadata purposes 
> (Media type is derived from Carrier type). For example, a 
> videocassette (carrier type) can also be encoded as DVD audio 
> (encoding format), while a videodisc can be encoded as HD-DVD, etc.
>
>    <Stuff> is complicated in the real world. A further source of 
> difficulty is the general conflation of carrier and content types in 
> single vocabulary terms, which is prevalent in most of the cataloguing 
> guidelines in use around the world by libraries. Many of these 
> guidelines have faced severe difficulty in recent years in clarifying 
> the difference between content and carrier, especially with 
> developments in digital technologies. The RDA/ONIX framework was 
> developed to assist metadata creators to make that clarification (to 
> improve interoperability between different metadata communities) and 
> avoid the problems in previous cataloguing rules.
>
>    For example, Jonathan asks for controlled vocabularies for 
> <multimedia> materials, but does he mean mixed content types (still 
> images, audio and text on a single carrier such as a <DVD>) or mixed 
> carrier types (DVD, CD and workbook in a <multimedia kit>), or both? 
> Whatever, RDA provides a way of creating unambiguous metadata in the 
> fairly ambiguous environment of human metadata creators and consumers.
>
>    Cheers
>
>    Gordon
>
>    Gordon Dunsire
>    Depute Director, Centre for Digital Library Research, University of 
> Strathclyde, Glasgow, Scotland/
>
> I hope this helps.
>
> Diane
>
> Jonathan Rochkind wrote:
>> Thanks Diane. That article on RDA/ONIX doesn't seem to include actual 
>> terms, the actual vocabularly. I realize there are plans to 
>> 'register' it officially, but prior to that, can the actual term list 
>> be found anywhere in human-readable format? Or does it not exist yet?
>>
>> Jonathan
>>
>> Diane I. Hillmann wrote:
>>> Hi, Jonathan,
>>>
>>> Two points as you search out a solution:
>>>
>>> 1. I agree with your assessment of the current RDA carrier 
>>> vocabulary.  You might want to look at the RDA/ONIX vocabularies 
>>> (still not registered, but there are plans to do so: 
>>> http://www.dlib.org/dlib/january07/dunsire/01dunsire.html).
>>>
>>> 2. These vocabularies are a start, not a finish: once RDA and the 
>>> vocabularies are "published" there's an intention to begin improving 
>>> them.  The first step was to get the out of the text, the second to 
>>> build on the NSDL Registry's vocabulary development tools (some 
>>> there, some not yet) to build them up in ways that will be much more 
>>> useful.
>>>
>>> Diane
>>>
>>> Jonathan Rochkind wrote:
>>>> Anyone know of any good existing controlled vocabulary for 'format' 
>>>> or 'carrier' for multimedia materials?  I'm thinking of things like 
>>>> "CD", "DVD", "digital", etc.
>>>>
>>>> The closest I can get is from RDA at 
>>>> http://metadataregistry.org/concept/list/vocabulary_id/46.html 
>>>> (thanks Karen and Diane), but it seems _really_ insufficient. As 
>>>> far as I can tell "audio disc" is used for both a CD and a vinyl 
>>>> disc, and there's nothing available there for "DVD" at all.   Or 
>>>> for "digital". Although I'm not sure what I mean by "digital", I 
>>>> guess CD and DVD are both digital, but I was thinking of something 
>>>> to identify a digital file on a computer network free of particular 
>>>> carrier. I guess that wouldn't be in a carrier vocabulary at all, 
>>>> after all, that would be sort of a null carrier. Phew, this stuff 
>>>> does get complicated quick. Which I guess is why nobody's worked 
>>>> out a good one yet.
>>>>
>>>> Too bad RDA's is so _far_ from good though. Any others anyone knows 
>>>> about?
>>>>
>>>> Jonathan
>>>>
>>>
>>>
>>>
>>> Jonathan Rochkind wrote:
>>>> Anyone know of any good existing controlled vocabulary for 'format' 
>>>> or 'carrier' for multimedia materials?  I'm thinking of things like 
>>>> "CD", "DVD", "digital", etc.
>>>>
>>>> The closest I can get is from RDA at 
>>>> http://metadataregistry.org/concept/list/vocabulary_id/46.html 
>>>> (thanks Karen and Diane), but it seems _really_ insufficient. As 
>>>> far as I can tell "audio disc" is used for both a CD and a vinyl 
>>>> disc, and there's nothing available there for "DVD" at all.   Or 
>>>> for "digital". Although I'm not sure what I mean by "digital", I 
>>>> guess CD and DVD are both digital, but I was thinking of something 
>>>> to identify a digital file on a computer network free of particular 
>>>> carrier. I guess that wouldn't be in a carrier vocabulary at all, 
>>>> after all, that would be sort of a null carrier. Phew, this stuff 
>>>> does get complicated quick. Which I guess is why nobody's worked 
>>>> out a good one yet.
>>>>
>>>> Too bad RDA's is so _far_ from good though. Any others anyone knows 
>>>> about?
>>>>
>>>> Jonathan
>>>>
>>>
>>
>

-- 
Jonathan Rochkind
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
410.516.8886 
rochkind (at) jhu.edu

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager