Joachim Wolfgang Kaltz wrote:
Andreas Hartmann schrieb:
(...)
Maybe the identification problem (e.g. restoring after archiving)
could be solved by meta data queries etc. Or maybe you have another
idea how to solve it? Or do we have to design the system in a way that
this should never be necessary?
IMO identification in that sense is dependent on how a specific
publication ("default", "wiki", "blog", ...) constructs a site based on:
- a bunch of content items (stored by the repository)
- a navigation model (for example, the sitetree xml of the default
publication)
If the navigation model is just some XML file (like the sitetree in the
default publication), you can store that too in the repository. I'm not
sure I see a problem for restoring after archiving in this case ?
If somebody creates a different publication, with a different navigation
model that is not easily restored, then she is responsible for
implementing publication-specific restoration.
That sounds reasonable.
Thanks for your comments!
-- 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]
