Order of Elements to be Displayed (getFull dissemination):
<title>
<agent> except <agent type="provider">
<place>
<time>
<physdesc>
<mediatype>
<description>
<subject>
<covplace>
<covtime>
<culture>
<style>
<agent type="provider">
<language>
<identifier>
<rights>
Display Label and Display Value Details:
The element s are those under the first instance of <divdesc>. All
occurrences of an element should be displayed.
All labels will be bold, lower case followed by a colon, e.g., name:
Unless otherwise noted, the display values are taken from the values inside
the element tags.
<agent><name>
If agent has a role attribute, use the value of the attribute as the label.
If agent has no role attribute, use the value of the type attribute as the
label.
If agent has no type attribute, use the text string "name" as
the label.
Ex:
painter: where <agent role="painter">
provider: where <agent type="provider">
name: where <agent>
Where <agent> displays in the order of elements will change, dependent
upon one particular attribute value. All instances of agent will appear
immediately following all instances of <title>, except when the attribute
value = "provider". When <agent attribute="provider>,
that instance of <agent> should appear between instances of the <style>
and <language> elements.
The display value for an agent is taken from its child element <name>.
But, if there are additional child elements <date> or <timeinterval>,
the values are concatenated and formatted differently. See the entries for
<date> and <timeinterval>for instructions on concatenating and
formatting.
<covplace><geogname>
Use the text string "place coverage" as the label.
The display value for <covplace> is usually straightforward and is
simply the value of the child element <geogname>, but can be affected
by its child elements <date> or <timeinterval>, where the values
are concatenated and formatted differently. See the entries for <date>
and <timeinterval>for instructions on concatenating and formatting.
<covtime>
Use the text string "date coverage" as the label.
The display value for <covtime> is usually straightforward and is
simply the value, but can be affected by its child elements <date>
or <timeinterval>, the values are concatenated and formatted differently.
See the entries for <date> and <timeinterval>for instructions
on concatenating and formatting.
<culture>
If culture has a type attribute, use the value of the type as the label.
Use the element name "culture" as the label.
Ex:
tribe: where <culture type="tribe">
culture: where <culture>
If there are multiple instances of <culture>, the values can be concatenated
using spaces and semicolons.
Ex:
culture: Spanish ; Galician where there is <culture>Spanish</culture>
and <culture>Galician</culture>
<description>
If description has a type attribute, use the value of the type as the label.
If description has no type attribute, use the text string "note"
as the label.
Ex:
inscription: where <description type="inscription">
note: where <description>
For a "display caption," when the description is used without
any label, such as for the caption text that appears under child object
thumbnails in the getFull display for a work object, the value is taken
from the instance of <description> that accompanies the thumbnail
resource link in its <res>.
Ex:
general view, entrance and archways where <description> general
view, entrance and archways</description> is present inside <res>
inside <resgrp>, which follows the <divdesc>.
<identifier>
If identifier has a type attribute, use the element name, followed by the
value of the type in parentheses.
If identifier has no type attribute, use the element name "identifier"
as the label
Ex:
identifier (accession number): where <identifier type="accession
number">
identifier: where <identifier>
<language>
Use the element name "language" as the label.
<mediatype><form>
Use the text string "type" as the label.
The value is taken from the <form> element that is wrapped in <mediatype>,
if no <form> element, use <mediatype> type attribute as the
value.
Ex:
type: Church (where <mediatype type="image"><form>Church</form></mediatype>)
type: image (where <mediatype type="image"/>)
If there are multiple instances of <mediatype><form>, the values
can be concatenated using spaces and semicolons.
Ex:
type: artwork ; painting where there is <mediatype><form>artwork</mediatype></form>
and <mediatype><form>painting</mediatype></form>
<physdesc>
If the type attribute="medium", then use the type attribute value
"medium" as the label.
If there is a type attribute="extent", then use the text string
"physical description" as the label
Ex:
medium: where <physdesc type="medium">
physical description: where <physdesc type="extent">
If there are multiple instances of <physdesc> with the same type, the
values can be concatenated using spaces and semicolons. Different types should
appear on separate lines.
Ex:
medium: timber ; steel ; glass ; pine ; reinforced concrete where
there are multiple instances of <physdesc type="medium">
<pid>
Do not include in the user display.
<place><geogname>
If there is a type attribute on <place>, use the element name "place",
followed by the value of the type in parentheses.
If there is no type attribute, then use the element name "place".
Ex:
place (current location): where <place type="current location">
place: where <place>
The value is taken from the <geogname> element that is wrapped in
<place>.
<relationship><set>
Do not include in the user display.
<rights>
If rights has a type attribute, use the value of the type as the label.
If rights has no type attribute, use the element name "rights"
as the label.
Ex:
access: where <rights type="access">
rights: where <rights>
<style>
Use the element name "style" as the label.
If there are multiple instances of <style>, the values can be concatenated
using spaces and semicolons.
Ex:
style: Byzantine ; Baroque where there is <style>Byzantine</style>
and <style>Baroque</style>
<subject>
If the scheme attribute = "unknown", then use the element name
"subject".
If the scheme attribute is present and is not "unknown", then
use the element name "subject", followed by the value of the scheme
in parentheses.
If there is no scheme attribute, then use the element name "subject".
Ex:
subject (aat): where <subject scheme="aat">
subject: where <subject scheme="unknown">
subject: where <subject>
<time>
If the type attribute is present, then use the value of the type attribute,
followed by a space and then the text string "date".
If there is no type attribute, then use the text string "date".
Ex:
publication date: where <time type="publication">
date: where <time>
The display value for <time> is taken from its child elements <date>
or <timeinterval>. See the entries for <date> and <timeinterval>for
instructions on concatenating and formatting.
<title>
For a "display title," when the title is used without any label,
such as at the top of a record display or as a caption in a results set,
select the title occurrence with the type attribute = "main",
or, if there is no type, use the first instance of the title element.
Ex:
Mandan Village as a display title where <title type="main">Mandan
Village</title>>, otherwise use the first occurrence of <title>,
whether it is typed or not
For all other titles displayed within the record information:
If the main title is additionally displayed anywhere where it requires a
label, when the type attribute="main", use the element name "'title"
as the label.
If a type attribute is present and the attribute value is "Larger
Entity Title", use the text string "related title" as the
label.
If a type attribute is present and the attribute value is not "main"
or "Larger Entity Title", then use the value of the type attribute,
followed by a space and then the text string "title".
If there is no type attribute, then use the element name "title".
Ex:
alternate title: where <title type="alternate">
related title: where <title type="Larger Entity Title">
title: where <title>
<date>
The date element is a very special case. The date element can appear wrapped
in other elements. You might see:
<agent role="painter"><name>Catlin, George</name><time><date>1796</date><date>1872</date></time></agent>
<date> can appear within <time>, <physdesc>, <place>,
<rights>, <covtime>, or <covplace>. When the date element
is wrapped in another element, it does not affect the label, but affects
the concatenation and formatting of the display value.
<time> and <date> display values
When <date> is wrapped within <time>, the value is not pulled
out with a label; the value is what follows the label from the <time>
element. <date> can also appear in pairs, for use in denoting date
ranges. <Date> will never appear more than twice for a date range.
Ex:
construction date: 1920-1931 when
<time type="construction"><date>1920</date><date>1931</date></time>
<date> dash <date> - two instances of <date> are separated
by a dash
or
publication date: 1923 when <time type="publication"><date>1920</date></time>
<date> - when there is a single instance of <date>
When <time> and <date> are wrapped in <agent>, the rules
are different.
painter: Rossetti, Dante Gabriel, 1828-1882 when <agent role="painter"><name>Rossetti,
Dante Gabriel</name><time><date>1828</date><date>1882</date></time></agent>
<name>comma space <date> dash <date> - two instances
of <date> are separated by a dash
or
painter: Thiebaud, Wayne, 1920- when <agent role="painter"><name>Thiebaud,
Wayne</name><time><date>1920</date></time></agent>
<name>comma space <date> dash
Only when wrapped in <agent> will a dash follow a single instance
of <date>
<covtime> and <date> display values
When <date> is wrapped within <covtime>, the value is not pulled
out with a label; the value is what follows the label from the <covtime>
element.
Ex:
date coverage: 1920-1931 when <covtime><date>1920</date><date>1931</date></covtime>
<date> dash <date> - two instances of <date> are separated
by a dash
or
date coverage: 1923 when <covtime><date>1923</date></covtime>
<date> - when there is a single instance of <date>
<covplace> and <date> display values
When <date> is wrapped within <covplace>, the value is not
pulled out with a label; the value is concatenated with the value from the
<covplace>. <date> can also appear in pairs, for use in denoting
date ranges. <Date> will never appear more than twice for a date range.
Ex:
place coverage: Spain, 1828-1882 when <covplace><geogname>Spain</geogname><date>1828</date><date>1882</date></covplace>
<covplace> comma space <date> dash <date> - two instances
of <date> are separated by a dash
or
place coverage: Spain, 1920 when <covplace><geogname>Spain</geogname><date>1920</date></covplace>
<covplace>comma space <date> - when there is a single instance
of <date>
The display value for <date> is usually straightforward and is simply
the value, but can be affected by its certainty or era attributes, where
the values are concatenated and formatted differently.
If <date> has a certainty attribute, then use the value of the certainty
attribute, followed by a space and then the value from <date>
Ex:
date: before 1900 when <date certainty="before">1900</date>
If <date> has an era attribute="bc", then use the value,
followed by the text string "BC"
Ex:
date: 1000 BC when <date era="BC">1000</date>
When there are two instances of date on its own with the same type or untyped,
then the instances should be treated as a data range.
Ex:
date: 1000 BC-1400 when <date era="BC">1000</date><date>1400</date>
<timeinterval>
The date element is a very special case. The <timeinterval> element
can appear wrapped in other elements. You might see:
<agent role="painter"><name> Jacopus, Master</name><time><timeinterval>15th
Century</timeinterval></time></agent>
<timeinterval> can appear within <time>, <physdesc>,
<place>, <rights>, <covtime>, or <covplace>. When
the date element is wrapped in another element, it does not affect the label,
but affects the concatenation and formatting of the display value.
<covplace> and <timeinterval> display values
When <timeinterval> is wrapped within <covplace>, the value
is not pulled out with a label; the value is concatenated with the value
from the <covplace>. <timeinterval> can also appear in pairs,
for use in denoting date ranges. <timeinterval> will never appear
more than twice for a date range.
Place coverage: Spain, 11th Century-12th Century when <covplace><geogname>Spain</geogname><timeinterval>11th
century</timeinterval><timeinterval>12th Century</timeinterval></covplace>
<covplace> comma space <timeinterval> dash <timeinterval>
- two instances of <timeinterval> are separated by a dash
or
place coverage: Spain, 14th Century <covplace><geogname>Spain</geogname><timeinterval>14th
century</timeinterval></covplace>
<covplace>comma space <timeinterval> - when there is a single
instance of <timeinterval>
<time>, <rights>, <place>, <physdesc>,
<covtime>,or <covplace> and <timeinterval>
display values
When <timeinterval> is wrapped within any of the above elements,
the value is not pulled out with a label; the value is what follows the
label from the any of these elements.
Ex:
construction date: After 200-Before 400 when
<time type="construction"><timeinterval>After 200</timeinterval><timeinterval>Before
400</timeinterval></time>
<timeinterval> dash <timeinterval> - two instances of <timeinterval>
are separated by a dash
or
publication date: January 15, 1970 when <time type="publication"><timeinterval>
January 15, 1970</timeinterval></time>
<timeinterval> - when there is a single instance of <timeinterval>
or
date coverage: 17th Century-19th Century when <covtime><timeinterval>1th
century</timeinterval><timeinterval>19th Century</timeinterval></covtime>
<timeinterval> dash <timeinterval> - two instances of <timeinterval>
are separated by a dash
or
date: 20th Century when <time><timeinterval>20th Century</timeinterval></time>
<timeinterval> - when there is a single instance of <timeinterval>
<rescon>
Sometimes, following the image thumbnails (<resgrp label="Digital
Images">), there will be textual information <resgrp label="Texts">.
The structure is:
<description type="citation">Citation for where the text
comes from</citation>
<rescon>
<section>
<p>Paragraphs of text about the images</p>
<p>And sometimes multiple paragraphs</p>
</section>
</rescon>
The display values are taken from <description> and from <section>,
do not require display labels, and can be formatted in whatever way is appropriate
for the interface design.
June 24, 2004; updated September 2, 2004
|
