Archiving in place

[#1]

Request for Feature Enhancement (RFE) Summary:	I would like to change the backend storage of assets based on its metadata while keeping the assets where they are in the DAM.
Use-case:	I would like to set up a property called Archive with a yes checkbox. When the box is not checked the asset is stored in active storage on the backend. When the status box is checked the asset is moved to glacier storage in the backend. So the asset stays in the same location in the DAM interface but the storage of it on the backend is dependent on the metadata in one of the properties.
Current/Experienced Behavior:	Archived assets are moved to a folder and all assets in that folder get moved to glacier storage on the backend.
Improved/Expected Behavior:	Backend storage is based on the metadata of an asset instead of what folder it is in.
Environment Details (AEM version/service pack, any other specifics if applicable):
Customer-name/Organization name:	Dario Mescia/Enterprise Mobility
Screenshot (if applicable):
Code package (if applicable):

[#2]

Can you please provide any rationale for this feature? What is the expected change when this checkbox is checked?

• Why do you want to move the binary to a cold-storage instead of the regular storage? For cost reasons?
• What would be the impact when the asset was moved to cold-storage? Would it still be fully accessible as it is today, for example as part of searches, can be linked as any other asset?

[#3]

I want to move it to cold storage for cheaper storage. We have a mandate to keep all of our assets indefinitely for legal purposes. This leads to a constantly growing pool of assets. When its moved to cold storage I'd like it to still be findable to the people with permission to see it but it would be a proxy instead of the original asset. If someone then needs to use the original, it would take a good bit of time to retrieve it and make it active again. 

The reason I want to keep everything where they are is that with a system like AEM which is very folder structure oriented it is very difficult to manage assets if I have to move them to a separate location to archive them. And some of the archived assets may still have a use in the future for things like historical projects so they still need to be searchable. The goal is that once assets are organized, tagged and catalogued they stay exactly where they are for their entire lifecycle. When they are archived the storage simply changes on the backend. There are other DAMs and MAMs that can do this.

[#4]

@dmescia2 Thanks for proposing this idea. This has been reported to the engineering under the internal reference ASSETS-54190. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.