innovation in metadata design, implementation & best practices

Title: Use of metadata at http://dublincore.org - a proposal
Identifier: http://dublincore.org/usage/meetings/2004/03/ISSUES/dublincore-org/
Date: 2004-03-10
Author: Tom Baker

The DCMI Web site currently has metadata records for more
than 700 individual items -- many of which are long-obsolete
working drafts. As a result, users searching the DCMI site are
presented with many irrelevant hits, and the genuinely useful
resources are hard to find. Moreover, the DCMI Web site is 
not well integrated into the OAI world. I propose we remedy
this situation by doing the following:

1) We create a list 50 to 100 "key" resources for which DCMI
   can commit to maintaining excellent metadata (see Appendix
   A below). DCMI would keep the short-list up-to-date and use
   it for periodically checking the freshness of metadata.
   The records for these 50 to 100 key resources would
   have good and exhaustive keywords, accurate dates, and
   abstract-length descriptions.

2) We delete the metadata for all other resources (or at any
   rate rename the *.rdf metadata files so they will not be 
   captured in the search index).

3) It would seem that Web sites (like DCMI's) with small
   numbers of documents to expose can now do this as an "OAI
   Static Repository" (see Appendix B below) -- perhaps by
   converting the RDF metadata into the XML schema "oai_dc",
   concatenating the schemas in one big XML file, and making
   that file available to OAI Static Repository harvesters.

4) If we get this far and the approach works well, we should
   not neglect to describe this method in a small document
   to be posted on the DCMI Web site.

------------------------------------------------------------------------
APPENDIX A: Best candidates for metadata
------------------------------------------------------------------------

http://dublincore.org/
http://dublincore.org/about/
http://dublincore.org/about/bylaws/ - doesn't exist yet
http://dublincore.org/about/copyright/ -- no metadata yet
http://dublincore.org/banners/
http://dublincore.org/dcregistry/ -- no metadata yet
http://dublincore.org/documents/
http://dublincore.org/documents/dc-xml-guidelines/
http://dublincore.org/documents/dces/
http://dublincore.org/documents/dcmes-xml/
http://dublincore.org/documents/dcmi-box/
http://dublincore.org/documents/dcmi-dcsv/
http://dublincore.org/documents/dcmi-ieee-mou/
http://dublincore.org/documents/dcmi-namespace/
http://dublincore.org/documents/dcmi-period/
http://dublincore.org/documents/dcmi-point/
http://dublincore.org/documents/dcmi-terms/
http://dublincore.org/documents/dcmi-type-vocabulary/
http://dublincore.org/documents/dcq-html/
http://dublincore.org/documents/dcq-rdf-xml/
http://dublincore.org/documents/library-application-profile/
http://dublincore.org/documents/usageguide/
http://dublincore.org/documents/usageguide/glossary.shtml -- separate metadata??
http://dublincore.org/documents/usageguide/qualifiers.shtml -- separate metadata??
http://dublincore.org/documents/wgguidelines/
http://dublincore.org/groups/
http://dublincore.org/groups/access/
http://dublincore.org/groups/agents/
http://dublincore.org/groups/architecture/
http://dublincore.org/groups/citation/
http://dublincore.org/groups/collections/
http://dublincore.org/groups/corporate/
http://dublincore.org/groups/corporate/Seattle/
http://dublincore.org/groups/date/
http://dublincore.org/groups/education/
http://dublincore.org/groups/environ/
http://dublincore.org/groups/government/
http://dublincore.org/groups/guide/
http://dublincore.org/groups/kernel/
http://dublincore.org/groups/languages/
http://dublincore.org/groups/libraries/
http://dublincore.org/groups/mailinglists.shtml
http://dublincore.org/groups/pid/
http://dublincore.org/groups/preservation/
http://dublincore.org/groups/registry/
http://dublincore.org/groups/standards/
http://dublincore.org/groups/tools/
http://dublincore.org/groups/type/
http://dublincore.org/links/
http://dublincore.org/news/
http://dublincore.org/news/adoption/
http://dublincore.org/news/communications/
http://dublincore.org/news/communications/deliverables.shtml
http://dublincore.org/news/documents.shtml
http://dublincore.org/projects/
http://dublincore.org/resources/
http://dublincore.org/resources/faq/
http://dublincore.org/resources/translations/
http://dublincore.org/schemas/
http://dublincore.org/sitemap.shtml
http://dublincore.org/sponsors/
http://dublincore.org/tools/
http://dublincore.org/usage/
http://dublincore.org/usage/decisions/
http://dublincore.org/usage/documents/
http://dublincore.org/usage/documents/abstract-model/ - address does not exist yet
http://dublincore.org/usage/documents/approval/
http://dublincore.org/usage/documents/criteria/
http://dublincore.org/usage/documents/mission/
http://dublincore.org/usage/documents/overview/
http://dublincore.org/usage/documents/principles/
http://dublincore.org/usage/documents/process/
http://dublincore.org/usage/documents/profiles/
http://dublincore.org/usage/documents/publications/
http://dublincore.org/usage/documents/vocabulary-guidelines/
http://dublincore.org/usage/meetings/
http://dublincore.org/usage/terms/
http://dublincore.org/usage/terms/history/
http://dublincore.org/workshops/

------------------------------------------------------------------------
APPENDIX B: Support for OAI Static Repositories
------------------------------------------------------------------------

According to http://www.openarchives.org/news/oaistaticrepo0301010.html,
the OAI protocol now provides: 

    a simple approach for exposing relatively static and
    small collections of metadata records through the OAI-PMH.
    The Static Repository approach is targeted at organizations
    that:

    -- Have metadata collections ranging in size between 1
       and 5000 records;
    -- Can make static content available through a
       network-accessible Web server;
    -- Need a technically simpler implementation strategy
       compared to acting as an OAI-PMH Repository, which
       requires processing OAI-PMH requests.

    A Static Repository is an XML file that is made accessible
    at a persistent URL. The XML file contains metadata
    records and repository information.

    A Static Repository becomes accessible via OAI-PMH through
    the intermediation of one Static Repository Gateway.
    A Static Repository Gateway uses the metadata records and
    repository information, provided via XML in the Static
    Repository, to process the six OAI-PMH requests for access
    to that information.