Methods

There are two methods you can use to create Opaque Container objects in Batch Builder:

1. Manually create objects from template. This is best when you have less than 5 objects to work with. In this scenario you generate an object structure in BB for each object and then copy files into it (can be done outside BB). See section 8.5 for the procedure.
   
   
2. Automatically build objects from template. This method is best for large batches of objects (5 or more objects per batch). In this scenario BB generates object structure for each of your objects and moves files into object directories. Before this can happen you need to rename your files to add special "object name" file prefixes or provide mapping files that associate files with their objects. See section 8.5 for the procedure.
   
   

Note that an opaque container object can have only one directory named "container" (where all the content files are stored). Inside the container directory there can one zip file containing files in any format..

Opaque container objects and the files they contain cannot be delivered using DRS delivery systems, such as FDS. Opaque container content can only be downloaded through Web Admin.

Accepted Formats

Files of any format can be deposited as part of an opaque container object.

Anchor
content-files-opaque content-files-opaque

Guidelines on Content Files

To the extent possible, care should be taken to only include in a single opaque container object zip file those files that logically make up an object.

Try to include within the same opaque container object's zip file, files that:

• Are related by derivative relationships (e.g. master and use copies)
• Have display or rendering dependencies (e.g. style sheets, scripts and images should be included in the same opaque container as web pages dependent on them)
• Require the same descriptive metadata (are part of the same work with the same bibliographic record)

Deposit in separate opaque container objects:

• Files which are not related or dependent on each other contextually or structurally
• Files that constitute several independent logical objects
• Omit from opaque container objects:
  • Content not intended for long-term preservation

Although it is expected that the content of opaque container objects might not be fully appraised or processed prior to deposit into the DRS, to the extent possible depositors should perform an initial weeding out of unwanted material. This is especially important in the case of donated hard drives which may contain applications, system files, cached data, etc.