Jörn Nettingsmeier schrieb:
[...]
IIRC the latest consensus was:
The workflow should not be initialized when the document is created.
This way, the fact if a document has a workflow only depends on the
resourcetype -> workflow assigment in publication.xconf. As long as
the document has no workflow history, it is in the initial workflow
state.
If you think that this behavior is wrong, feel free to restart the
discussion :)
i'm not sure if i understand this. right now, the following seems to
happen when somebody creates a document with the default creator:
* a new document is created by copying the doctype sample;
* a metadata file is created.
this metadata has no <workflowVersion/> elements yet. all i'm asking is
that upon creation, a workflowVersion entry with number 0 and
"event:create" is created, stating the date of creation and the user who
did it.
That would require that the workflow schema contains a state
"non-existent" with a transition to the state "authoring", triggered
by the event "create". Does this make sense? What do the others think?
this seems to be orthogonal to the actual workflow definition for a
doctype (i.e. how many stages etc.), and i don't see how this could
possibly have implications for the robustness of the repository.
It would mean that
- either you can't add documents without adding the workflow meta data
- or the system would have to handle both types (with and without
workflow meta data) in the same way.
"event:create" is an event outside of whatever workflow you want to define.
-1
IMO there shouldn't be "system" events which are not defined by the
workflow schema.
the reason i want this is to be able to display meta information on the
page ("last modified on <date> by <user>", or even "created by <user>").
I'd rather handle this separated from the workflow, e.g. using
a "created:" meta data entry.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
