Here is another example that uses the notes field. Both notes and the
display relate to the entire agent set as attached to the specific
work (the Musee d'Orsay/ Gare d'Orsay). CCO also suggests how to do
end dates for living people, active firms (plus 100 for individual,
9999 for firm). I happen to do that the other way round (plus hundred
for firm, 9999 for individual), as I think it is easier to find and
update the "9999" as individual artists die and you can replace it
with their actual death date. You could also add an "extent" to go
with the role for Gae Aulenti--"interior design", but my xml export
does not do that at the moment (although it is in my database).
Does this help?
--<agentSet>
<display>
ACT Architecture (French architectural firm, founded ca. 1982);
Gaetana Aulenti (Italian architect, born 1927); Victor Alexandre
Frédéric Laloux (French architect, 1850-1937)</display>
<notes>
ACT Architecture members: Renaud Bardon, Pierre Colboc and Jean-Paul Philippon
</notes>
-<agent>
<name refid="500023967" type="personal" vocab="ULAN">Laloux, Victor
Alexandre Frédéric</name>
-<dates type="life">
<earliestDate>1850</earliestDate>
<latestDate>1937</latestDate>
</dates>
<culture>French</culture>
<role>architect</role>
</agent>
-<agent>
<name refid="500031019" type="personal" vocab="ULAN">Aulenti, Gaetana</name>
-<dates type="life">
<earliestDate>1927</earliestDate>
<latestDate>9999</latestDate>
</dates>
<culture>Italian</culture>
<role>architect</role>
</agent> -
<agent> <name refid="nr 95039966" type="corporate" vocab="LCNAF">ACT
Architecture</name>
-<dates type="activity">
<earliestDate>1982</earliestDate>
<latestDate>2082</latestDate>
</dates>
<culture>French</culture>
<role>architectural firm</role>
</agent>
</agentSet>
>
>
> On Mon, May 21, 2012 at 10:40 AM, Arnold (exc), Matthias
> <[log in to unmask]> wrote:
>>
>>
>> Hello list,
>>
>>
>>
>> I’m a bit puzzled about the use of repeating top-level elements together
>> with <display> and <notes>.
>>
>>
>>
>> If I have for instance three agents, the schema allows me to record:
>>
>> <agentSet>
>> <display/>
>> <notes/>
>> <agent>
>> <name>AGENT 1</name>
>> </agent>
>> <agent>
>> <name>AGENT 2</name>
>> </agent>
>> <agent>
>> <name>AGENT 3</name>
>> </agent>
>> </agentSet>
>> however, this means that the <display> and <notes> elements may not be used
>> for an individual agent, but only for the whole agentSet.
>>
>>
>>
>> the two alternative versions, which would make agent-specific display/notes
>> values possible, are not allowed:
>>
>> a) repeating sets
>>
>> <agentSet>
>> <display/>
>> <notes/>
>> <agent>
>> <name>AGENT 1</name>
>> </agent>
>> </agentSet>
>> <agentSet>
>> <display/>
>> <notes/>
>> <agent>
>> <name>AGENT 2</name>
>> </agent>
>> </agentSet>
>> <agentSet>
>> <display/>
>> <notes/>
>> <agent>
>> <name>AGENT 3</name>
>> </agent>
>> </agentSet>
>> b) repeating agents with “inline” display/notes
>>
>> <agentSet>
>> <agent>
>> <display/>
>> <notes/>
>> <name>AGENT 1</name>
>> </agent>
>> <agent>
>> <display/>
>> <notes/>
>> <name>AGENT 2</name>
>> </agent>
>> <agent>
>> <display/>
>> <notes/>
>> <name>AGENT 3</name>
>> </agent>
>> </agentSet>
>>
>> My question is, if that is intended or perhaps a mistake in the schema? how
>> should display/notes values for multiple agents be handles?
>>
>>
>>
>> Alternatively, even if variant a) is not possible because elementSets may
>> not be repeated, variant b) might be useful if multiple agents occur,
>> because it directly connects display/notes values to one agent. Could that
>> be considered for a possible future update of the schema?
>>
>>
>>
>> Best,
>>
>> Matthias Arnold
>>
>>
>
>
>
> --
> Susan Jane Williams
> Independent Cataloging and Consulting Services
> [log in to unmask]
> Phone: 812-272-1896
--
Susan Jane Williams
Independent Cataloging and Consulting Services
[log in to unmask]
Phone: 812-272-1896
|