Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »


The RipStation BR6-7604 may be used for shipments that include 15 or more pieces of optical media all of which belong to one of the following categories (follow links for more information on media identification):

If you are working with fewer than 10 discs of one of the above categories, it will be more time-efficient to simply use the BDPL Ingest Tool, following instructions in the Ingest User Manual and Workflow Guidelines.

The RipStation workflow requires that the barcodes for each optical disc are entered in a plain text file, which is then stored alongside the appropriate application (RipStation or RipStation DataGrabber).  The discs themselves must be placed on the RipStation input spindles in the same order as on the plain text file.

After the RipStation completes the transfer of content off the discs, files must be copied to the Scandium file server and then moved to the appropriate shipment folder.  The will then be run to complete any file replication and content analysis so that RipStation content is identical to the Information Packages produced by the standard BDPL Ingest tool.

Once the ingest of RipStation content has completed, BDPL staff will then use the script to check in each disc to see if it all processes successfully completed or if there were any failures in the transfer and/or analysis of content.  Failed items will be reviewed by the digital preservation librarian and will be run through the standard BDPL Ingest Tool workflow (or, if incorrectly categorized, the other RipStation workflow).  During postprocessing, staff will also follow the BDPL guidelines to Scan the Physical Media (the disc, case with barcode, and any additional descriptive materials) using the desktop scanner. 

Set Up for RipStation and RipStation DataGrabber Workflows

 To help determine the type of disc, use information on the disc (labels and manufacturers' information) as well as details in the shipment manifest.  For assistance, see the guidelines for Identifying Different Types of Optical MediaNote that CDDA content cannot be burned to a DVD!

  • On the RipStation, create a "userdata.txt" file for the current group of discs.  Enter each item barcode in the file, one per line, making sure not to include extra spaces (see example below). Save periodically to prevent losing your information!

NOTE: the 'userdata.txt' filename is very important; do not use additional characters or capital letters or it won't be recognized by the software!

  • Remove each disc from its case or enclosure and write the last four digits of the barcode on the inside of the disc (around the center hole).  Depending on the barcode scheme, it may be necessary to use more than four digits to avoid confusion.


  • Then place the discs in a stack on the work surface.  Place them upside down so that the first disc (directly on the table) corresponds to the first barcode in userdata.txt file (and the final disc in the stack will be the final barcode in the file).

  • Place the empty cases or enclosures in a place where they will not be in the way.  Don't stack too high, or they may topple over and it will be more challenging to match the discs back up with the cases. (If there are multiple stacks of cases, it may help to include a post-it note on each to indicate the order.)

  • When all barcodes are entered in userdata.txt, save the file alongside the appropriate application:
    • RipStation (for CDDAs): 
    • RipStation DataGrabber (for data discs and DVD-Video content): 

  • Finally, load discs onto the RipStation input spindle(s), ensuring they are in the same order as they were entered on the userdata.txt file (i.e., first disc on the first spindle is the first barcode in the file).

NOTE: if loading discs into both input spindles, put the first stack in the spindle closest to the RipStation drives, as it will be checked first by the robotic arm.

CDDA Workflow: RipStation Application


Data Disc and DVD-Video Workflow: RipStation DataGrabber Application


The RipStation DataGrabber software should not require any adjustments, as the settings will be saved from one operation to the next.  If these are changed or reset, the software configuration for data discs and DVD-Videos should reflect:

  • Loader type: MFD
  • Ouput format: ISO/MDF Image
  • Disc count: 0
  • FIle type filter: leave blank
  • Root path: D:\Local Data\
  • Name format: [shipmentID]\%0\disk-image\%0  


  • Double-click the DataGrabber icon on the RipStation desktop to launch the application.

  • Once the program starts, make sure that:
    • The settings match the configuration outlined above.
    • A current copy of userdata.txt is stored in the DataGrabber program folder: C:\Program Files\MF Digital\RipStation DataGrabber

  • Load the disks onto the input spindle in the same order that they are listed in userdata.txt. NOTE: the software first checks the input spindle closest to the drives.

  • Press the 'Start' button and start grabbing some data!  It's recommended that you keep an eye on the RIpStation while the DataGrabber is in operation in case any errors or issues occur that require assistance.

Copying Files to Scandium


Note .bat scripts on RipStation

Completing Ingest for RipStation Content


Post-Processing RipStation Content

Run and create images


Robotic Arm Is Unable to Pick Up Disc

The robotic arm may have trouble grasping individual discs for no apparent reason.  After several unsuccessful attempts, the software will display a dialogue box asking if you want to cancel the operation (no more discs), try again (discs remain), or keep going (additional discs have been added).  Click the 'Try again' button to continue; it may be necessary to gently lift the disc up to meet the robotic arm or nudge it closer to the spindle frame so that it can be picked up.

Unexpected Crash

The RipStation DataGrabber software may stop unexpectedly in the middle of a batch.  If this happens, check the RipStation output window to see the last barcode that was successfully completed:

Remove any uncompleted discs that may have been left in the drives and return to the input spindle, making sure they are in the same order as in the 'userdata.txt' file. Be sure to delete any barcodes from userdata.txt that have been completed so that the next disc in the spindle is the first barcode in the file.

"Unable to close the drive tray"

While using the DataGrabber software to transfer content off of data discs and DVD-Video discs, BDPL staff on several occasions have encountered a situation where a disc is loaded into a drive and the software produces an error message indicating it is 'Unable to close the drive tray' and that the batch has completed, even though other discs are remaining.  An example of the DataGrabber output window is below:

15:19:56 The batch has started.
15:19:58 The loader has been initialized.
15:20:21 NewBatch.cpp(675) : The loader has failed to load the next disc into drive E:.
LoaderMFD.cpp(109) : Unable to close the drive tray.
Drive.cpp(314) : Unable to close the drive tray.
Drive.cpp(313) : Error 8 'CStarBurn_ScsiTransportASPI::ExecuteCDB(): Command failed'
SCSI driver returned 0x1B10030
15:20:21 NewBatch.cpp(675) : The loader has failed to load the next disc into drive F:.
No more discs loaded due to previous failure.
15:20:21 NewBatch.cpp(675) : The loader has failed to load the next disc into drive G:.
No more discs loaded due to previous failure.
15:20:21 NewBatch.cpp(675) : The loader has failed to load the next disc into drive H:.
No more discs loaded due to previous failure.
15:20:21 The batch has completed.

This problem appears to be caused by optical media that are not correctly formatted or finalized.  To confirm, remove the problematic disc from the RipStation and attempt to open on one of the BDPL workstations.  If the disc cannot be read, skip it and restart the batch process.

*****NOTE: when recovering from this error, be sure to edit the list of barcodes in userdata.txt so that the barcode in the first line of the file represents the disc at the top of the input stack.*****

  • No labels