Digitization Workflow : SIP prep and steps up until bagging. https://cloud.wikis.utexas.edu/wiki/x/zQ6RAg
Materials exchange happens and arrives to Digital Stewardship with bag group, filename formatting and general metadata provided by collection owner. Collection owner also details how they want the material digitized and delivered.
Digital Stewardship manager provides next available SIP number per batch to be digitized. This will be one SIP per book/volume, or batch/set (of maps, blueprints, cassettes, videos). The next available SIP is determined by using our internal SIPS and DS_Tracking spreadsheets.
DS tracking and SIPS spreadsheets are filled out with assigned SIP and information provided in part by collection owner: Title, identifier, delivery method for digital assets, bag group, digitization instructions, format, UUID, and other relevant information.
A folder is created in 0_processing using the bag group identifier for the material being scanned.
Material is digitized according to instructions and placed in its bag group folder in 0_processing. Archival files (raw, uncompressed scans) are kept in a folder called SIP_files. Derivatives are created from these archival files and kept in a folder called SIP_derivatives. SIP folders containing material that also goes through DocWizz will have a folder called SIP_docworks (folder titled for consistency, as DocWizz used to be called DocWorks.) Any metadata such as submissions spreadsheets, readme notes, media photographs, TARO and UTL catalog xml records, condition spreadsheets, loan documentation is kept in a folder called SIP_metadata. Another possible folder is SIP_diskimage which is created when the material is an optical disc (DVD) and imaged using FTK Imager. (Forensic Tool Kit)
Scanned material is QC’d by original digitization technician, and maybe a supervisor, and moved to 1_delivery folder in dps
Delivery person gives last QC, and delivers the material as specified by collection owner. Derivatives are delivered via Box, disk2 Server, access disc, and/or DAMS.
Digital material is moved to 2_bag-info to be described for bagging. There are bag-info templates for each bag group. Standardized language is used for technical metadata and processing. Each SIP has its own unique bag-info text file. If submission documentation applies to more than one SIP, a copy of the submission documentation will be bagged with each SIP. https://cloud.wikis.utexas.edu/wiki/x/hAGRAg
Delete system files like thumbs.db, ds_store, xlsx, Bridge labels and ratings, etc. Convert xlsx into csv and bag with the csv. Don’t bag jpg files or docWizz backup (dwb) files.
10. Bag these SIPs using a script. AIP is data folder plus 4 bagit generated txt files. A copy of these 4 txt files and submission documentation is saved locally to dps/sips. Mark bag size in SIPs spreadsheet.