Storing Content in the DRC

The process of adding content to the server is a workflow set up by each Community, and can include many steps to the ultimate goal of making the ContentObject available. At the very beginning of the workflow is the registration of the item into the DRC through one of these methods:

Each of these loading methods has an associated configuration element to specify what fields the ObjectSubmitter will be asked to fill in.

Note -- it may be more useful to think of this stage of ingestion from the point of view of how the object gets into the repository ingestion workflow, and also to separate the creation of metadata from the loading of the digital object. For example:

  • Web Form-based Upload ("Dropbox"?)
  • WebDAV Load
  • Command line tools

Ingestion Workflow Framework

At the point the submitter uploads the object(s) and keys the metadata, the IngestionWorkflowFramework routes the object through a series of processing queues for both automated and manual activities related to the submission and publication process. The processing queues are set by the Community's EditorModerator depending on the needs and desires of the Community, and these queues can be put together in any number of ways. (The complete list of queues can be found in the description of the IngestionWorkflowFramework.)

For example, a Community's workflow may be set such that a submitted item is first reviewed by an EditorModerator and when approved it made available to the CommunityAudience?. Or the workflow could be set the opposite way: the item is immediately published and is routed to the EditorModerators? for review and possible withdrawal. The workflow could also be more complex: an object is submitted, reviewed by an editor, published, and then has its metadata enhanced. Peer reviewed journals and approval of electronic theses and dissertations can use a chain of submission -> review -> peer review -> resubmission -> review -> publish -> metadata enhancement.

Open Archives Initiative

Another way in which content can be added to the DRC is via the OpenArchivesInitiative? OaiServiceProvider. With OAI harvesting, only the metadata about objects in another repository is added to the DRC. The metadata includes pointers back to the originating repository; these pointers can be followed when searching and browsing on the DRC. Metadata added through the OAI harvester does not go through any of the workflows described above.

What if a community would like to add additional metadata to an OAI object in order to make it relevant for inclusion in the DRC? Is there a mechanism to add "local" level metadata for enhancement?

Also, OAI is encouraging repositories to expose both simple Dublin Core and other richer metadata formats. Will the DRC harvest all formats of metadata about objects from other repositories?

Meta Buddy

MetaBuddy is a web-based system to assist communities in developing properly formatted (e.g. standards-based) ApplicationProfile documents for projects hosted on the DRC.

License Buddy

LicenseBuddy? is a web-based system to assist AuthorCreators? and EditorModerators? in selecting the appropriate license for their content.