Requirements
The DAM will have a concept of originals, where the file you upload is kept as an original that you can revert an asset back to later on.
Alternative 1 - Separate workspaces
Assets in one workspace, originals in another.
Pros
Cons
Alternative 2 - Separated by path
Assets under /assets and originals under /originals
Pros
Cons
Alternative 3 - Mixed in the same tree
Since an asset refers to exactly one master we could have a tree of folders and originals with the assets as sub nodes of the original.
Pros
Cons
Additionally
Q: What is the id/name of an original? Is it important at all?
Q: How do we create a hierarchy of originals? We want to avoid a flat structure in JCR
We must remove the original when the last asset linking to it is removed
Future improvements
Reuse of content when asset and original is identical
Overview
Content Tools