2. Group 3 – Cardinal Core Metadata Schema
Table of Contents
Introduction.............................................................................................................................................3
Purpose and Scope...............................................................................................................................3
Background.........................................................................................................................................4
Sources Consulted in Initial Planning Stage .........................................................................................5
Planning and Implementing Cardinal Core...............................................................................................5
Project Creation...................................................................................................................................5
Structural Development .......................................................................................................................6
Cardinal Core Application Profile............................................................................................................7
Element Descriptions...........................................................................................................................7
General Input Guidelines ...................................................................................................................18
Cataloging.............................................................................................................................................20
XML Encoded Records .....................................................................................................................20
Columbus Law School Courtyard Fountain, The Catholic University of America, Washington, DC20
Automobile Traffic, Sargent Road NE, Washington, DC................................................................22
Helicopter in Flight, District Heights, MD .....................................................................................23
Birds, Springfield Oaks, Springfield, Virginia ................................................................................25
Sources .................................................................................................................................................27
3. Group 3 – Cardinal Core Metadata Schema
Introduction
Purpose and Scope
The Cardinal Core metadata schema was developed with the intention of contributing
towards supporting audiovisual materials within digital archival collections. With an eye
towards the growing number of digital collections and the need to address new media within the
archival community, this schema will be used to describe, curate, and preserve the Sounds of our
Community collection. This is a grass roots project conducted by the Catholic University of
America (CUA) American Catholic History Research Center and University Archives. The
collection will consist of digital audio sound clips recorded in multiple locations around the
Washington, D.C. Metropolitan Area. Recordings may be of traffic, nature and wildlife,
construction, machinery, or human interactions. The audio files will be contributed by local
community members with an interest in preserving audio snapshots of the region in thirty second
sound bites. Categories of audio genre will be applied upon submission, via participant supplied
descriptive metadata. Acceptable format for the recordings include: mp3, OGG, mp4, wav, and
wma. The schema will allow for linking between audio files and related materials, such as map
images of the locations where sounds were captured and GPS coordinates of the locations. The
combination of maps and GPS coordinates will allow viewers to pinpoint where the sounds were
captured and look at the locations in relation to one another.
Anticipated user groups include the public, local historians, and those interested in
environmental history. The collection will be maintained and curated by a small staff at the
Catholic University of America. The size of the collection is dependent on the rate of community
participation, but will likely be limited to a few thousand recordings. Participants may contribute
as many files as desired, with a minimum of one file per submission. Submission is limited to a
maximum of twenty files per upload event.
4. Group 3 – Cardinal Core Metadata Schema
Background
In developing our schema, we looked to current best practices in the field.
Interoperability was a necessity, to enable use between multiple platforms and institutions. In the
past, schemas were largely developed for use within one institution. Today, with the growing
globalization of interaction between institutions, it is imperative that metadata schemas are able
to function in a way that enables the sharing of data and resources without unnecessary
headache. Controlled vocabulary ensures data is described correctly and consistently. Having
clear guidelines and standards within a schema enables metadata to be applied the same
everywhere by everyone. It lessens the likelihood that information will be lost or mismanaged
during the curation process.
Metadata schemas specifically geared towards digital audio collections are not nearly as
common as images or texts. Because digital audio is a fairly recent medium, development in
metadata for digital audio material is ongoing. The granular nature of audiovisual material
requires that applicable schemas allow flexibility of description within elements. Since our
collection is majority audio files, we wanted to find schemas that were widely used for the
implementation of metadata within digital collections. An investigation of similar ongoing
proects within the library and archival community revealed the use of METS, PBCore, and
MODS as common schemas. We were attracted to PBCore and MODS and used them to guide
our schema development.
Both PBCore and MODS have attractive elements that seem useful to curating digital
audio materials. Used by radio and television broadcasting stations, PBCore offers the ability to
describe analog and digital audio collections, so that they are easily searched, used, and shared
across different platforms. MODS offers the flexibility and granularity to be able to describe a
5. Group 3 – Cardinal Core Metadata Schema
variety of resources. MODS is often used in the library setting and is often compared to MARC,
though it’s element set is language based, while MARC is characterized by numeric values. In
addition to look at examples from these existing schemas, we incorporated customized elements
specific to our project, such as the ability to map to GPS coordinates.
Sources Consulted in Initial Planning Stage
ALA Metadata Standards and Guidelines Relevant to Digital Audio
http://www.ala.org/alcts/sites/ala.org.alcts/files/content/resources/preserv/audio_metadata.pdf
Archive.org – Audio https://archive.org/details/audio
The British Library Sounds - Environment http://sounds.bl.uk/Environment
The Cornell Lab of Ornithology, Macaulay Library – Building the Archive
http://macaulaylibrary.org/building-the-archive#audio-curation
Loyola University Chicago eCommons: Metadata for Digital Collections
http://ecommons.luc.edu/cgi/viewcontent.cgi?article=1001&context=lib_facpubs
Planning and Implementing Cardinal Core
Project Creation
The development of the Cardinal Core schema was an extensive project, which resulted
in more challenges than originally anticipated, but also helpful and beneficial solutions as well.
Challenges arose in multiple phases of the metadata schema development. The first challenge
arose during the creation phase. We, as the developers, unanimously agreed to focus on digital
audio materials, but there was no resolution regarding the end user group or project scope. Due
to the lack of this critical information, Cardinal Core required substantial modifications in order
to develop a tool that was both usable and relatable. Eventually, it was decided to specify two
end user groups, one being the primary user group and the other being the secondary user group.
6. Group 3 – Cardinal Core Metadata Schema
The primary user group was comprised of members of the District of Columbia
Metropolitan Area (D.C., Maryland, and Northern Virginia). Focusing on this primary user
group also resolved the issue of scope, because we were able to define and shape the schema,
based on our users anticipated needs. The secondary user group was local historians and those
interested in environment history. This user group was selected due to their possible interest
tracing history through audiovisual means. It would enable them to target specific communities
or locations for research purposes. The emergence of a definition of who we were serving and
how they may utilize the collection helped us to more adequately resolve other challenges that
arose in a more efficient manner.
Structural Development
The second group of challenges became evident during the structural development of
Cardinal Core. It became necessary for us to define what guidelines were necessary for our
schema. While there are many metadata schemas already in existence and many are already
being used successfully in repositories worldwide, we wanted to try to focus on drawing
inspiration from schemas that already worked well with audio materials. After some back and
forth discussion among team leaders and consultation of metadata best practices, it was
eventually agreed to use MODS and PBCore as examples of working schemas and to add
additional elements as needed. We appreciated the user friendly aspects of these two schemas.
Because our primary user group was defined as the general public, there may be a large number
of inexperienced users submitting files and inputting basic descriptive metadata. We wanted to
make the process as streamlined as possible. We settled on a total of nineteen elements.
In defining the elements associated with our schema, there was some uncertainty
involved with defining the cardinality and obligation of each piece. The majority of our elements
were decided to be required and repeatable, due to the level of granularity required for managing
7. Group 3 – Cardinal Core Metadata Schema
audio recordings. Additional challenges were user focused. There were concerns on how long
each audio recording should be and how many should be donated by any one person. It was
agreed that the required length be set at thirty seconds minimum, with a maximum length of one
minute. Due to the short audio recording length, we hoped to be able to support files of adequate
quality and quantity within our storage system.
Cardinal Core Application Profile
Element Descriptions
Below is the element description chart comprised of element set. The field name section,
on the left, will include information on the element name such as obligation, cardinality, and
whether it is searchable through the catalog interface. Obligation refers to whether the element is
mandatory and cardinality refers to whether it is repeatable. Dublin Core equivalency is noted in
relation to interoperability. The input data section, on the right will explain the definitions of the
element, its use and rules, controlled vocabulary values, examples, and sometimes tools and
references where applicable, in order to help decrease ambiguity.
1. Title
Required
Repeatable
Public (searchable)
DC (Title/Alternative Title)
The name given to a work or group of works that
identifies it
The contributor will add the title during the upload
process.
Multiple titles may be given, and should be separated
by additional <alternativeTitle> elements. The title
should not begin with articles such as ‘A’ or ‘The’.
Titles that are will be discarded.
2. Creator
Mandatory or Required
The person or organization responsible for creating or
capturing a media work.
8. Group 3 – Cardinal Core Metadata Schema
Repeatable
Public (searchable)
DC (Creator)
The contributor will add the creator during the upload
process.
There must be at least one, but there may be multiple
creators. Multiple creators should be separated by
additional <creatorInfo> elements.
If the creator is a person, the name should be entered
as: “Last Name, First Name, Middle Initial” followed
by the date of birth (and death if applicable). This helps
to distinguish John Speight born in 1945 from John
Speight born in 1990.
For Example:
Speight, John 1945-
If the creator is a group or organization, enter the name
of the group or organization, followed by the
department.
For Example:
Catholic University of America. Department of Library
Science.
Refer to the Library of Congress Authority Headings
for proper formats when applicable:
http://authorities.loc.gov/
If the Library of Congress Authorities is not applicable,
users may enter the group or organization simply by its
proper name.
3. Contributor
Mandatory or Required
Repeatable
Public (searchable)
DC (Contributor)
The contributor refers to a secondary creator, who may
have had a part in the creation of a sound. It may also
be the main creator. The contributor might be an editor,
an institution, or an individual. It may also refer to the
individual, institution or organization responsible for
donating the audio file to the repository.
The receiving institution will add this information upon
reception of the audio file.
4. Creation Date
9. Group 3 – Cardinal Core Metadata Schema
Mandatory or Required
Non-repeatable
Public (searchable)
DC (date created)
The creation date is the specific date on which the
recording originated. This is differentiated from the
date on which the item record entered the collection.
The user will add this information during the upload
process.
The W3CDTF (http://www.w3.org/TR/NOTE-
datetime) standard will help the user to format the date
and time correctly, in order to cut down on variable
entered data.
The ISO international Standard 8601 uses this site to
represent the date and time correctly. It expressed as
YYYY-MM-DD where years are YYYY, months are
MM, and days are DD.
For example, a sound recorded on October 2, 2013
would be expressed correctly by ISO Standard 8601 as
2013-10-02.
5. Upload Date
Mandatory/Required
Non-repeatable
Public (Searchable)
DC (record creation date or
date digital)
The date on which the audio work was submitted to the
collecting repository or captured as a digital entity
. The MODS schema expresses upload date as
“dateCaptured”. Upload date is differentiated from the
“creation date”.
This element is mandatory due to the importance of
documenting when a sound enters or is uploaded into
the collection. Upload date is non-repeatable. It will be
automatically applied via timestamp, at the time of file
upload.
The best tool used for controlled vocabulary is the W3
Consortium (http://www.w3.org/TR/NOTE-datetime)
for the proper date. The ISO international Standard
represents years as YYYY, months as MM, and days as
DD.
For example:
On November 6, 2013, an audio file was uploaded into
the collection. As expressed by the ISO Standard, the
proper way to display the Upload date would be years
(YYYY) – months (MM) – days (DD) or 2013-11-06.
6. Digital Origin
10. Group 3 – Cardinal Core Metadata Schema
Mandatory or Required
Unrepeatable
Public (searchable)
DC (Format)
The digital origin refers to the method by which a work
has become digital.
This would be supplied by contributing user during the
upload process.
The element is considered mandatory or required
because it is essential to get a better understanding of
the objects that are entered into the collection. Even
though most donated recordings will be considered
born digital, the origins of any converted or related
material will need to be identified. Items can be
identified as born digital, digitized, or converted from
microfilm, etc.
An appropriate controlled vocabulary tool to use would
be the AACR, allowing for proper punctuation and
capitalization. The acceptable terms would be “born
digital,” “digitized,” or “converted”.
For example:
An audio sound that has been recorded with an Apple
iPhone 4S would be considered “born digital”.
7. Collection Title
Mandatory or Required
Repeatable
Public (searchable)
DC (Title/Relation-Is-Part-Of)
The collection title is the name of a group of digital
works, considered to be
Each file will have at least one collection title: Sounds
of Our Community, which will be autofilled during the
upload process. Files belonging to a collection of the
creator relating to a theme or relationship may have a
second collection title, which will be supplied by the
user during the upload process.
Multiple collection titles will be separated by additional
collection title elements, which will function as user
supplied tags.
For example, “Saratoga in the Spring” may be the title
of a collection of files capturing the sounds of spring in
Saratoga, Springfield, Virginia.
Only the Sounds of Our Community collection title is
required.
11. Group 3 – Cardinal Core Metadata Schema
8. Location
Mandatory/Required
Repeatable
Non-Searchable
DC (Contributor)
Location describes the institution or repository where
the digital object or collection is held.
Location allows the public know where to go in order
to retrieve the collection. It is considered repeatable to
account for the amount of detail that the record creator
or donor wants to give, such as the full address.
For Example:
This collection Sounds of Our Community is held at
The Catholic University of America.
If the user wishes to add the full address of the
institution, he or she can utilize Google Maps
(http://maps.google.com). Once at the site, one can
enter Catholic University of America, and it will
retrieve an address for the institution.
For Example:
The location of our collection is: The Catholic
University of America. The full address would be: The
Catholic University of America
620 Michigan Ave Northeast
Washington DC 20064
9. Place
Mandatory or Required
Repeatable
Public (searchable)
DC (Coverage-spatial)
Place describes the physical location associated with
origin, production, or publication of a work. The place
where the sound was captured is expressed as a location
name.
Place should be differentiated from the “GPS
Coordinates” element where the coordinate are
expressed in latitude and longitude. It should also be
differentiated from the <location> element describing
the location of the collection or repository.
Using the Getty Thesaurus of Geographic Materials,
http://www.getty.edu/research/tools/vocabularies/tgn/,
you can enter in the place name and retrieve the
preferred term as well as the identification provided by
the Thesaurus.
For example:
12. Group 3 – Cardinal Core Metadata Schema
Enter “Brookland” into the Thesaurus and you will
retrieve its nested hierarchy laid out as World-North
and Central America-United States-DC-Washington
Another such tool is the USGS or the United States
Geographic Survey site (http://geonames.usgs.gov/).
One can enter in the area, place, neighborhood, or
institution and will be provided with the preferred name
along with other information.
For example:
Entering “Brookland” into the survey will provide the
elevation, its location within the District, as well as
other neighborhood landmarks such as elementary
schools or post offices.
A third useful tool for finding the exact location and
inserting into the metadata is Google Maps
(https://maps.google.com/). This tool will bring back
the physical address of the place where a sound was
recorded.
For example:
Catholic University of America address is as follows:
Catholic University of America
620 Michigan Ave NE, Washington, D.C.
20064
10. GPS Coordinates
Optional/Recommended if
available
Repeatable
Public (searchable)
DC (Coverage-spatial)
GPS Coordinates describes the location where a sound
was captured, expressed in latitude and longitude.
This element gives context to the digital work. The
information the coordinates provide will be useful for
our primary and secondary users.
The GPS Coordinates element is repeatable, allowing
for the entrance of different formats (degrees minutes
and decimal degrees) as well as for entering both the
latitudinal and longitudinal coordinates.
Using the Getty Thesaurus of Geographic Materials,
http://www.getty.edu/research/tools/vocabularies/tgn/,
you can enter the neighborhood where you recorded
your sound. It provides you an ID number as well as the
latitude and longitude coordinates. The Thesaurus
13. Group 3 – Cardinal Core Metadata Schema
expresses the coordinates as both in degrees minutes or
decimal degrees.
For example:
The “Brookland” neighborhood, located in
Washington, DC, is expressed as follows:
Degrees Minutes:
Latitude 38 55 00 N
Longitude 076 59 00 W
Decimal Degrees:
Latitude 38.9167
Longitude and -76.9833
It is essential to remember to differentiate between the
two expressions.
Another such tool is the use of the United States
Geographical Survey Geographic Name Information
System http://geonames.usgs.gov/. Enter in the Name
of Institution, the State, or County. It provides you with
the class of institution or place, the County, as well as
the latitude or longitude coordinates.
For example:
Catholic University of America coordinates are as
follows:
Degrees Minutes:
Latitude 38 55 59 N
Longitude 076 59 52W
11. Description
Mandatory/Required
Repeatable
Unsearchable
DC (Description or Abstract
Description)
The description element provides a physical description
of the work.
This is user supplied information, conveyed during the
upload process. It is required that the user describe the
contents of the file, along with the equipment used.
Although this will be free text, use of the AACR will
help provide rules for syntax and should be used. The
user should provide as lengthy descriptions as
necessary to fully explain the importance of the sound’s
inclusion into the collection. The archivists will then
clean up the supplied description for display purposes.
For Example:
14. Group 3 – Cardinal Core Metadata Schema
This sound was recorded at the Pryzbla student center
at Catholic University of America. It was during the
rush lunch period causing it to be rather packed and
raucous. You can hear murmuring voices throughout.
At 00:28 seconds, high heels dominate the recording as
they approach the recording device.
The recording device was an Apple iPhone 4S, using
the Camera application available through software iOS
6.
12. Subject
Optional; Recommended
Repeatable
Public (searchable)
DC (Subject)
This element refers the primary topics on which a work
is focused. It may include: keywords, phrases,
individuals, places, events, or other descriptive words
which help categorize the work.
Some descriptive words or phrases that could be helpful
in describing the subject’s topic would include
community and events, landscape and nature, recreation
and social life, and industry.
The subject element will be supplied by the archivists
upon reception of file uploads. It will be based on the
description.
The words or phrases used to describe the subject are
standardized according to the Library of Congress
Subject Heading format. Since the topics are local in
nature and may be unique to specific neighborhoods, it
is possible that some subjects may not be found in the
LCSH or any other national thesaurus.
However, it is recommended when possible to use the
Library of Congress Subject Headings. The LSCH can
be found at (http://id.loc.gov/authorities/subjects.html).
After entering the keyword or phrase, one must choose
from the menu beneath and choose the appropriate
subject heading.
For Example:
One recording was of an outdoor fountain.
According to the LCSH, the topical subject of the
sound would be “water”.
13. Publisher
15. Group 3 – Cardinal Core Metadata Schema
Mandatory/Required
Non repeatable
Public (searchable)
DC (Publisher)
Publisher refers to the person, group, or organization
who distributes or makes the file available. If the
creator is the publisher, then the creator will be entered
in as the publisher.
This element will be applied by the receiving
institution.
There must be at least one, and only one publisher.
Formatting is the same as it is for contributor. Refer to
Creator input data or the Library of Congress Authority
Headings for proper formats when applicable:
http://authorities.loc.gov/
14. Type
Mandatory/Required
Repeatable
Non-searchable
DC (Type/Format)
Type refers to the format of the content file received or
the type of resource.
This element will be added by the receiving institution.
While the content in our collection will be a majority
the same type, the formats may be different. This will
be repeatable allowing for the user to enter information
on both the type and format of the object in the
collection.
The best controlled vocabulary for our users to utilize
for type is the tool DCMI Type Vocabulary
(http://dublincore.org/documents/2000/07/11/dcmi-
type-vocabulary/.) This allows the end user to use the
proper term for type. In order to use this tool, one can
click on the Sound and the site will provide the user
with a definition.
For Example:
The type of object donated would be “audio”.
The best controlled vocabulary for format our users to
utilize is IMT or Internet Media types. This is a set of
media types specified by the Internet Assigned
Numbers Authority
(http://www.iana.org/assignments/media-types/). Select
the audio section and a list of types will appear. Find
your format type and include it in the record.
16. Group 3 – Cardinal Core Metadata Schema
For Example:
An audio/MPEG 4 file.
Using the IMT, one can find that the audio/MPEG 4
generic is the correct way to list its format and thus can
be entered into the collection.
15. Length
Recommended if available
Repeatable
Non-searchable
DC (Coverage-temporal)
The number and material of work expressed physically
or extent of work expressed in hours and minutes. It is
described as “extent” in the MODS schema.
Provided by the user during the upload process. It will
be automatically converted to the proper format by the
system.
The element, while recommended, really is necessary
due to the ease with which this information is given to
the recorder. Recording devices that provide length of
time should be included. The date and time along with
the extent of the recording should also be included.
The W3 tool is the best to use in order to give an
accurate description of the length or extent of a
recorded sound and can be found at the W3
Consortium, http://www.w3.org/TR/NOTE-datetime.
The ISO international Standard uses this site to
represent the date and time correctly. It includes years
(YYYY), months (MM), days (DD), hours (hh),
minutes (mm), seconds (ss), miliseconds or fractions of
seconds (s) as well as the time zone designator (TZD).
There are many tools to find the time zone where your
community is located. One tool is the World Time
Server
(http://www.worldtimeserver.com/current_time_in_US-
DC.aspx).
For Example:
One sound was recorded on September 25, 2013 at
9:15:00 PM, Eastern Standard time. The proper way to
display as dictated by the W3 Consortium would be
2013-09-15T21:15:00-04.
In order to fully identify the extent of a recording, both
the start and stop time need to be established.
18. Group 3 – Cardinal Core Metadata Schema
Non-searchable
DC (Relation/Relation-Is-Part-
Of)
This would be supplied by archivists at the hosting
repository.
For example, if John Smith, creator, has multiple files
he has authored, each of them would connect to the
others. Other content such as photographs, maps, or
GPS coordinates, which help to provide context to the
audio files would be listed within this element as well.
19. Notes
Optional
Non-repeatable
Non-Searchable
DC (Description)
This allows for the input of additional information
related to the work that is not covered by other
metadata elements.
It is expected that the user will add any pertinent
information to a file as they seem necessary. Archivists
may also add additional notes.
For Example:
If a user wants to add additional information about the
conditions, environment, or context of the recorded
sound, they may do so here.
General Input Guidelines
Data value specifications include text, numbers, and punctuation symbols in order to
accommodate all symbols used in titles, and other important content.
The field size designation states that users can utilize as many characters as needed. We
opted not to limit character input, because limiting the number of characters makes it more
difficult to adequately enter essential information. A flexible size is important to be able to enter
all necessary information. However, it is also important for users to keep in mind that not all
information may be appropriate for a given field. Additional information may be added in the
repeatable Notes element. All elements are searchable and visible to the public unless noted.
19. Group 3 – Cardinal Core Metadata Schema
Users can utilize abbreviations, acronyms, etc., if it will help increase the searchability of
files. However, abbreviations need to spelled out somewhere within the bibliography. Users can
capitalize when needed in order to be precise. Any title articles such as ‘a’, ‘the’, or ‘and’ at the
beginning of a title should be omitted.
The title, date, and other variants would be handled within the element set, with the
addition of a separate, specific element. For example, the element “alternate title” should be used
for the inclusion of alternate titles.
20. Group 3 – Cardinal Core Metadata Schema
Cataloging
XML Encoded Records
Columbus Law School Courtyard Fountain, The Catholic University of America,
Washington, DC
<?xml version=“1.0” encoding=“utf-8”?>
<Sound1>
<titleInfo>
<CollectionTitle>
<display>Collection Title: Sounds of Our Community</display>
<title>Sounds of Our Community</title>
</CollectionTitle>
<RecordingTitle>
<display>Recording Title: Columbus School of Law Courtyard Fountain</display>
<title>Columbus School of Law Courtyard Fountain</title>
</RecordingTitle>
</titleInfo>
<creatorInfo>
<display>Katherine Greene, Recorder</display>
<name type="personal">
<namePart>Greene, Katherine</namePart>
<role>Recorder</role>
</name>
</creatorInfo>
<ContributorInfo>
<display>The Catholic University of America, Contributor</display>
<name type="institution">
<namePart>Catholic University of America</namePart>
<nonsort>The</nonsort>
<role>Contributor</role>
</name>
</ContributorInfo>
<OriginInfo>
<display>Date Created: September 25, 2013</display>
<dateCreated encoding="w3cdtf">2013-09-25</dateCreated>
<display>Date Uploaded to Repository: November 06, 2013</display>
<uploadDate encoding="w3cdtf">2013-11-06</uploadDate>
<digitalOrigin>Born Digital</digitalOrigin>
</OriginInfo>
<physicalDescription>
<display>Object Type: Sound</display>
<type>Sound</type>
<display>Format: MP4</display>
<format>MP4 Audio</format>
21. Group 3 – Cardinal Core Metadata Schema
<display>Start Time: 2:15:00 PM</display>
<display>Stop Time: 2:15:31 PM</display>
<length encoding="w3cdtf">
<start>2013-09-25T21:15:00-04:00</start>
<stop>2013-09-25T21:15:31-04:00</stop>
</length>
<display>Repository is Located at the Catholic University of America 620 Michigan Ave NE
Washington, DC 20064</display>
<location type="institution">
<name>Catholic University of America</name>
<nonsort>The</nonsort>
<address>620 Michigan Ave Northeast Washington DC 20064</address>
</location>
</physicalDescription>
<UniqueIdentifier>
<ID>00001</ID>
</UniqueIdentifier>
<SubjectInfo>
<subject>
<display>Topical Subject: Water</display>
<topic encoding="lcsh">Water</topic>
<display>Geographic Subject: The Catholic University of America 620 Michigan Ave NE,
Washington, D.C. 20064</display>
<place>The Catholic University of America 620 Michigan Ave NE, Washington, D.C.
20064</place>
<display>latitude: 38 55 59N</display>
<display>longitude: 076 59 52W</display>
<coordinates type="gnis">
<latitude type="degrees minutes">385559N</latitude>
<longitude type="degrees minutes">0765952W</longitude>
</coordinates>
</subject>
</SubjectInfo>
<DescriptionInfo>
<display>There was quiet conversation not heard above the fountain. The recording device
was an iPhone 4s using iOS 6.</display>
<description>It was mid-afternoon and rather quiet. The fountain was working really well
and it comes out clearly in the recording. There was quiet conversation but you can't hear
it above the fountain. The sound was recorded with iPhone 4s Voice Memos application
on iOS 6.</description>
</DescriptionInfo>
<AccessCondition>
<display>Catholic University of America. All Rights Reserved</display>
<provenance>Catholic University of America. All Rights Reserved.</provenance>
</AccessCondition>
</Sound1>
25. Group 3 – Cardinal Core Metadata Schema
<description>Military helicopter flies overhead of Seacrest Village apartment
building at 12:40pm. It likely is affiliated with nearby Joint Base Andrews. Other
sounds heard include insect chirping.<description>
</DescriptionInfo>
<AccessCondition>
<display>Catholic University of America. All Rights Reserved</display>
<provenance>Catholic University of America. All Rights
Reserved.</provenance>
</AccessCondition>
</Sound3>
Birds, Springfield Oaks, Springfield, Virginia
<?xml version=“1.0” encoding=“utf-8”?>
<Sound4>
<titleInfo>
<CollectionTitle>
<display>Collection Title: Sounds of Our Community</display>
<title>Sounds of Our Community</title>
</CollectionTitle>
<RecordingTitle>
<display>Recording Title: Birds</display>
<title>Birds</title>
</RecordingTitle>
</titleInfo>
<creatorInfo>
<display>Sean Ryan, Recorder</display>
<name type="personal">
<namePart>Ryan, Sean</namePart>
<role>Recorder</role>
</name>
</creatorInfo>
<ContributorInfo>
<display>The Catholic University of America, Contributor</display>
<name type="institution">
<namePart>Catholic University of America</namePart>
<nonsort>The</nonsort>
<role>Contributor</role>
</name>
</ContributorInfo>
<OriginInfo>
26. Group 3 – Cardinal Core Metadata Schema
<display>Date Created: September 27, 2013</display>
<dateCreated encoding="w3cdtf">2013-09-27</dateCreated>
<display>Date Uploaded to Repository: November 06, 2013</display>
<uploadDate encoding="w3cdtf">2013-11-06</uploadDate>
<digitalOrigin>Born Digital</digitalOrigin>
</OriginInfo>
<physicalDescription>
<display>Object Type: Sound</display>
<type>Sound</type>
<display>Format: MP3</display>
<format>MP4 Audio</format>
<display>Start Time: 6:00:00 PM</display
><display>Stop Time: 6:00:32 PM</display>
<length encoding="w3cdtf">
<start>2013-09-27T18:00:00-06:00</start>
<stop>2013-09-27T18:00:32-06:00</stop>
</length>
<display>Repository is Located at the Catholic University of America 620 Michigan Ave NE
Washington, DC 20064</display>
<location type="institution">
<name>Catholic University of America</name>
<nonsort>The</nonsort>
<address>620 Michigan Ave Northeast Washington DC 20064</address>
</location>
</physicalDescription>
<UniqueIdentifier>
<ID>00004</ID>
</UniqueIdentifier>
<SubjectInfo>
<subject>
<display> Topical Subject: Birds</display>
<topic encoding="lcsh">Birds</topic>
<display>Geographic Subject:Springfield Oaks, Springfield, Virgina</display>
<place>Springfield Oaks, Springfield, Virgina</place>
<display>latitude: 38 43 40.7676</display>
<display>longitude: -77 12 17.1036</display>
<coordinates type="gnis">
<latitude type="degrees minutes">384340.7676</latitude>
<longitude type="degrees minutes">-771217.1036</longitude>
</coordinates>
</subject>
</SubjectInfo>
27. Group 3 – Cardinal Core Metadata Schema
<DescriptionInfo>
<display>Hundred of bird gather at the same tree in Springfield Oaks at 6 p.m. every day,
chirping and singing, and make the sidewalk dirty. The recording was made using the Samsung
Galaxy S3 cell phone.</display>
<description>Hundred of bird gather at the same tree in Springfield Oaks at 6 p.m. every day,
chirping and singing, and make the sidewalk dirty. The recording was made using the Samsung
Galaxy S3 cell phone.</description>
</DescriptionInfo>
<AccessCondition>
<display>Catholic University of America. All Rights Reserved</display>
<provenance>Catholic University of America. All Rights Reserved.</provenance>
</AccessCondition>
</Sound4>
Sources
Brooks, M et al. Public Broadcasting Metadata Dictionary Project. 2011. Last Retrieved on
December 1, 2013. Retrieved from http://pbcore.org/elements/
Baker, T; Ruhle, S; Johnston, P. Dublin Core Metadata Initiative. Modified last September 26,
2011. Last Retrieved on December 1, 2013. Retrieved from Metadata Object
Description Schema. Last Retrieved on December 1, 2013. Retrieved from
http://www.loc.gov/standards/mods/
The British Library Board. British Library. Last Retrieved on December 1, 2013. Retrieved from
http://sounds.bl.uk/Environment
Delaware Division of Libraries (7/30/2013). Delaware Heritage Collection Metadata
Supplement: Local Implementation of CDP Dublin Core Metadata Best Practices
Version 2.1.1.1-25. Last Retrieved on December 1, 2013. Retrieved from
http://libraries.delaware.gov/news2013/DE_Heritage_MetadataSupplement_07_2013.pdf
Getty Research Institute. Getty Thesaurus of Geographic Names. Last Retrieved on December 1,
2013. Retrieved from http://www.getty.edu/research/tools/vocabularies/tgn/
Library of Congress. Library of Congress Subject Headings. Last Retrieved on December 1,
2013. Retrieved from http://id.loc.gov/authorities/subjects.html
Library of Congress. Metadata Object Description Schema. Last Modified July 9, 2013. Last
Retrieved on December 1, 2013. Retrieved from http://www.loc.gov/standards/mods/
Miller, S. Metadata for Digital Collections. Neal-Schuman Publishers Inc. New York, 2012.
United States Geographic Survey. Geographic Names Information System. Last Retrieved on
December 1, 2013. Retrieved from http://geonames.usgs.gov/pls/gnispublic
28. Group 3 – Cardinal Core Metadata Schema
W3 Consortium. Last modified September 15, 1997. ISO 8601. Last Retrieved on December 1,
2013. Retrieved from http://www.w3.org/TR/NOTE-datetime
