Ingesting into the Repository is the act of taking a digital asset and creating metadata to describe this asset, checking that the asset and metadata is valid, followed by a review process to ensure that everything is compliant with DRI guidelines. Surrogate information may be generated at this point in time. Once the new digital object is prepared and validated, it is then ingested for preservation. A DRI digital object refers to metadata, and the associated digital asset e.g. an image, a document, an audio file etc. A digital object without assets, i.e. metadata only, is also a valid digital object. A depositor should also consider ingesting contextual information about their collections to aid other researchers in reusing their data. Contextual information is also ingested into the Repository as a digital object. Methods of Ingestion into the Repository
A depositor can create collections and ingest digital objects into these in three different ways:
1. User Interface
Content can be ingested into the Repository using the user interface. The user interface allows the user to create a collection by filling in collection-level metadata into a form. The Repository includes a web-based user interface for single object ingest. This user interface provides blank fields to allow cataloguers to create metadata for a single digital object to be ingested into a target collection. The metadata records are stored as XML and can be exported by the cataloguer as an XML file if desired. Metadata in XML format can also be ingested directly into a collection in the Repository.
2. DRI Client Application
Content can be ingested into the Repository using the DRI Client Application. This method is currently command line based. The DRI Client Application can be used to ingest a single digital object into a target collection that is already in the Repository, or can be used to create a collection at the time of ingestion. The DRI Client Application can also be used for bulk ingest, where the depositor can ingest multiple digital objects at once.
3. DRI REST-Based API
Content can be ingested into the Repository through third-party applications using the DRI REST-based API.