DALNET DIGITAL METADATA

1
DALNET DIGITAL METADATA

• Progress Report
• IHDC Metadata Task Force
• March 22, 2002

2
CHARGE

• develop an information architecture that
  incorporates and integrates the diverse resources
  of the Dalnet Im_at_gine Information Hub

3
TASKS

• Formulate, evaluate, endorse appropriate data
  standards

4
Environmental Factors

• Dalnet Information Infrastructure

5
Environmental Factors

• Dalnet Information Infrastructure
• Potential Projects

6
Environmental Factors

• Dalnet Information Architecture
• Potential Projects
• Legacy Data Systems

7
Environmental Factors

• Dalnet information architecture
• Potential projects
• Legacy data systems
• New and evolving data systems

8
Constraints

• No final answers

9
Constraints

• No final answers
• No one-size-fits-all answers

10
Constraints

• No final answers
• No one-size-fits-all answers
• No one answer

11
Results

• Pathway not a destination

12
Results

• Pathway not a destination
• Customizable metadata choices

13
Results

• Pathway not a destination
• Customizable metadata choices
• Integration of metadata

14
Results

• Pathway not a destination
• Customizable metadata choices
• Integration of metadata
• Standards-based approach

15
Results

• Pathway not a destination
• Customizable metadata choices
• Integration of metadata
• Standards-based approach
• Hybrid data structures

16
Implications

• The on-going involvement and oversight of the
  DALNET Data Standards Committee or an equivalent
  group will be necessary for consistent
  development of the information instructure.

17
DALNET Information Architecture Model 1
DALNET WEBSITE/IHDC GATEWAY Links to iPacs
Digital databases
IPAC 1
IPAC 3
IPAC 2
Horizon Digital Metadata
Horizon Bib DB
Horizon Digital Metadata
Horizon Digital Metadata
Horizon Bib DB
Horizon Digital Metadata
Horizon Bib DB
Horizon Digital Metadata
Local Image Server
DALNET Image Server
18
Example

• Smithsonian Horizon Catalog
• Siris

19
Model 1 Issues

• Pros
• Can be done now
• No additional software
• Uses Marc-based metadata

• Cons
• Lacks high-level integration
• Lacks flexibility for diverse projects
• Uses only Marc based Metadata

20
DALNET Information Architecture Model 2
Library 2 Website
DALNET WEBSITE/IHDC GATEWAY Links to iPacs
Digital databases
Library 1 Website
iPAC 1
iPAC 2
Digital Metadata
Digital Metadata
Horizon Bib DB
Horizon Bib DB
Image Server
21
Example

• Willliam Blake Archive
• IATH Website listing
• University of Virginia Virgo Catalog

22
Model 2 Issues

• PROS
• Can be done now
• Requires no additional DALNET software
• Flexible
• Customizable

• Cons
• Lacks high-level integration
• Access becomes more complex as number of
  databases grows

23
DALNET Information Architecture Model 3
Unified Searching Interface
Integrated Search Engine
Library Marc DB
Marc Digital Metadata
Library Marc DB
Non-Marc Digital Metadata
Non-Marc Digital Metadata
Non-Marc Digital Metadata
Image Server
24
Model 3 Issues

• Pros
• Provides high-level access
• Permits individual access
• Accommodates diverse metadata needs

• Cons
• Requires additional DALNET software
• Requires careful monitoring of emerging standards

25
Critical Path

• Models are not exclusive

26
Critical Path

• Models are not exclusive
• Model 3 is the ultimate destination

27
Critical Path

• Models are not exclusive
• Model 3 is the ultimate destination
• Models 1 2 represent interim strategy

28
Critical Path

• Models are not exclusive
• Model 3 is the ultimate destination
• Models 1 2 represent interim strategy
• Models 1 2 must be used with Model 3 in mind

29
Current Reality

• Model 1 UDM Shipping Database

30
Current Reality

• Model 1 UDM Shipping Database
• Model 2 Health Calendar

31
Steps to a Successful Transition

• Make careful indexing choices

32
Steps to a Successful Transition

• Make careful indexing choices
• Data that integrates at the semantic level

33
Steps to a Successful Transition

• Make careful indexing choices
• Data that integrates at the semantic level
• Use standardized data-encoding

34
MTF Strategies

• 1. Dalnet Data dictionary
• Provides access and description elements at
  present
• Accommodates digital vs. original
• Maps to current standards
• Extendable
• Adaptable to multiple formats

35
MTF Strategies

• Data Systems
• Marc21 Core record elements (www.loc.gov/marc/
• Dublin Core Element Set (dublincore.org)
• Encoded Archival Description (EAD)
  (www.loc.gov.ead/)
• CDWA (www.getty.edu/research/institute/standards/c
  dwa/index.html)
• VRA Core (www.vraweb.org/vracore3.htm)

36
MTF Strategies

• 2. Data Entry Template
• Based on Data Dictionary
• Saves to MARC or RDF-XML

37
MTF Strategies

• 2. Data Entry Template
• Based on Data Dictionary
• Saves to MARC or RDF-XML
• 3. Simple authority procedure
• Insure consistency within DALNET

38
Oversight Tasks

• On-going DALNET group (Data Standards Committee?)

39
Oversight Tasks

• On-going DALNET group (Data Standards Committee?)
• Provide assistance

40
Oversight Tasks

• On-going DALNET group (Data Standards Committee?)
• Provide assistance
• Permit custom approach

41
Oversight Tasks

• On-going DALNET group (Data Standards Committee?)
• Provide assistance
• Permit custom approach
• Enable integration

42
Future Tasks

• Develop consistent file-naming protocols

43
Future Tasks

• Develop consistent file-naming protocols
• Extend data dictionary

44
Future Tasks

• Develop consistent file-naming protocols
• Extend data dictionary
• Evaluate new standards

45
Future Tasks

• Develop consistent file-naming protocols
• Extend data dictionary
• Evaluate new standards
• Explore issues of authority control across
  diverse databases

46
Future Tasks

• Develop consistent file-naming protocols
• Extend data dictionary
• Evaluate new standards
• Explore issues of authority control across
  diverse databases
• Monitor infrastructure developments re metadata

47
Dalnet Data Dictionary

• Access and description

48
DALNET Data Dictionary

• Access and description
• Semantic values

49
DALNET Data Dictionary

• Access and description
• Semantic values
• Few syntactical rules

50
DALNET Data Dictionary

• Access and description
• Semantic values
• Few syntactical rules
• No data transmission standard specified
• MARC, XML vs. proprietary formats
• Z39.50 tag sets (Bib-1 CIMI)

51
Data Dictionary Components

• Name of element

52
Data Dictionary Components

• Name of element
• Required or not required

53
Data Dictionary Components

• Name of element
• Required or not required
• Digital original or digital reproduction vs.
  original resource

54
Data Dictionary Components

• Name of element
• Required or not required
• Digital original or digital reproduction vs.
  original resource
• Definition

55
Data Entry Tool

• Saves to MARC or RDF-XML

56
Data Entry Tool

• Saves to MARC or RDF-XML
• Requires no knowledge of specific standards

57
Data Entry Tool

• Saves to MARC or RDF-XML
• Requires no knowledge of specific standards
• Requires minimal training

58
Data Entry Tool

• Saves to MARC or RDF-XML
• Requires no knowledge of specific standards
• Requires minimal training
• Based on data dictionary

59
Data Mapping

• Integrate indexes

60
Data Mapping

• Integrate indexes
• Select data elements

61
Data Mapping

• Integrate indexes
• Select data elements
• Move data