View
44
Download
0
Category
Preview:
DESCRIPTION
NPS Bibliographic Metadata Exchange Standard (NPS-BMES) & Application Profile (NPS- BibMAP ). Dry Tortugas. Vietnam Veterans. WHAT’S IN A NAME ?. BMES Proposed standard to facilitate bibliographic metadata exchange B ibliographic M etadata E xchange S tandard - PowerPoint PPT Presentation
Citation preview
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
Amalin FergusonNPS Library Program Manager
NPS RIM Conference, Reference Management Session
Ft. Collins, Colorado, April 22nd, 2010
Dry Tortugas
NPS Bibliographic Metadata
Exchange Standard (NPS-BMES)
&Application Profile
(NPS-BibMAP)
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
WHAT’S IN A NAME ? BMES Proposed standard to facilitate
bibliographic metadata exchange
Bibliographic
Metadata
Exchange
Standard
BibMAP Recommended application of
the bib metadata standard
Bibliographic
Metadata
Application
Profile
Petrified ForestVietnam
Veterans
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
WHAT’S THE POINT ? Problem #1 – Metadata Quality
who, what, where, when
info resource verification
info resource relevancy
info resource usability
info resource location
Problem #2 – Efficiencyuniform guidance for core metadata creation
core metadata sharing, reuse + repurpose
discovery + retrieval via federated searching
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
WHO SHOULD CARE ?
NPS information architects Bib metadata-related positions
- program area managers
- systems developers/managers
- stewards and curators
- policy makers + standards developers
- guidance developers + trainers
- creators (mostly indirectly)
- end users (always indirectly!)
Appomattox Court House
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
GROUNDWORK
Current Awareness & Research
metadata concepts + terms
metadata authorities
metadata SME resources
issues, initiatives & trends
Surveys & Interviewsmajor NPS stakeholders
NPS bib applications
metadata standards
best practices + encoding schemes
application profile documentsDry Tortugas
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
CORE FRAMEWORKBMES element set based on Dublin Core
(DC) widely used + supported descriptive metadata set
element order not relevant - all elements may repeat
qualified DC (QDC) accommodates element ‘refinements’
Key principles for use of DC endorsedone to one = 1 resource, 1 record
dumb down = QDC value meaningful for simple DC
NPS BibMAP for content guidelinesincorporates + expands upon DC-Lib app profile
element definition, occurrence, obligation (some raised)
recommended encoding schemes for applicable elements
best practices + examples for content creation
XML export for machine-readable exchange
Hawai’i Volcanoes
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
ELEMENT SET Title (M) Identifier (MA)
Creator (MA) Source
Contributor (MA) Language (MA) Publisher (MA) Relation
Subject (MA) Coverage *
Description Rights (MA) Date (MA) Audience**
Type (M) Edition (MA) Format * Location (MA)
* may consider elevating obligation status
** added to Simple DC, along w/ Rights Holder & Provenance, to constitute Qualified DC
italicized elements borrowed’ from Metadata Object Description Schema (MODS) maintained by LC underlined elements are those for which best practice recommends encoding schemes be used
National Register
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
Element Refinements Title (1) - alternative (i.e., alternative title)
Description (2) - abstract, table of contents
Date (9) - created, valid, available, issued, modified …
Format (2) - extent, medium
Identifier (1) - bibliographic citation
Relation (10) - is version of, is part of, replaces …
Coverage (2) - spatial, temporalUSS Arizona
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
TITLE ELEMENT RULES• Transcription source for book Title is title page (not cover/spine)• Transcribe Title as it appears on title page – w/o punctuation• Capitalize first letter of first word and proper nouns only• Exception is conference proceedings (conf. name is entity)• Use space colon space to separate Title proper from subtitle• Repeat Title element to capture parallel titles (e.g., trans.)• Option to add LC GMT or local genre term as subtitle -
enclose in square brackets, e.g. < : [completion report] >• Use refinement Alternative (alt. title) for other forms of Title• Use appropriate Relation element refinement for Series Title• Ditto if work (e.g., book chap., journal art.) is part of larger
work (e.g., book, whole journal) or vice versa – has part• Use Bibliographic Citation (refinement of Identifier element ) to capture full citation for journal article• Best practice points to AACR2/RDA for fuller guidance
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
• Use refinements of the Date element for diff date types
• Date Created is the only mandatory Date refinement
• Best practice recommends ISO 8601 standard for (syntactic) encoding scheme for dates, e.g.
YYYY
YYYYMMDD or YYYY-MM-DDYYMM not YY-MM
• Best practice points to AACR2/RDA for fuller guidance
DATE ELEMENT RULES
Wilson’s Creek
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
TYPE ELEMENT RULES• The Type element obligation status is mandatory
• Best practice says use a semantic encoding scheme - controlled term/vocabulary list - for the Type element
• Repeat the Type element for multiple types + schemes
• Ideally the ID for the Type encoding scheme is included
in the metadata and is itself drawn from a controlled list
• Best practice - select at least one term from DCMI TypesCollection Image SoftwareDataset Interactive Resource Sound
Event Service TextCatoctin Mountain
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information OfficerSUBJECT ELEMENT -
XMLStatement (
Property URI (dc:subject)
Vocabulary Encoding Scheme URI (dcterms:LCSH)
Value String (“Conservationists--United States--Biography”)
)
Statement ( Property URI (dc:subject)
Vocabulary Encoding Scheme URI (dcterms:LCNA)
Value String (“Muir, John, 1799-1833”)
)
Statement (
Property URI (dc:subject)
Value String ("polar oceanography”)
)
[example adapted from Scholarly Works Application Profile – SWAP (a DC app profile)]Muir Woods
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
BMES/BIBMAP CO-OP
• Review and comment on BibMAP draft iterations
• Consensus re elements with Mandatory (M/MA) obligation
• Consensus re encoding schemes for (M/MA) elements
• Collaborative guidance development for (M/MA) elements
• Collaborative decision tree/workflow
• Central guidance/service portal for bib metadata creators
Jefferson National
Expansion
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
BIBMAP APPROVAL04/01 – working draft posted
04/30 – working draft comments due (ext?)
07/31 – review draft posted (est.)
08/31 – review draft comments due (est.)
09/30 – final draft (vers.1) submitted (est.)
12/31 – final draft (vers.1) approved (est.)
Luna Moth Catoctin
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
WHERE’s BIBMAP ? RIM (i.e. RISD) SharePoint site http://portal.nps.gov:46840/RIM/default.aspx
• All Standards list on left nav bar
• Standards > Metadata in right pane
• NPS BibMAP row on list
• NPS BibMAP docs column (for doc)
• NPS-BibMAP review column (for list)
• New tab to submit comments to list
[for updates on biblio metadata matters, see new DIS Front Page (pending) on RISD SharePoint site]Manassas
National Park ServiceU.S. Department of the Interior
Resource Information Services DivisionNational Information Systems CenterOffice of the Chief Information Officer
BEYOND NPS-BibMAP
• Enterprise, lifecycle approach to digital assets creation + management (not just metadata…)
• Enterprise Metadata Framework Portalwith standards, registries, guidance, tools …
• Enterprise Federated Search
Stones River
Thanks for your attention !!
Recommended