Thorsten Scherler wrote:
[...]
That only makes sense when we introduce UUIDs since
otherwise we will run again in the egg chicken problem of meta data,
file and mapper.
This problem is solved. But what remains is the problem that meta data
sources have to be moved when document locations change.
well see the other thread, it is not really solved. ;)
Yes, unfortunately it can't be solved with the current architecture.
The problem is:
- a repository node stores its meta data
- the meta data source URI is derived from the node source URI
- the node source URI depends on the meta data (source extension)
I don't see a solution that doesn't require migrating the content.
IMO the cleanest solution would be a flat structure based on UUIDS.
/content/12345 -> document
/content/12345.meta -> meta data
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
