[Slide stating problem] - PowerPoint PPT Presentation

1 / 8
About This Presentation
Title:

[Slide stating problem]

Description:

Title: Appropriateness (using DC for objects that are not information resources) Author: Carl Lagoze Last modified by: Thomas Baker Created Date – PowerPoint PPT presentation

Number of Views:36
Avg rating:3.0/5.0
Slides: 9
Provided by: CarlL170
Learn more at: http://eprints.rclis.org
Category:

less

Transcript and Presenter's Notes

Title: [Slide stating problem]


1
Slide stating problem
2
Appropriateness misusing DC to describe
"people" or "places"
  • Possible solution
  • Evaluate appropriateness element-by-element
    relative to entities described
  • At a minimum, Identifier and Type ("Person")?
  • Helps users decide utility of resources
  • Guidance, type-by-type, on appropriate usage
  • Use protocol to express preference for richer
    formats (see below)

3
Quality of metadata content
  • "Junk" records make junky indexes
  • Responses
  • Junk metadata problem broader than just DC!
  • Better tools, interfaces, partitioned workflows
    for metadata creation and quality control
  • Better guidelines for use of DC in specific
    communities
  • DC useful not just for indexing, but listing and
    browsing results

4
Quality too-broad semantics
  • Intrinsic problem with DC?
  • Broad, fuzzy buckets inevitably hold diversity
  • Harvester must sometimes guess context e.g.,
    dcidentifier, dcsubject
  • Proliferation of more-specific elements/qualifiers
    would increase complexity
  • Rather, recommended constraints, e.g.,
    "dcidentifier should be a URI"

5
Effort stopping short of providing richer
metadata
  • Problem
  • People with rich metadata dumbing down to DC
  • People with no metadata make DC then stop, even
    if DC is not ideal
  • Responses
  • Promote richer metadata parallel to DC
  • Point to preferred metadata from about container
    for required DC format
  • Or consider DC "non-preferred" by default (most
    cases)

6
Examples of richer formats
  • LOM
  • MARC
  • Academic metadata format (AMF)
  • RDF combination of multiple metadata formats
  • OLAC

7
Group mood summary
  • Keep Dublin Core mandatory
  • Encourage use of richer formats
  • Support indication of "preferred" formats
  • Constrain too-broad elements with usage
    recommendations ("use a URI for dcidentifier")
  • Explain how to use DC with non-document-like
    resources (just Identifier/Type?)

8
Issues
  • Constraint that no solution can invalidate
    current implementations
  • Issue of empty DC records that are actually
    compliant
Write a Comment
User Comments (0)
About PowerShow.com