Business case for archiving content hosted in AGO. Archiving/un-archiving vs deleting/recreating.
Data (hosted feature and tile services) storage is the biggest cost. When projects are shelved for extended periods of time, but not necessarily permanently in which case content could just be deleted, it would be useful to be able to tag an app or a map as "archived". All hosted content referenced by the app, and owned by the same owner of the app could also be automatically tagged as archived.
Content tagged as archived would then be disabled (unaccessible) and charged a reduced rate for service credits.
Archived content could be easily un-archived/made accessible. Organizations would realize a credit saving for archived content and maximize good use of staff time. Archiving could be more efficient than republishing content and rebuilding maps and apps if content was deleted and project needed to be recreated.
The notion of archiving could also be useful for audit or record requirements.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.