Hi everyone,
Thanks Nino, that's just great.
> Thanks, I'll take a look. Is there anyway that someone on the
> documentation team to sketch out the workflow. You have developed
> this over a few years and we don't really have a workflow to work
> with. This would help to demistify workflow.
Maybe the drawing I created some time ago[1] (according to the
description given from Jean resp. the oooauthors list) can be helpful
for discussion. Feel free to use or change it. Note, that it may be
inaccurate or outdated.
Verbal description (AFAIR):
There are 2 main workflow pathways: A simple one for internal documents
and another one leading to externally published documents.
The internal path only has 2 states: draft & published internally.
The external path includes 3 different document states:
internal draft,
pending review (which means, submitted for publication),
published externally.
Internal published documents are owned by (who can edit it) a user, a open
group or a closed group (membership)? What is the difference between users
who can edit/create internal documents and those who can edit/create
externally published documents?
Transitions are, of course, submission, publication, and retraction (the
latter leading back to draft state[?])
L10N: Documents from any state might give rise to translation
activities, which again would open the same (or a similar) workflow for
the (now localized) document.
The main 2 problems in the (folder based) Plone system IMHO was to find
a document (where is the newest version?) and to get a quick overview
over the project state (how many documents are in which state, how many
untranslated documents, etc.). Hence, keeping track over the project
had to be done mainly by a human (i.e. Jean ).
Also missing are "minor" state informations e.g. "checked for software
version X.Y" or "indexed" or "branding updated" or similar (which is a
minor point but nice2have, and could be done e.g. by tagging).
No problem, this can be done with "Taxonomy" feature within Drupal. Also
with "Views" we can generate reports on that information. What kind of
reports would you like to have?
- List of internal documents, ordered by date. (each document, "node", as
revisions, so no problem, almost like a wiki).
- List of internal documents, grouped by workflow state.
- List of internal documents, filtered manually with terms (published for X,
Y, etc).
... What more?
I really think we are going to need a Dashboard on the website so users
can accommodate their work or interest on their dashboard.
Cheers
Note/Question: Should I cross-list?