Driving Scenario: TERRA-REF project uses file path uploading to create file entries in Clowder that point to mounted file paths (i.e. data bytes are not stored in MongoDB). TERRA's 1PB allocation on storage condo is filling up, necessitating some files (likely starting with raw data from 2016+) be moved into tape storage or offsite backup.

However for referencing and metadata purposes, we want to retain entries in Clowder for data that we archive. However, data will obviously not be available for download at that point as the on-disk source has been removed. If we incorporate a new status, ARCHIVED, to the file pages:

(see bottom PROCESSED)

...we could even include some kind of text or configurable place per instance that describes what to do or who to contact if a user wants to access an archived file.

A simple start would be:

• support for ARCHIVED Status
• API for assigning the status to a file
• UI for same (less urgent, archiving will not be done via user interface)
• Simple page with configurable text when someone tries to download an Archived file
  • "Please contact the Clowder administrator for information on accessing archived data."