Scans folder

From UA Libraries Digital Services Planning and Documentation
Revision as of 10:29, 20 November 2009 by Scpstu32 (Talk | contribs)

Jump to: navigation, search

Contents

Scans folders

Content

Scans folders should contain ONLY tiff or wav files, compound-object folders that contain tiff or wav files, or subpage-level folders containing subpage-level scans.

  • Optimize scans/audio before uploading to the server, so that we don't have to ask ourselves whether the digitized materials online are optimized; we'll just know.

Workflows

This section shows the folder naming sequence from beginning to end, i.e. from the scans being made to content being made ready for placement into archival storage. Note that, as of this writing on 2009 November 20, content typically goes directly into Storage/Acumen. This is the "standard working procedure". There will be, however, exceptions to this rule when content will first go into ContentDM. This will require

Standard Working Procedure: Content goes into Storage/Acumen

This applies if the collection is handed directly to Jody for placement in Storage/Acumen.

  • Scans_#
  • Scans_Check_#
  • Scans_QCed_#
  • Scans_Store_#

Non-Standard: content goes into ContentDM first and then into Storage/Acumen

This applies if the collection, or parts thereof, are first handed to the Metadata Unit for the purposes of remediating the metadata (i.e. adding Subject Headings) after which the content is placed into ContentDM by the Metadata Unit. Digital Services then verifies that everything is in working order before handing the collection off to Jody for placement in Storage/Acumen.

  • Scans_#
  • Scans_Check_#
  • Scans_QCed_#
  • Scans_Ready_#
  • Scans_Online_#
  • Scans_Online_Store_#

Naming Convention Glossary

There is a life-cycle to the workflow that dictates a rigid naming convention for Scans folder. The glossary below denotes the implications of various naming suffixes in regard to "Scans" folders.

Please observe the naming conventions for Scans folders as defined below (observe capitalization and use of underscores, too):

  • Scans
    • This is the working Scans directory. Scans made/optimized get uploaded here.
  • Scans_Check_#
    • After roughly 300 objects are scanned, the Scans folder gets renamed as "Scans_Check_#", where # exists to differentiate one Scans_Check folder from the next - i.e. "Scans_Check_1", "Scans_Check_15".
    • No new scans must go in this newly named folder. After the Scans folder is renamed to "Scans_Check_#", a new, plain "Scans" folder must be made to house active scans.
  • Scans_QCed_#
    • After performing Quality_Control, and rectifying all issues with the scans, rename a "Scans_Check_#" to "Scans_QCed_#". For example, ""Scans_Check_15" to "Scans_QCed_15".
  • Scans_Ready_#
    • The "Ready" tag indicates that the corresponding Metadata, and Collection_Information are in working order for a folder formerly named "Scans_QCed_#". This is done only when content will go into ContentDM first.
      • The use of "Ready" at the Collection Level folder implies inheritance for all lower level folders.
  • Scans_Online_#
    • This change is made by the Metadata Unit after they have remediated the metadata for a "Scans_Ready_#" folder and placed the contents into ContentDM. This is done only when content will go into ContentDM first.
      • The use of "Online" at the Collection Level folder implies inheritance for all lower level folders.
  • Scans_Online_Store_#
    • This change from "Online" to "Online_Store" is made by Digital Services after verifying the contents and all corresponding Metadata, and Collection_Information are still in working order and that no extraneous files exist due to the process of placing things into ContentDM. This is done only when content will go into ContentDM first.
      • The use of "Online_Store" at the Collection Level folder implies inheritance for all lower level folders.
  • Scans_Store_#
    • This change indicates that the folder is prepared for placement into archival storage - corresponding Metadata, and Collection_Information are in working order.
      • The use of "Store" at the Collection Level folder implies inheritance for all lower level folders.
  The value of "#" will remain constant throughout the life cycle of the folder prior to going to storage.
  For example, "Scans_Check_3" will, after quality control, be renamed to "Scans_QCed_3".
Personal tools