Overview

This is a description of the procedure to automatically build a batch of still image objects from template using Batch Builder 2 (BB). Use this method if you have a large number of objects (more than 10) that need to be created and your source files are not broken into directories by object.

Procedure summary:

1. Create a new project.
2. Enter DRS deposit information.
3. Create the object template.
4. Add directories to the object template.
5. Repeat steps in (4) for additional nested directories if needed.
6. Save your work
7. Move/copy images into the object template.
8. Create a new object batch.
9. Process the batch.

What you need before you start:

• Prepare digital images and put them in a directory of your choice somewhere on local hard disk or network drive. If you have more than one file per image (e.g.: an archival master and a deliverable or an archival master, a deliverable and a thumbnail) make sure file names match (e.g.: image-1.tif, image-1.jp2 and image-1.jpg).
• Decide what you will use for owner supplied names for image objects and the digital image files they consist of. For instance, you could use local classification or local accession numbers. Consult Section 3 Naming rules for files, objects and directories of this Guide for more information.
• Make sure you either provide object name prefixes for each file to specify which objects it should be assigned to (The syntax is: [obj-osn]--[file_name].[extension]) or provide object assignment for your file in an external mapping file. For more details about providing object prefixes for your files see the File name pattern options section of Installation and Setup. For more details about external mapping files see Using mapping.txt File.

Procedure:

Start at Step 5 if you are reusing a project to generate a new batch.

1. Create new project in Batch Builder
   
   1. From main menu select Project > New.
   2. Enter project data:
      Project Name: enter a name for your project (used for internal tracking only).
      Project Directory: select the directory where project will be saved (click ellipsis button to browse for or create a directory).
      TIP: use 'project' as part of the directory name to make it easier to identify later. (e.g. museum_slide_project)
      Content Model: select the "still image" value from the dropdown.
      Project Description (optional): Any information relevant to the project – will only remain locally.
   3. Click OK to continue.
      
      
2. Enter DRS deposit settings:
   
   1. Click on "Deposit Settings" in Project Panel tree.
   2. Enter deposit data in the form:
      Batch Name Pattern: default - {owner}{batchDir}{yyyy}{mo}{dd}_{hh24}{mm}{ss}
      (This is the name for a batch that appears on DRS deposit reports. Batch name must be at least 3 characters long.)
      Success Email: type email and press enter.
      Failure Email: type email and press enter.
      Success Method: choose how you will receive load report.
      Deposit Agent: type your HUID.
      Deposit Agent Email: type your official Harvard email address.
      
      
3. Create object template:
   Metadata added at this level will be applied to every object in a batch, unless overridden by specific object metadata that you define in later steps.
   
   1. Click on "Object Template" in Project Panel tree:
   2. Enter required object metadata in the form:
      Owner Code: your owner code (use all caps).
      Billing Code: your billing code (use all caps).
      File Access Flags: the DRS access flag. At this level, select the least restrictive value if the batch will contain a mix of public and restricted files.
      URN Authority Path: your NRS authority path. Use all caps. Look up your Path here if needed: http://nrs.harvard.edu/urn-3:hul.ois:nrsstatusprod.
      File URN Resource Name Pattern: use default value {n} to generate a unique number.
   3. Switch to "optional" tab to enter any optional metadata (for example, descriptive metadata, roles and relationships that will apply to your objects). For more about optional metadata see Sections 9. Adding Relationships, 10. Adding Descriptive Metadata, 11. Adding Supporting Content.
      
      
4. Add directories to template:

   In automatic object workflow, you create role-based directories (archival master, deliverable) and in a later step, Batch Builder will create the objects for you.

For one image file per object:

Add directory:

1. 1. Right click on "OBJECT TEMPLATE" in the Project Panel on the left and select the 'add a directory…" menu option.
   2. Type in a name for your directory in the text box . The directory name will start with "image" but the name you type will be appended to it. Tip: to make it easier to read, start your directory name with an underscore (_) So, typing '_tifs_and_jpegs' will result in a directory called 'image_tifs_and_jpegs'
   3. In the Project Panel on the left select the directory you just created.
   4. In the Content Panel on the right, choose "yes" from the dropdown list for the field "First Generation in DRS".
   5. Choose "HIGHUSE" for Usage Class.

Add additional metadata (optional tab):

1. 1. Select the new directory in the Project Panel on the left
   2. In the Content Panel, select the 'optional' tab.
   3. Scroll down to "Still Image File Metadata "
   4. Enter any file level optional metadata in the form
      Role: use Ctrl Click to select ARCHIVAL_MASTER and DELIVERABLE roles. Note that in order to get a delivery URN on deposit a file needs to have a role DELIVERABLE set in BB.
      
      

For multiple image files per object (e.g., archival master, deliverable), you need to create a directory for the master file and a nested sub-directory for each derivative file.

Add a master directory:

1. 1. Right click on "OBJECT TEMPLATE" in the Project Panel on the left and select the 'add a directory…" menu option.
   2. Type "-archival_master" or a similar suffix that describes the role for your directory in the text box. The directory name will start with "image" but the name you type will be appended to it. So, typing '-archival_master' will result in a directory called 'image-archival_master'
   3. In the Project Panel on the left select the directory you just created.
   4. In the Content Panel on the right, choose "yes" from the dropdown list for the field "First Generation in DRS".
   5. Choose "LOWUSE" for Usage Class.

Add additional metadata (optional):

1. 1. Select the new directory in the Project Panel on the left
   2. In the Content Panel, select the 'optional' tab.
   3. Scroll down to "Still Image File Metadata "
   4. Enter any file level optional metadata in the form
      Role: select ARCHIVAL_MASTER.

Add a nested directory for derivative (e.g. a directory for deliverable images):

1. 1. Right click on the directory you just created in the Project Panel on the left and select the 'add a directory…" menu option.
   2. Type "-deliverable" or a similar suffix that describes the role for your directory in the text box. The directory name will start with "image" but the name you type will be appended to it. So, typing '-deliverable' will result in a directory called 'image-deliverable'
   3. In the Project Panel on the left select the directory you just created.
   4. In the Content Panel on the right, choose "no" from the dropdown list for the field "First Generation in DRS".
   5. Choose "HIGHUSE" for Usage Class.
      
      

Add additional metadata for this derivative subdirectory (optional):

1. 1. Select the new directory in the Project Panel on the left
   2. In the Content Panel, select the 'optional' tab.
   3. Scroll down to "Still Image File Metadata "
   4. Enter any file level optional metadata in the form
      Role: select appropriate value for derivative (e.g., DELIVERABLE). Note that in order to get a delivery URN on deposit a file needs to have a role DELIVERABLE set in BB
   5. Repeat steps 3 and 4 to create additional nested directories if you have more files derived from the current one.

     5.  Save your work (Project > Save on main menu).

     6.  Copy image files into Batch Builder template directory on disk (can be done outside Batch Builder).

The directories you created in BB have been created on disk, in the project's template path: {project_name}\template\

In order to tell BB which object each file should end up with you need to either add object name prefixes to each file name or supply a mapping.txt file that associates each file with its future object. See Section 3: Naming Rules for Objects for how to add an object name prefix. See Using mapping.txt File for how to create a mapping file.

In the automatic workflow, files with the same role (archival master, deliverable) are copied into the corresponding role-based directory. In a later step, Batch Builder will use the object name prefix for each file to create object directories and move files for each object into these directories.

Note: if you need to check where the directories are on disk, click on "Deposit Settings" in the Project Panel tree and look at the Project Path field at bottom.
** Quick way to copy content files: you can drag files from your file system onto the object template directories in the Batch Builder project panel.
** If using mapping.txt, this is when you should copy it to the auxiliary template path in the project.
** If including external MODS descriptive metadata, this is when you should copy it to the auxiliary template path in the project.

     7.  Create a new object batch.

You can create your new object batch in the Graphical User Interface or using the Command Line Interface (CLI).

In the Graphical User Interface

1. 1. From the Object menu in BB select "Create a new batch with objects from template"; enter the name of the batch directory to be created on disk and click OK. A new batch icon will be added to the Project Panel on the right (icon with a red letter B) and new objects will be built that are going to be part of this batch.
   2. In the Project Panel click on the "+" next to the Batch icon of the batch you just created to expand the tree – it will show the icons for the new objects (a blue letter O).
   3. (Optional) Select the object icon of your new object in the Project Panel and switch to "optional" tab in the Content Panel to enter any optional metadata (for example descriptive metadata, roles or/and relationships that will apply to your objects). For more about optional metadata see Sections9. Adding Relationships, 10. Adding Descriptive Metadata, 11. Adding Supporting Content. . Note that any metadata entered at the object level will override metadata entered at the template level.
   4. Save the project to have BB write the new metadata values to the internal configuration files.

     8.  Process the batch.

You can process your batch in the Graphical User Interface (GUI) or using the Command Line Interface (CLI).

In the In the Graphical User Interface

1. 1. In the Project Panel on the left right-click on the batch you want to process (batch icon with a red letter B) and select "Create descriptors and batch.xml."
   2. Builder will start processing the batch.
   3. When the batch is successfully processed you will see the following message:

FINISHED - Creation of batch.xml and descriptors complete for batch ….
If you see any error messages, remedy the errors and re-process the batch.

In the Command Line Interface

1. 1. In the command line window (Terminal on Mac or Linux or CMD on Windows) change to the BB installation directory, e.g.: cd C:\Program Files\BatchBuilder\BatchBuilder-2.0.33
      Type bathcbuildercli –a build –p [project_directory_path] –b [batch_directory_name], e.g.: batchbuildercli -a build -p "E:\My Project" -b batch1
   2. (Optional) add additional parameters to the bathcbuildercli command to substitute batch, object and directory level properties. For more information see Section 14. Processing Batches Using Command Line Interface.
   3. When the batch is successfully processed you will see the following messages:

Building PREMIS file metadata...
Building HulDrsAdmin file metadata...
Success!

If you see any error messages at the end of batch processing, remedy the errors and re-process the batch (you can disregard any errors showing during batch processing on command line as long as you get the final "Success!" message).