I believe that Terence is right. Instead of:
<temporal authorityURI="http://library.unsw.edu.au/vocabulary"
valueURI="http://library.unsw.edu.au/vocabulary#builtDate">1968</temporal>
you could do:
<temporal
authorityURI="http://library.unsw.edu.au/vocabulary#builtDate">1968</temporal>
In this case, your value is a literal string (which dates are), not a
selection from a list of terms that each have a URI.
That assumes that "authorityURI" refers to the actual authority
property, not a generic URI for an authority vocabulary.
kc
On 4/16/14, 7:58 AM, Terence H. Catapano wrote:
> Alyson,
>
> I'm not sure the valueUri attribute is being used as intended in your
> example.
>
> According to the change document for MODS 3.4
> (http://www.loc.gov/standards/mods/changes-3-4.html), the valueUri
> attribute is defined as:
>
> "A URI uniquely identifying the term or controlled value, as assigned by
> the body responsible for the maintenance of the vocabulary."
>
> In your example the valueUri is being used to uniquely identify the
> *type* or subclass of temporal term being used, not to uniquely identify
> the value/term itself.
>
> I confess I don't know where you could include the typing/subclassing
> information. The documentation on authorityUri/valueUri is sparse, so
> maybe others can comment on the intended usage of the attributes.
>
> /Terry
>
>
>
>
> On Tue, 15 Apr 2014, Alyson Dalby wrote:
>
>> Hello,
>>
>> I'm trying to create a MODS framework for a collection of photos of
>> ships,
>> and I'm hoping that the user community can help me with the use of the
>> authorityURI and valueURI attributes.
>>
>> The photos can contain multiple ships, each of which has several
>> descriptive
>> elements. To achieve this we're mapping along the following lines:
>>
>> Ship 1:
>> <subject>
>> <name></name>
>> <genre></genre>
>> <occupation></occupation>
>> <temporal></temporal>
>> </subject>
>>
>> Ship 2:
>> <subject>
>> <name></name>
>> <genre></genre>
>> <occupation></occupation>
>> <temporal></temporal>
>> </subject>
>>
>> This seems fairly straightforward. Where things get complex is in the
>> temporal element.
>>
>> Each ship has three dates associated with it - the build date,
>> commissioned
>> date and the decommissioned date. As there is no display label
>> attribute in
>> the temporal sub-element, we're looking at using authorityURI and
>> valueURI.
>> In this case, the authority is us (my library) and the values are "built
>> date", "commissioned date" and "decommissioned date".
>>
>> This would look like:
>>
>> <subject>
>> <temporal authorityURI="http://library.unsw.edu.au/vocabulary"
>> valueURI="http://library.unsw.edu.au/vocabulary#builtDate">1968</temporal>
>>
>> <temporal authorityURI="http://library.unsw.edu.au/vocabulary"
>> valueURI="http://library.unsw.edu.au/vocabulary#commissionedDate">1969</temp
>>
>> oral>
>> <temporal authorityURI="http://library.unsw.edu.au/vocabulary"
>> valueURI="http://library.unsw.edu.au/vocabulary#decommissionedDate">1980</te
>>
>> mporal>
>> </subject>
>>
>> The questions we have are:
>> 1. Can authorityURI and valueURI be specified at the lower
>> sub-element? The
>> examples we found all have it at the top level element.
>> 2. If one specifies the valueURI, are we right in thinking that one still
>> needs the actual element value between the tags? (In the example
>> above, that
>> would be the "1968" bit.)
>> 3. Is this a correct use of the authorityURI and valueURI attributes?
>> Have
>> we done anything wrong with this mapping?
>>
>> We've been pouring over the guidelines and we're still unsure of the
>> answers
>> to these questions. I hope someone in the community can help us out!
>>
>> Alyson Dalby
>> Library Repository Services, UNSW Australia
>>
>>
>
> Terry Catapano
> Special Collections Analyst/Librarian
> Columbia University Libraries Digital Program
> 212-854-9942
> [log in to unmask]
>
--
Karen Coyle
[log in to unmask] http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet
|