J. Wolfgang Kaltz wrote:
Andreas Hartmann schrieb:
Michael Wechner wrote:
[...]
I think you can still store the documents in a structured way, but
each document
has a unique ID which is mapped onto the path within the
hierarchy/structure, e.g. by
hashmap. This unique ID (uid) is then being used within the Scheduler
or for references
for instance and not the path itself.
IMO this is mostly a usability problem at document creation time. Right
now when the user creates a new document in the default publication, she
has to guess a document id which does not exist in this branch. This is
not ideal but still acceptable, as typically there will only be a few
documents within that branch. But if we want the user to provide a
publication-wide unique id at creation, Lenya will need to propose such
an id in the creation mask (a sort of auto-increment).
IMO the unique ID should be opaque to the user.
It can be auto generated on document creation and doesn't have to be
human-readable.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
