Exporting Metadata

You can export metadata from CONTENTdm if you have rights to run reports and export metadata. Export metadata from your CONTENTdm collections to use for other purposes. You can also use this option to register your collection in WorldCat.

CONTENTdm offers the following export choices:

  • Tab-delimited format. Export collection metadata to a tab-delimited file.

  • XML format. Export collection metadata to one of three XML export options.

  • OCLC SiteSearch. Export collection metadata to an appropriate format for use in an OCLC SiteSearch database (discontinued).

  • WorldCat Sync. Register with the Digital Collection Gateway to make your collections available for WorldCat harvesting.

  • OAI. Enable CONTENTdm as an OAI repository to allow OAI harvesters to harvest your collection metadata.

Learn about:

  1. Exporting to Tab-delimited Text Files
  2. Exporting to XML
  3. Exporting to OCLC SiteSearch

For more information about enabling OAI for metadata harvesting, see OAI Support.

Choosing a Metadata Export Mode

The following table provides a quick reference to help you compare what is exported for each mode. For more information, see the Help topic for each mode.

Mode Description Exported Metadata Fields

Exported Administrative/

Other Metadata Fields

Is Page-Level Metadata in Compound Objects Exported?
Tab-Delimited Text file containing metadata fields delimited by tab characters

This standard file format is used with spreadsheets and databases

Option:
Field names in first record
All fields Archival file

CONTENTdm file name

CONTENTdm file path*

Date created

Date modified

Reference URL

CONTENTdm number

OCLC number
Yes
Standard Dublin Core XML
An XML schema that exports according to the Dublin Core standard Only fields mapped to Simple Dublin Core Reference URL Yes
CONTENTdm Standard XML An XML schema developed for CONTENTdm

Options:
Custom XML header

Fields mapped to Qualified Dublin Core have XML tag names based on Dublin Core

If fields are unmapped, they are tagged as unmapped

All fields
Reference URL

Archival file

CONTENTdm file name

CONTENTdm file path

Date created

Date modified

Reference URL

CONTENTdm number

OCLC number
Yes (full text field only or all page-level metadata)
Custom XML A simple XML schema that allows for user-specified XML names

Option:
Repeated field options for fields that contain multiple controlled vocabulary terms and fields that use identical XML tags

Selected fields; you specify XML tag names

Archival file

CONTENTdm file name

CONTENTdm file path

Date created

Date modified

Reference URL

CONTENTdm number

OCLC number
Optionally can include page-level metadata for pages of compound objects (no structural information is included in this export so compound object pages are exported as individual items)
OCLC SiteSearch Dublin Core
Produces the SGML and DTD files that can be used to load a defined Dublin Core database

(Discontinued)
Only fields mapped to Simple Dublin Core None Yes
OCLC SiteSearch Custom
Produces the SGML file that can be used with the DTD file to load a custom OCLC SiteSearch database

(Discontinued)
Selected fields; you specify custom tag names None Yes
WorldCat Sync
After registration, map your fields to MARC and define a schedule for harvesting data into WorldCat Only fields mapped to Simple or Qualified Dublin Core Only fields mapped to Simple or Qualified Dublin Core No
OAI Used for harvesting CONTENTdm sites and can be used in OAI harvesting export applications

Options:
Simple or Qualified Dublin Core
Only fields mapped to Simple or Qualified Dublin Core Reference URL Optional (default = no)

* Note: CONTENTdm file path provides the full locations (URLs) for items. For PDF compound objects and EAD files, the path to the complete print version of the file is provided instead of the path to the compound object.