Simple Ingest Format

Prerequisite(s)

• The Simple Ingest Format directory (bag) must be accessible on a drive mounted on the repository server. On the production repository server, a conventional location would be a subdirectory within /srv/hydra/repo-work/ or on Fedora 4 servers, /srv/perkins/repo-work.
• Since Collection objects currently require a title, be sure that the row for the collection (the row with the empty path column) in metadata.txt contains a value in the title column.
• Be sure that the data subdirectory and its subdirectories contain only the files that you want to ingest (plus metadata.txt). Be particularly alert for the undesired presence of "dot" files or other "hidden" files.

Analyzing the Simple Ingest Format Directory and Preparing the Ingest Batch

• The following command scans the Simple Ingest Format directory (bag), reports on the results of the scan, and prompts you to either create a pending batch or cancel the operation.
  • In place of <full path to bag directory>, put the full path to the Simple Ingest Format directory.
  • In place of <user key>, put the user key ([email protected]) of the staff member who will process the batch.

From /srv/perkins/hydra/dul-hydra, rake dul_hydra:batch:simple_ingest FOLDER=<full path to bag directory> BATCH_USER=<user key>

• When you run the command given above, you should see output like that shown below that specifies the path to the data directory, the number of files found to be ingested, any files in the data directory (such as metadata.txt) that will not be ingested, and a count of the various types of objects (Collection, Item, and Component) that will be created during the ingest. Review this information carefully to insure that it is what you expect.

Inspected /srv/hydra/repo-work/foo/foo-ingest/data
Found 49 files
Excluding /srv/hydra/repo-work/foo/foo-ingest/data/metadata.txt
Content models {:collections=>1, :items=>49, :components=>49}

• The output noted above should be followed by the prompt:

p - Create pending batch
x - Cancel operation
Enter p, x : 

Enter p followed by RETURN to create a pending ingest batch. Enter x followed by RETURN to cancel the Simple Ingest operation.

Processing the Ingest Batch

• If you responded with p to the prompt noted above, a pending ingest batch should have been created. The ingest batch will be associated with the user whose user key you supplied as BATCH_USER when you ran the simple_ingest task. Only that user (or a superuser) can process the batch.
• To process the batch, follow the instructions on ... need to add page for this. This is https://ddr.lib.duke.edu/batches in Fedora 3.

Setting Roles on Ingested Object(s)

• When the ingest batch has successfully completed, the resulting objects will have no roles set on them. A superuser will need to access the appropriate object(s) and set the appropriate role(s). For example, the superuser may want to give someone the Curator role on collection object in the policy scope.
• Hint: To find the ingested collection object in the repository, the superuser may want to access the batch from the Batches display and scan its list of batch objects to determine the collection's PID. Or he or she may be able to find the collection via a title or other metadata search.