Extent of cartographic, still image, notated music, and 3D form are content 
related extent elements. The 'still image' list is content-related-- the 
carriers such as "sheet" or "card" should say nothing about what content is on 
them (could be a poster, could be a map, could be a folded sheet making a 
pamphlet).

That these various extent types may be augmented with subunits for the carriers 
(or themselves augment carriers) is part of the problem:

1 atlas (3 volumes)
3 maps on 2 sheets

versus

1 computer disc (3 maps)
1 microfilm reel (1 atlas)


The broad Content Type categories are fine -- a "map" is a content value 
subordinate to "cartographic image". I don't like saying "1 cartographic image" 
for 1 map.

Rather this is better:

Content Type = cartographic image
Media Type = unmediated
Carrier Type = sheet
** Extent of Carrier Type = 1
[note: one can substitute another term for carrier type - RDA 3.4.1.5 - these 
should also be registered]

** Cartographic unit = maps
** Extent of cartographic units = 2 [these number will also trigger the plural 
form - "maps"]


Display following instruction in RDA 3.4.2.3:

2 maps on 1 sheet



I think it's possible to break down the Extent values into content and carrier 
categories-- but there are rules for how they can be later combined in 
displays. There are some dependencies affecting what values go together and in 
what order. For example:

Content Type = cartographic image
Carrier Type = volume
Subunits of Carrier Type = 233 pages

Cartographic unit = atlas
Extent of cartographic unit = 1


Display following instruction in RDA 3.4.2.5:

1 atlas (233 pages)

Rules to follow: a content value ('atlas') augmented by subunit values of the 
carrier 'volume' which generally happens when there is only a single volume.


Thomas Brenndorfer
Guelph Public Library

________________________________________
From: Resource Description and Access / Resource Description and Access 
[RDA-L@LISTSERV.LAC-BAC.GC.CA] On Behalf Of Karen Coyle [li...@kcoyle.net]
Sent: April-11-12 3:10 AM
To: RDA-L@LISTSERV.LAC-BAC.GC.CA
Subject: Re: [RDA-L] Content and carrier

Thomas,

Here's my problem: to create a machine-actionable format for this data,
we need to define our "things" precisely. Right now we have 3 "things"
defined in RDA:

content
   - which has a defined list for type
carrier
   - which has a defined list for type
medium
   - which has a defined list for type

And then we have something called "extent", but clearly extent isn't a
thing on its own, it is an attribute of something else. It appears that
extent is intended to be an attribute of carrier, as per chapter 3.
Therefore a data model might have:

carrier = audio disc
   extent
     number of units = 2
   dimensions
     size in inches = 3.5
   compression
     ?? mp3

something like that. (I made that up, it might not be true to the
carrier type.) This could display as: "2 discs, MP3" or however you
wish. If the information needed for the user display isn't here, then
there are things that need to be added.

It makes no sense to separately code content and carrier, and then
create a display text for the same data. We should really only enter
data once. And we want all of the data to be machine-actionable, so
textual statements are to be avoided.

So I'm trying to figure out what to do with things like "map", which
seems to be content, not carrier, and which can have an extent. It seems
to me that we need:

content = cartographic 2-dimensional (e.g. map, but the former is more
precise as coded data)
   extent of content = 1
carrier = sheet
   extent of carrier
     number of units = 1
   dimensions of carrier
     height in cm = 30
     width in cm = 44

and this could display something like "map (1 sheet 30 x 44 cm)"

For this reason I need to know if your "units" are content, or are
carrier. I did a quick table showing RDA content terms, carrier terms,
and the terms from extent of still image:

http://kcoyle.net/rda/ContentCarrierStillImage.htm

The terms in extent of still image don't appear in either the content
nor the carrier list, but seem to be more detailed than either of those
lists. Are they types of content? Or types of carrier? Or (and I hope
not) a combination of the two.

kc


On 4/10/12 3:45 PM, Brenndorfer, Thomas wrote:
> By my count, there are several kinds of "units" for Extent in RDA:
>
>
> Units for Carrier Type, or, Units for term substituting for Carrier Type
>
> Units for cartographic resources; can be subunits for some carriers
>
> Units for notated music; can be subunits for some carriers
>
> Units for still images; can be subunits for some carriers
>
> Units for three-dimensional forms; can have further subunits of component 
> pieces
>
> Units for text (these stand alone as the subunits when a single volume is 
> involved; otherwise use units for Carrier Type (volume, sheet)); can be 
> subunits for some other carriers or used with special units (cartographic, 
> notated music)
>
> Special subunits for certain carriers-- special subunits can be used for 
> computer carriers, filmstrips and filmslips, flipcharts, microfiche, overhead 
> transparencies, stereographs, videodiscs of still images
>
>
> Thomas Brenndorfer
> Guelph Public Library
>
>
>
>
>
>> -----Original Message-----
>> From: Resource Description and Access / Resource Description and Access
>> [mailto:RDA-L@LISTSERV.LAC-BAC.GC.CA] On Behalf Of Karen Coyle
>> Sent: April 10, 2012 12:24 AM
>> To: RDA-L@LISTSERV.LAC-BAC.GC.CA
>> Subject: Re: [RDA-L] Content and carrier
>>
>> Thomas, it seems that you have introduced a new category: "unit." Given
>> that my interest is in creating an actual machine-actionable format for
>> this data, I have to ask: would this unit be coded as content, carrier, or
>> is it something different?
>>
>> kc
>>
>> On 4/10/12 1:26 AM, Brenndorfer, Thomas wrote:
>>> ________________________________________
>>> From: Resource Description and Access / Resource Description and Access
>> [RDA-L@LISTSERV.LAC-BAC.GC.CA] On Behalf Of Karen Coyle [li...@kcoyle.net]
>>> Sent: April-09-12 1:48 PM
>>> To: RDA-L@LISTSERV.LAC-BAC.GC.CA
>>> Subject: Re: [RDA-L] Content and carrier
>>>
>>> ....
>>>> So it looks like RDA does try to do a better separation of content and
>>>> carrier than exists in MARC, at least in the fixed field area. Also, RDA
>>>> content has the various cartographic types (dataset, image,
>>>> 3-dimensional, etc.) which I assume are subsumed under "map" in the MARC
>>>> 007.
>>>
>>> Rather the 007 for map is subsumed under LDR/06=e for cartographic
>> resources. The 007s for map and globe correspond to the cartographic
>> expression units (i.e., the cartographic extent units). My understanding is
>> that the 007 for map is applied to all cartographic resources, except
>> globes and if the carrier type is microform. Other 007s would be added for
>> the actual carriers' Media Type, like "projected" or "computer" or
>> "microform". The carriers are different -- volume, slide, object, computer
>> disc -- and don't indicate anything cartographic in and of themselves.
>>>
>>>
>>>>>
>>>>> An "atlas" can't be a carrier-- the carrier is defined in the
>>>>> RDA/ONIX Framework has having attributes such as binding and
>>>>> intermediation device. An "atlas" is only cartographic content, and
>>>>> the physical carrier could be three distinct physical volumes.
>>>>>
>>>>> Using all the elements, an atlas could be:
>>>>>
>>>>> Content Type: cartographic image Media Type: unmediated Carrier Type:
>>>>> volume Extent of Cartographic Resource: 1 atlas (3 volumes)
>>>>>
>>>
>>>> But it is listed in RDA under "extent of cartographic resource." So it's
>>>> either content or carrier, and it isn't in the RDA content list.  So it
>>>> seems that you are saying that the "extent of cartographic" list is
>>>> neither content nor carrier, but a display form that includes both?
>>>
>>>
>>> RDA 3.4.2.1 for the application of cartographic units points to "printed,
>> manuscript, graphic or three-dimensional resource" for situations in which
>> the cartographic unit appears first, followed by, on occasion, the carrier
>> type value, as in:
>>>
>>> 1 atlas (3 volumes)
>>>
>>>
>>> The situation is reversed for the other carrier types, in which the
>> cartographic unit follows the carrier type value:
>>>
>>> 1 computer disc (xv pages, 150 maps)
>>> [from RDA 3.4.1.7.1]
>>>
>>> Specifically, cartographic units are used as subunits for:
>>>
>>> RDA 3.4.1.7.1 - computer discs, cartridges, etc.
>>> RDA 3.4.1.7.4 - microfiches [this is actually being corrected in the
>> April update to RDA to reflect subunits for all types of microform]
>>> RDA 3.4.1.7.5 - online resources
>>>
>>>
>>>
>>>
>>>>
>>>>> The Carrier Type is what conveys the content -- it's not the content
>>>>> itself. Specific content and form values like "map", "globe",
>>>>> "poster", "drawing", "game", "coin", "score" describe content and
>>>>> cannot serve as Carrier Type values. Values like "pages" and "leaves"
>>>>> are better described as subunits of volumes, or potentially subunits
>>>>> of other carriers such as microform or online resources.
>>>
>>>> OK, this makes sense. But I don't understand what you are saying about
>>>> RDA's use of these. Are you saying that RDA's use of terms like "atlas"
>>>> in Extent of Cartographic unit is a good thing? And do you see it as
>>>> content, carrier, or both?
>>>
>>>
>>> As in the above examples, it's a bit confusing when the carrier type can
>> be both before or after the cartographic unit in the Extent element.
>>>
>>> It's easier to understand if there's a bit more granularity, with a
>> recognition that the cartographic units are really expression terms, not
>> manifestation terms. Carrying expression data inside of a manifestation
>> element isn't wrong, I would say-- it's just may lead to some
>> inefficiencies in duplicating that information for every manifestation for
>> the same expression.
>>>
>>> Thomas Brenndorfer
>>> Guelph Public Library
>>
>> --
>> Karen Coyle
>> kco...@kcoyle.net http://kcoyle.net
>> ph: 1-510-540-7596
>> m: 1-510-435-8234
>> skype: kcoylenet

--
Karen Coyle
kco...@kcoyle.net http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet

Reply via email to