Preparing Collections on the S Drive for Online Delivery and Storage

From UA Libraries Digital Services Planning and Documentation
(Difference between revisions)
Jump to: navigation, search
(Admin)
(6 intermediate revisions by 2 users not shown)
Line 50: Line 50:
 
***If multiple Digital Collections spawn from the same Analog Collection, there can be more than one Collection Information XML file as follows: u0003_0000001.1.xml, u0003_0000001.2.xml, etc.
 
***If multiple Digital Collections spawn from the same Analog Collection, there can be more than one Collection Information XML file as follows: u0003_0000001.1.xml, u0003_0000001.2.xml, etc.
 
***Make sure to refer to the [[Collection_Information|Collection_Information]] page regarding acceptable data values.
 
***Make sure to refer to the [[Collection_Information|Collection_Information]] page regarding acceptable data values.
** '''[[TrackingFiles#Scope|u0003_0000001.log.txt]]'''
+
** '''[[Tracking Data|u0003_0000001.log.txt]]'''
 
***Include a text version of the log file with every batch; previous versions of the log will be overwritten by the newest version.
 
***Include a text version of the log file with every batch; previous versions of the log will be overwritten by the newest version.
  
Line 56: Line 56:
 
** [[Thumbs_icons|Thumbs Icon]] - .png extension.
 
** [[Thumbs_icons|Thumbs Icon]] - .png extension.
 
** [[OCR List|OCR list]] - .ocrList.txt extension.
 
** [[OCR List|OCR list]] - .ocrList.txt extension.
 +
*** '''u0001_0000002.ocrList.txt'''
 
<!--** Finding Aid - .xml extension-->
 
<!--** Finding Aid - .xml extension-->
**Other relevant documents saved as plain .txt (ANSI or UTF-8 without BOM preferred). If possible please incorporate any additional data into the log.txt file. For example, audio collections often have significant item-level notes that we want to retain. These plain text files can be saved with a ".notes.txt" extension - i.e. "u0008_0000001_0000001.notes.txt".
+
** [[Skipped Items | Skipped items list]] - .skipped.txt extension. For batched collections: this should be present ONLY during the last upload, as it will contain information about skipped items across the entire collection.
 +
*** '''u0003_0000193.skipped.txt'''
 +
**Other relevant documents saved as plain .txt (ANSI or UTF-8 without BOM preferred). If possible please incorporate any additional data into the log.txt file. For example, audio collections often have significant item-level notes that we want to retain. These plain text files can be saved with a ".notes.txt" extension
 +
*** '''u0008_0000001_0000001.notes.txt'''
  
 
===Metadata===
 
===Metadata===
Line 63: Line 67:
 
* Must contain:
 
* Must contain:
 
**'''u0003_0000001.m01.txt'''  or '''u0002_0000001.m03.txt'''  or '''u0008_0000001.m02.txt'''  
 
**'''u0003_0000001.m01.txt'''  or '''u0002_0000001.m03.txt'''  or '''u0008_0000001.m02.txt'''  
***Note the type of spreadsheet is echoed in the segment before the ".txt" --  if this is a batch file, the batch number follows the m0x value:  u0002_0000001.m01.1.txt.
+
***Note the type of spreadsheet is echoed in the segment before the ".txt" --  if this is a batch file, the batch number precedes the m0x value:   
 +
**** example: '''u0002_0000001.1.m01.txt'''.
 +
**** check this file for: Diacritics, Quotes, UTF-8 encoding
 
***see [https://intranet.lib.ua.edu/cataloging/metadata/SpreadsheetRegistry] for more information.
 
***see [https://intranet.lib.ua.edu/cataloging/metadata/SpreadsheetRegistry] for more information.
 
**'''A MODS folder'''
 
**'''A MODS folder'''
Line 80: Line 86:
 
** u0003_0000001_0000001.txt, u0003_0000002_0001.txt, etc. - plain .txt files corresponding to non-compound and compound objects (inside respective subfolders).
 
** u0003_0000001_0000001.txt, u0003_0000002_0001.txt, etc. - plain .txt files corresponding to non-compound and compound objects (inside respective subfolders).
 
** u0003_0000001_0000001.ocr.txt, u0003_0000002_0001.ocr.txt, etc. - plain .txt files of OCRed tiffs corresponding to non-compound and compound objects (inside respective subfolders). If cleaned up .txt files exist, remove the corresponding .ocr.txt file.
 
** u0003_0000001_0000001.ocr.txt, u0003_0000002_0001.ocr.txt, etc. - plain .txt files of OCRed tiffs corresponding to non-compound and compound objects (inside respective subfolders). If cleaned up .txt files exist, remove the corresponding .ocr.txt file.
 +
 +
===needsRemediation===
 +
*This folder always exists at the following location.
 +
** S:\Digital Projects\Administrative\Pipeline\collectionInfo\forMDlib\needsRemediation
 +
*Must contain:
 +
**Excel formatted version of the batch metadata. 
 +
***example: '''u0002_0000001.1.m01.xlsx'''.

Revision as of 17:38, 23 April 2013

The following page assumes the content for upload has already been through the Quality Control process

Contents

Preparation Procedure

Choose one of the following checklists:

One-Shot Collections are small enough to be completed in one batch, so they require no batch numbering or batching process.

Ongoing Collections are those which will have multiple batches for upload, so they require "batching."

One-Shot Collections

  1. Move collection folder from Digital_Coll_in_progress to Digital_Coll_Complete
  2. Remove extra text in folder name so that it is labeled with just the collection number
    1. Example: u0003_0000633_HarperTimetables --> u0003_0000633
  3. Finalize collection documentation
    1. Tracking Data
      1. OLD/SEPARATE FILE: save TrackingFiles spreadsheet (see S:\Digital Projects\Organization\TrackingFiles) as tab delimited .txt file in Admin folder (see TrackingFiles for more)
      2. NEW/INTEGRATED: COPY Filename column from the metadata spreadsheet to a new sheet, MOVE Tracking Data columns to new sheet, SAVE as tab delimited .txt file in Admin folder (see Tracking Data for more)
    2. OCR List: see these instructions
    3. Metadata: save spreadsheet (minus the tracking data you should’ve already removed) as tab delimited .txt file in Metadata folder
  4. Create MODS
  5. Carefully check contents of the folders (see list below)
    1. Make sure to remove any unnecessary files created during the capture process (for example, test scans or supplementary metadata or text file notes about progress)
  6. Once everything is okay, you’re ready to Upload Content!

Ongoing Collections

  1. Set up collection folder in Digital_Coll_Complete, and create inside it
    1. Admin
    2. Metadata
    3. Transcripts (if necessary)
  2. Move Scans folder from ongoing collection folder in Digital_Coll_in_progress to this new collection folder in Digital_Coll_Complete
  3. Follow the procedures for Creating Batch Documentation
  4. Create MODS
  5. Double-check contents of the folders (see list below)
  6. Once everything is okay, you’re ready to Upload Content!


Checking Folders

The Collection Level folder contains subfolders and their content must adhere to certain specifications prior to the collection being considered ready to "ship" for online access and long term storage.

The collection number u0003_0000001 will be used as an example.

Admin

  • This folder must exist.
  • Must contain:
    • u0003_0000001.xml
      • If multiple Digital Collections spawn from the same Analog Collection, there can be more than one Collection Information XML file as follows: u0003_0000001.1.xml, u0003_0000001.2.xml, etc.
      • Make sure to refer to the Collection_Information page regarding acceptable data values.
    • u0003_0000001.log.txt
      • Include a text version of the log file with every batch; previous versions of the log will be overwritten by the newest version.
  • May also contain:
    • Thumbs Icon - .png extension.
    • OCR list - .ocrList.txt extension.
      • u0001_0000002.ocrList.txt
    • Skipped items list - .skipped.txt extension. For batched collections: this should be present ONLY during the last upload, as it will contain information about skipped items across the entire collection.
      • u0003_0000193.skipped.txt
    • Other relevant documents saved as plain .txt (ANSI or UTF-8 without BOM preferred). If possible please incorporate any additional data into the log.txt file. For example, audio collections often have significant item-level notes that we want to retain. These plain text files can be saved with a ".notes.txt" extension
      • u0008_0000001_0000001.notes.txt

Metadata

  • This folder must exist.
  • Must contain:
    • u0003_0000001.m01.txt or u0002_0000001.m03.txt or u0008_0000001.m02.txt
      • Note the type of spreadsheet is echoed in the segment before the ".txt" -- if this is a batch file, the batch number precedes the m0x value:
        • example: u0002_0000001.1.m01.txt.
        • check this file for: Diacritics, Quotes, UTF-8 encoding
      • see [1] for more information.
    • A MODS folder
      • This folder will contain all the MODS files created via Archivist Utility (see: Making MODS).

Scans

  • This folder must exist.
  • Must only contain:
    • Scans (tiffs/wavs) of non-compound objects and compound objects (inside respective subfolders). All other files types will not be retained. Temporary files and thumbs.db files do not have to be deleted since they will be removed upon transfer to Storage.

Transcripts

  • This folder can exist only if transcripts exist.
  • Must only contain one or more of the following types of files:
    • u0003_0000001_0000001.tif, u0003_0000002_0001.tif, etc. - corresponding to non-compound and compound objects (inside respective subfolders).
    • u0003_0000001_0000001.txt, u0003_0000002_0001.txt, etc. - plain .txt files corresponding to non-compound and compound objects (inside respective subfolders).
    • u0003_0000001_0000001.ocr.txt, u0003_0000002_0001.ocr.txt, etc. - plain .txt files of OCRed tiffs corresponding to non-compound and compound objects (inside respective subfolders). If cleaned up .txt files exist, remove the corresponding .ocr.txt file.

needsRemediation

  • This folder always exists at the following location.
    • S:\Digital Projects\Administrative\Pipeline\collectionInfo\forMDlib\needsRemediation
  • Must contain:
    • Excel formatted version of the batch metadata.
      • example: u0002_0000001.1.m01.xlsx.
Personal tools
http://www.lib.ua.edu/wiki/digcoll/index.php?title=Preparing_Collections_on_the_S_Drive_for_Online_Delivery_and_Storage&diff=4623&oldid=4511
www.lib.ua.edu
crawl=CC-MAIN-2014-23
35575
application/http; msgtype=response
sha1:VSC2CM52ELLYQGCYOUTM6NIJ53LKQGYM
<urn:uuid:90baea47-1153-4cbd-a766-20fae0ae5977>
2014-07-31T00:19:12Z
130.160.4.174
sha1:B45JR4FM7UC6B7L3DABDWKPRPPUA6D6Z
<urn:uuid:d7c5b010-2063-4c75-861e-7aeb2cf9e6ce>
http://www.lib.ua.edu/wiki/digcoll/index.php?title=Preparing_Collections_on_the_S_Drive_for_Online_Delivery_and_Storage&diff=4623&oldid=4511
length
response
<urn:uuid:406650cd-53f9-41b0-aee0-c6094918ce6b>
robots: classic
hostname: ip-10-146-231-18.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2014-23
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for July 2014
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf