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.

Assets in one workspace, originals in another.

Pros

Cons

References will need to be by uuid only

Streaming the original will require support an additional workspace

Assets under /assets and originals under /originals

Pros

References can be JCR properties of reference type

Cons

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

Findig the original given an asset is trivial

Detecting when the original is not used by any assets is trivial

Enumerating the assets using an original is trivial

Cons

Not ideal for the workbench component as it will need to hide the original but show the assets beneath it.

Ordering assets will only be possible among the assets having the same original

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

Q: In what ways does the original differ from the asset? Do we use the same node type for instance?

We must remove the original when the last asset linking to it is removed

Reuse of content when asset and original is identical to reduce the size of the repository