normalize standalone collection objects to be in "/digital/objects/collectionstub/" rather than being in other places (usually in "/digital/collectionstub/objects").
Keeping all objects together in one dir makes it easy to make sure they are being archived and backed up, and could be migrated to new object storage easily. Also keeps the generated part of each collection clean (so the html dirs can just be deleted and rebuilt from source to clean up-- earlier experience show that having the objects in the html dir leads to accidental deletion...).
probably do in conjunction with setting up a separate cb-standalone-template for UI.
normalize standalone collection objects to be in "/digital/objects/collectionstub/" rather than being in other places (usually in "/digital/collectionstub/objects").
Keeping all objects together in one dir makes it easy to make sure they are being archived and backed up, and could be migrated to new object storage easily. Also keeps the generated part of each collection clean (so the html dirs can just be deleted and rebuilt from source to clean up-- earlier experience show that having the objects in the html dir leads to accidental deletion...).
probably do in conjunction with setting up a separate cb-standalone-template for UI.