Skip to content
This repository has been archived by the owner on Jun 27, 2020. It is now read-only.

NESCent Ingest

Jim Coble edited this page Apr 21, 2015 · 2 revisions

#Content Modeling#

  • Collection: A collection object will be created for each NESCent project. One (or more?) collection objects will be created for NESCent administrative materials not associated with a project.
  • Item: An item object will be created for each file ingested.
  • Component: A component object will be created for each file ingested.

#File System Layout#

A directory is created to contain the NESCent materials and metadata. Within that directory, a sub-directory is created for each project and one (or more?) for administrative materials not associated with a project. The files associated with each project or administrative grouping are placed within the appropriate project or administrative sub-directory.

The top directory also contains a delimited text file named `ddr-ingest-metadata.txt' containing descriptive metadata. More information on the metadata file is found below.

Example File System Layout:

NESCent
|----ddr-ingest-metadata.txt
|----Administrative
|    |----FileA.doc
|    |----FileB.xls
|----Project1
|    |----FileC.doc
|    |----FileD.zip
|    |----FileE.pdf
|----Project2
|    |----FileF.txt
|    |----FileG.xls
...
Clone this wiki locally