Navigation
Basic Operations
Home
Issues & Requests
Member API
Partner Tools
Recent Changes
test page
 

Updating

APTrust does not version bags. If you want to keep multiple versions of a bag, use a naming convention. For example:
  • virginia.edu.bag_of_photos
  • virginia.edu.bag_of_photos_V2
  • virginia.edu.bag_of_photos_V3
When you upload a bag that has the same name as an existing bag, this is what happens:
  • If a file in the new bag has the same name as a file in the old bag and the size or the md5 checksum or the sha256 checksum has changed, we overwrite the old file with the new one. You cannot recover the old file.
  • If a file in the new bag has the same name as a file in the old bag and the size and checksums have not changed, we do nothing.
  • If a file in the new bag did not exist in the old bag, we save it.
  • If a file in the old bag is not present in the new bag, we do not delete it.
This table shows what happens when you upload a new version of a previously ingested bag. 

 Old Bag  New Bag What's in Storage  Why
 bag-info.txt    bag-info.txt (changed)new version    Contents in new version have changed
 data/document.pdf data/document.pdf (unchanged) old version The document did not change
 (file not present) data/new_image.jpg new version File did not exist in old bag, but it's here now
 data/old_image.jpg (file not present) old version Although this file has been deleted from the new bag, we will not assume you want to delete it from storage. File deletion must be a deliberate act of the depositor. 

This update policy has three important implications.
  1. If you want to delete files from an ingested bag / intellectual object, you must do that deliberately. Currently, you can delete only through our Web UI.
  2. When you restore the bag described in the table above, you'll get back both old_image.jpg and new_image.jpg (unless you manually delete one of them before you restore).
  3. You can update metadata in a bag by uploading only the metadata, as long as there's at least one file in the data directory and the bag is otherwise valid. This may be useful for bags that contain 100GB of data and 100KB of frequently-updated metadata.


Updated on Apr 1, 2016 by Andrew Diamond (Version 2)