Anchor
_de0daxo33k1c _de0daxo33k1c

Instructions for QA Testing of Storage Class-Enabled BatchBuilder
8/5/2022 JW DRAFT
On Tuesday Aug 25, 2022 LTS plans to release storage class enhancements to production DRS along with a new version of Batch Builder (BB v2.3.0) that is storage class-enabled. With this release, use of older versions of Batch Builder will not be possible – batches generated in an older version will fail to load because they lack storage class assignments.

...

To request help or report a problem, contact LTS Support.
1. Install Batch Builder 2.3.0
2. Create and Generate Your Test Batches
3. Verify Storage Class Assignment Before Deposit
4. Verify Storage Class Assignment After Deposit
5. Storage Class Assignment Criteria

...

Anchor
_ucmkoe7y8wwx _ucmkoe7y8wwx

1. Install Batch Builder 2.3.0

• Download Batch Builder 2.3.0 and follow the installation instructions.
• Point Batch Builder at the QA instance of DRS:
  1. On your file system, open the BatchBuilder-2.3.0 folder and change to the \conf subfolder. Locate the bb.properties files:
  2. Rename the bb.properties file to bb.properties.orig. Click Yes if your system asks you to confirm.
  3. Rename the bb.properties.qa file to bb.properties. Click Yes if your system asks you to confirm. Your active bb.properties file is now configured for QA DRS. If Batch Builder is open when you do this, you'll need to close and restart it.
  4. To reverse this action and return to the original bb.properties file (which points to production DRS), just reverse these steps. Rename bb.properties to bb.properties.qa and remove the .orig extension to reactivate the original bb.properties file. Then restart Batch Builder.

...

• After batch generation but before deposit, open an object descriptor.xml file in a text or xml editor and search for examples of a hulDRSAdmin:storageClass element. There should be one of these for every file in the object. Is the assigned storageClass value appropriate for the file? See the Storage Class Assignment Criteria section for auto-assign criteria. E.g., this
• Examples:
  • This storageClass element was assigned to an archival master file that is not deliverable: <hulDrsAdmin:storageClass status="current" creatingAgent="http://idtest.lib.harvard.edu:9020/wordshack/person/43824" createDate="2022-07-28T14:29:39.913Z">AR</hulDrsAdmin:
  storageClass>E.g., this
  • storageClass>
  • This storageClass element was assigned to a deliverable file:<hulDrsAdmin:storageClass status="current" creatingAgent="http://idtest.lib.harvard.edu:9020/wordshack/person/102" createDate="2022-07-26T19:14:17.773Z">DE</hulDrsAdmin:
  storageClass>E.g., this
  • storageClass>
  • This storageClass element was assigned to a file that is both archival master and deliverable:<hulDrsAdmin:storageClass status="current" creatingAgent="http://idtest.lib.harvard.edu:9020/wordshack/person/102" createDate="2022-08-05T19:17:39.516Z">RE</hulDrsAdmin:storageClass>

Anchor
_1ilxblilagch _1ilxblilagch

4. Verify Storage Class Assignment After Deposit

• Log into QA Web Admin: {+}https://drs2-qa.hul.harvard.edu/drs2_webadmin/search+ .
• Verify the storage class after deposit.
  1. Find the file metadata page for the same files you sampled in Step 3.
  2. Go to the Admin metadata section and look for the Storage class field.
  3. The value displayed in Web Admin should match the auto-assigned value in the descriptor you checked in Step 3. If values don't match, please report this to LTS.
• Check deposited content that should be deliverable. Try the delivery URN. If delivery links don't work, please report this to LTS Support. Note: It can take up to 15 minutes for content to become deliverable. All newly-deposited files are immediately moved to their preservation storage locations but the deliverable copies are moved into delivery storage by an automated process that runs at every quarter hour.

...