2009
Backyard Botanicals Metadata
Dictionary
Digital Underground
11/1/2009
Digital Underground Data Dictionary
Descriptive, Technical, and Administrative Metadata for Digital Images
pertaining to the
Backyard Botanicals Collection
This data dictionary provides a complete reference to the metadata used for the Backyard Botanicals
Collection at Dspace. The list was compiled using Dublin Core standards as well as NISO. For the
complete metadata elements as well as clarification please refer to the Dublin Core website at
http://dublincore.org/documents/dces/. For the complete list of NISO standards please refer to the
ANSI/NISO Z39.87 - Data Dictionary - Technical Metadata for Digital Still Images, which can be found
at
http://www.niso.org/kst/reports/standards?step=2&gid=None&project_key=b897b0cf3e2ee526252d9f830
207b3cc9f3b6c2c.
The Premis Data Dictionary for Preservation Metadata Standards was used as a reference for this
dictionary, specifically 2.1 eventIdentifier and 3.1 agentIdentifier. These two elements were tailored to
meet the specific needs of the Backyard Botanicals Collection. DC and NISO standards were used to
fulfill the provenance requirements of the collection therefore negating the need to utilize Premis as more
than a reference.
Usage
This dictionary should be utilized by anyone submitting to the collection; as well as anyone maintaining
the collection for preservation. Permission to update this dictionary will be granted for the purpose of
maintenance and preservation.
Document Administration
This dictionary is authored, administered and maintained by the Digital Underground.
Karen Davis
Jon-Erik Gilot
Mystye Gorgan
Forest Rushay
Gregory Stall
3
Backyard Botanicals Metadata Dictionary
Section 1: Dublin Core................................................................................................................................... 4
4.1 Title ..................................................................................................................................................... 4
4.8. Creator ............................................................................................................................................... 4
4.2 Subject................................................................................................................................................. 5
4.3 Description .......................................................................................................................................... 5
4.17 Provenance ....................................................................................................................................... 6
4.4 Type..................................................................................................................................................... 6
4.7 Coverage ............................................................................................................................................. 7
4.10 Contributor ....................................................................................................................................... 7
4.11 Rights................................................................................................................................................. 8
4.12 Date ................................................................................................................................................... 8
4.13 Format ............................................................................................................................................... 8
4.16 Audience ........................................................................................................................................... 9
4.18 Rights Holder..................................................................................................................................... 9
Section 2: NISO............................................................................................................................................ 10
6.2 fileSize ............................................................................................................................................... 10
7.1.1 imageWidth.................................................................................................................................... 10
7.1.2 imageHeight .................................................................................................................................. 11
7.1.3.1 colorSpace ................................................................................................................................... 11
8.2.1 dateTimeCreated ........................................................................................................................... 11
8.2.2 imageProducers ............................................................................................................................. 12
8.2.3 captureDevice ................................................................................................................................ 12
8.4.1 digitalCameraManufacturer........................................................................................................... 12
8.4.2.1 digitalCameraModelName .......................................................................................................... 13
8.4.2.2 digitalCameraModelNumber ...................................................................................................... 13
10.1.4 processingRationale ..................................................................................................................... 13
10.1.5 Processing Software ..................................................................................................................... 14
10.1.6 processingActions ........................................................................................................................ 14
10.2 Previous Image Metadata ............................................................................................................... 14
Section 3: DUMD (Digital Underground Metadata).................................................................................... 15
agentIdentifier ........................................................................................................................................ 15
eventIdentifier ........................................................................................................................................ 15
3
Section 1: Dublin Core
4.1 Title
Label
Element Description
Guidelines
Title
The name given to the resource. Typically, a Title will be a name by which the
resource is formally known.
If in doubt about what constitutes the title, repeat the Title element and include
the variants in second and subsequent Title iterations. If the item is in HTML,
view the source document and make sure that the title identified in the title
header (if any) is also included as a Title.
Ex
Notes
Title="A Pilot's Guide to Aircraft Insurance"
A second property with the same name as this property has been declared in the
dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the
document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmiterms/) for an explanation.
Mandatory/Optional M
Repeatable
No
4.8. Creator
Label
Element Description
Guidelines
Creator
An entity primarily responsible for making the content of the resource. Examples
of a Creator include a person, an organization, or a service. Typically the name of
the Creator should be used to indicate the entity.
Creators should be listed separately, preferably in the same order that they
appear in the publication. Personal names should be listed surname or family
name first, followed by forename or given name. When in doubt, give the name
as it appears, and do not invert.
In the case of organizations where there is clearly a hierarchy present, list the
parts of the hierarchy from largest to smallest, separated by full stops and a
space. If it is not clear whether there is a hierarchy present, or unclear which is
the larger or smaller portion of the body, give the name as it appears in the item.
Ex
Notes
Creator="Shakespeare, William"
If the Creator and Publisher are the same, do not repeat the name in the
Publisher area. If the nature of the responsibility is ambiguous, the
recommended practice is to use Publisher for organizations, and Creator for
individuals. In cases of lesser or ambiguous responsibility, other than creation,
use Contributor.
5
Backyard Botanicals Metadata Dictionary
Mandatory/Optional M
Repeatable
No
4.2 Subject
Label
Element Description
Guidelines
Subject and Keywords
The topic of the resource.
Typically, the subject will be represented using keywords, key phrases, or
classification codes. Recommended best practice is to use a controlled
vocabulary. To describe the spatial or temporal topic of the resource, use the
Coverage element.
In general, choose the most significant and unique words for keywords, avoiding
those too general to describe a particular item. Subject might include
classification data if it is available (for example, Library of Congress Classification
Numbers or Dewey Decimal numbers) or controlled vocabularies (such as
Medical Subject Headings or Art and Architecture Thesaurus descriptors) as well
as keywords.
When including terms from multiple vocabularies, use separate element
iterations. If multiple vocabulary terms or keywords are used, either separate
terms with semi-colons or use separate iterations of the Subject element.
Ex
Notes
Subject="Aircraft leasing and renting"
A second property with the same name as this property has been declared in the
dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the
document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmiterms/) for an explanation.
Mandatory/Optional M
Repeatable
Yes
4.3 Description
Label
Element Description
Guidelines
Description
An account of the content of the resource. Description may include but is not
limited to: an abstract, table of contents, reference to a graphical representation
of content or a free-text account of the content.
Since the Description field is a potentially rich source of indexable terms, care
should be taken to provide this element when possible. Best practice
recommendation for this element is to use full sentences, as description is often
used to present information to users to assist in their selection of appropriate
5
resources from a set of search results.
Descriptive information can be copied or automatically extracted from the item if
there is no abstract or other structured description available. Although the
source of the description may be a web page or other structured text with
presentation tags, it is generally not good practice to include HTML or other
structural tags within the Description element. Applications vary considerably in
their ability to interpret such tags, and their inclusion may negatively affect the
interoperability of the metadata.
Ex
Description="Illustrated guide to airport markings and lighting signals, with
particular reference to SMGCS (Surface Movement Guidance and Control
System) for airports with low visibility conditions."
Notes
A second property with the same name as this property has been declared in the
dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the
document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmiterms/) for an explanation.
Mandatory/Optional O
Repeatable
No
4.17 Provenance
Label
Element Description
Guidelines
Ex
Provenance
A statement of any changes in ownership and custody of the resource since its
creation that are significant for its authenticity, integrity and interpretation. The
statement may include a description of any changes successive custodians made
to the resource.
Provenance="This copy once owned by Benjamin Spock."
Provenance="Estate of Hunter Thompson."
Provenance="Stolen in 1999; recovered by the Museum in 2003."
Notes
Under the DC Element Description
Mandatory/Optional O
Repeatable
Yes
4.4 Type
Label
Element Description
Resource Type
The nature or genre of the content of the resource. Type includes terms
describing general categories, functions, genres, or aggregation levels for
content. Recommended best practice is to select a value from a controlled
vocabulary (for example, the DCMIType vocabulary ). To describe the physical or
digital manifestation of the resource, use the FORMAT element.
7
Backyard Botanicals Metadata Dictionary
Guidelines
If the resource is composed of multiple mixed types then multiple or repeated
Type elements should be used to describe the main components.
Type="Image"
Ex
Notes
Mandatory/Optional O
Repeatable
Yes
4.7 Coverage
Label
Element Description
Guidelines
Coverage
The extent or scope of the content of the resource. Coverage will typically
include spatial location (a place name or geographic co-ordinates), temporal
period (a period label, date, or date range) or jurisdiction (such as a named
administrative entity). Recommended best practice is to select a value from a
controlled vocabulary (for example, the Thesaurus of Geographic Names [Getty
Thesaurus of Geographic Names, http://www.
getty.edu/research/tools/vocabulary/tgn/]). Where appropriate, named places
or time periods should be used in preference to numeric identifiers such as sets
of co-ordinates or date ranges.
Whether this element is used for spatial or temporal information, care should be
taken to provide consistent information that can be interpreted by human users,
particularly in order to provide interoperability in situations where sophisticated
geographic or time-specific searching is not supported. For most simple
applications, place names or coverage dates might be most useful.
Coverage="Boston, MA"
Ex
Notes
Mandatory/Optional O
Repeatable
No
4.10 Contributor
Label
Element Description
Guidelines
Contributor
An entity responsible for making contributions to the resource.
Examples of a Contributor include a person, an organization, or a service.
Typically, the name of a Contributor should be used to indicate the entity.
Ex
Notes
The same general guidelines for using names of persons or organizations as
Creators apply here. Contributor is the most general of the elements used for
"agents" responsible for the resource, so should be used when primary
responsibility is unknown or irrelevant.
Mandatory/Optional O
Repeatable
Yes
7
4.11 Rights
Label
Element Description
Guidelines
Ex
Rights Management
Information about rights held in and over the resource. Typically a Rights
element will contain a rights management statement for the resource, or
reference a service providing such information. Rights information often
encompasses Intellectual Property Rights (IPR), Copyright, and various Property
Rights. If the rights element is absent, no assumptions can be made about the
status of these and other rights with respect to the resource.
The Rights element may be used for either a textual statement or a URL pointing
to a rights statement, or a combination, when a brief statement and a more
lengthy one are available.
Rights="Access limited to members"
Rights="http://cs-tr.cs.cornell.edu/Dienst/Repository/2.0/Terms& quot;
Notes
Mandatory/Optional O
Repeatable
No
4.12 Date
Label
Element Description
Guidelines
Ex
Date
A date associated with an event in the life cycle of the resource. Typically, Date
will be associated with the creation or availability of the resource. Recommended
best practice for encoding the date value is defined in a profile of ISO 8601 [Date
and Time Formats, W3C Note, http://www.w3.org/TR/NOTE- datetime] and
follows the YYYY-MM-DD format.
If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may
be used. Many other schemes are possible, but if used, they may not be easily
interpreted by users or software.
Date="1998-02-16"
Date="1998-02"
Date="1998"
Notes
Mandatory/Optional M
Repeatable
Yes
4.13 Format
Label
Element Description
Guidelines
Format
The file format, physical medium, or dimensions of the resource.
In addition to the specific physical or electronic media format, information
concerning the size of a resource may be included in the content of the Format
9
Backyard Botanicals Metadata Dictionary
element if available. In resource discovery size, extent or medium of the resource
might be used as a criterion to select resources of interest, since a user may need
to evaluate whether they can make use of the resource within the infrastructure
available to them.
When more than one category of format information is included in a single
record, they should go in separate iterations of the element.
Ex
Title="Dublin Core icon"
Identifier="http://purl.org/metadata/dublin_core/images/dc2.gif& quot;
Type="Image"
Format="image/gif"
Format="4 kB"
Notes
Recommended best practice is to select a value from a controlled vocabulary (for
example, the list of Internet Media Types [http://www.iana.org/
assignments/media-types/] defining computer media formats).
Mandatory/Optional O
Repeatable
Yes
4.16 Audience
Label
Element Description
Guidelines
Ex
Audience
A class of entity for whom the resource is intended or useful. A class of entity
may be determined by the creator or the publisher or by a third party.
Audience terms are best utilized in the context of formal or informal controlled
vocabularies. None are presently recommended or registered by DCMI, but
several communities of interest are engaged in setting up audience vocabularies.
In the absence of recommended controlled vocabularies, implementers are
encouraged to develop local lists of values, and to use them consistently.
Audience="elementary school students"
Audience="ESL teachers"
Audience="deaf adults"
Notes
Mandatory/Optional O
Repeatable
No
4.18 Rights Holder
Label
Element Description
Guidelines
Rights Holder
A person or organization owning or managing rights over the resource.
Recommended best practice is to use the URI or name of the Rights Holder to
indicate the entity.
Since, for the most part, people and organizations are not typically assigned URIs,
9
Ex
a person or organization holding rights over a resource would be named using a
text string. People and organizations sometimes have websites, but URLs for
these are not generally appropriate for use in this context, since they are not
clearly identifying the person or organization, but rather the location of a website
about them.
RightsHolder="Stuart Weibel"
RightsHolder="University of Bath"
Notes
Uncer the DC Element Rights
Mandatory/Optional O
Repeatable
No
Section 2: NISO
6.2 fileSize
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes
Use
A data element that designates the size in bytes of the image file
Positive integer
M
N
618 72839
The file size must record the number of bytes as recorded by the system. Do not
attempt to record file sizes in terms of KB, MB, or other notation
System
7.1.1 imageWidth
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
Use
A data element that specifies the width of the digital image, i.e. horizontal or x
dimensions in pixels
Positive integer
M
N
1330
The image width may be the shorter or longer dimension of the image,
depending upon the orientation of the camera or scanner during image capture.
For multiple resolution image file formats, value shall specify the highest
resolution
System
Manager
User
11
Backyard Botanicals Metadata Dictionary
7.1.2 imageHeight
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
Use
A data element that specifies the height of the digital image, i.e. vertical or y
dimensions in pixels
Positive integer
M
N
2130
The image height may be the shorter or longer dimension of the image,
depending upon the orientation of the camera or scanner during image capture.
For multiple resolution image file formats, value shall specify the highest
resolution
System
Manager
User
7.1.3.1 colorSpace
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
A data element that designates the color model of the decompressed image
data.
String
O
N
WhitelsZero
BlacklsZero
RGB
PaletteColor
TransparencyMask
CMYK
YcbCr
CIELab
ICClab
DeviceGray
DeviceRGB
DeviceCMYK
Other(key in appropriate text name)
Notes:
Use
8.2.1 dateTimeCreated
Definition
A data element that designates the Date or Date Time the image was created
11
Type
Mandatory/Optinal
Repeatable
Values
Ex:
Notes:
Use
Date Time
MA
N
YYYY-MM-DD (2004-07-15)
YYYY-MM-DD HH:MM:SS (2004-07-15 19:20:00
Use ISO 8601 numeric representations of date and time
See section 10.1.1 dateTimeProcessed for images created by processing image
data (digital to digital)
Manager
8.2.2 imageProducers
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
Use
A data element that identifies the organization –level producers of the image
string
O
Y
Luna Imaging
JJT, Inc
University of Michigan
The image width may be the shorter or longer dimension of the image,
depending upon the orientation of the camera or scanner during image capture.
For multiple resolution image file formats, value shall specify the highest
resolution
Manager
8.2.3 captureDevice
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
Use
A data element that designates the classification of device used to create the
image data
Enumerated type (restricted to list)
O
N
Transmission scanner
Reflection print scanner
Digital still camera
Still from video
When image processing is used to generate the image data from a digital source,
see section 10.1 ImageProcessing
Manager
8.4.1 digitalCameraManufacturer
Definition
A data element that identifies the manufacturer of the digital camera used to
13
Backyard Botanicals Metadata Dictionary
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
Use
create the image
String
O
N
Phase One
Manager
8.4.2.1 digitalCameraModelName
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
Use
A data element that identifies the camera model name of the digital camera
used to create the image
String
O
N
H_20
When image processing is used to generate the image data from a digital source,
see section 10.1 ImageProcessing
Manager
8.4.2.2 digitalCameraModelNumber
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
Use
A data element that identifies the model number of the digital camera used to
create the image
String
R
N
C2520B
Manager
10.1.4 processingRationale
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
A data element that provides rationale for image editing decisions or describes
trigger event for image migration
String
O
N
Processing action in 10.1.6 undertaken to best match to source image
TIFF to JPEG 2000 undertaken as TIFF format no longer supported
13
Use
Manager
10.1.5 Processing Software
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
Use
A container of information detailing the processing software used to edit or
transform the image data ; comprised as four data elements:
10.1.5.1 processingSoftwareName, 10.1.5.2 processing SoftwareVersion, 10.1.5.3
processingOperatingSystemName, 10.1.5.4 processing OperatingSystemVersion
Container
O
Y
Adobe Photoshop (software Name)
CS (Software Version)
Windows or Win (Operating System Name)
XP (operating System Version)
Containers may be repeated but individual elements may not
Manager
System
10.1.6 processingActions
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
Use
A data element that designates an ordinal listing of the image processing steps
performed by way of 10.1.5 ProcessingSoftware
String
R
Y
Editing ex: Rotate 90 degrees cw; ICC profile added
Transformation ex: Format migration from TIFF 6.0 to lossless JPEG 2000
Whenever possible, script or action files should be supplied for this element
Manager
10.2 Previous Image Metadata
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
A data element of technical metadata from previous generations of the image
file recorded to document provenance and change history and to provide
essential metadata that could be used to simulate return to original image data
(retains previous data types)
M (each time a new generation of the image is created)
Y
The metadata for the source file is recorded as a block in this section. Each
15
Backyard Botanicals Metadata Dictionary
Use
subsequent generation’s metadata is appended
Manager
User
Section 3: DUMD (Digital Underground Metadata)
*please see note
agentIdentifier
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
Notes:
Use
A data element that for this purpose identifies the name of the person who owns
the flowers in the photo and photographer, name of person who took the photo
String
O
Y
String
eventIdentifier
Definition
Type
Mandatory/Optional
Repeatable
Values
Ex:
A designation used to uniquely identify the event within the
preservation repository system.
String
Mandatory; *detail is optional
Yes*individual elements are not
For this dictionary three eventidentifiers exist that cover, separately, Dspace
date time, Dspace Detail, and Dspace Name; values below
dspacedatetime: Date/time uploaded to Dspace: YY-MM-DD HH:MM:SS format
dspacedetail: more info of what occurred during dspace session
dspacename: Name of person uploading to Dspace
Notes:
Use
*The fields used here are crafted after 2.1 and 3.1from Premis and tailored to meet the specific needs of
the group.
15