On Fri, 04 Feb 2011, Johannes Gutleber wrote: > I consider the invenio software as a document server for a project.
Do you mean you are considering to set up a new Invenio instance, or perhaps reuse an already existing Invenio instance such as CDS at CERN? > - versioning of submitted documents As Alexander hinted, some documentation can be found in BibUpload Admin Guide and BibEdit Admin Guide. Basically, Invenio stores (i) every metadata revision update and (ii) every attached file revision update. The metadata revisions are usually hidden to end users and only visible to the administrators; the end users only see the latest record version. The file revisions are usually public to end users, but can be made hidden if need be. The versioning setup can be configurable to a large extent. For example, we have some special collections at CDS where various versions of the same pre-publication document live alongside each other and authorized users can see/use/comment on them within various deadlines. This does not use the generic out-of-the-box versioning facility, but uses independent records as versions. Does this cover what you were thinking about? We can be more specific if you tell me what your concrete use case would be. > - defining an approval workflow for submitted documents including > reviewing Invenio sources contain a simple approval workflow demo, see the Demo Book Submission. The publiline facility hinted to by Alexander permits to introduce more complex submission lines. A word of warning though: the generic Invenio version of publiline is somewhat dirty at this moment, we have more complex examples at CDS that we are trying to polish and commit back to generic Invenio sources. Please tell us more details about your approval needs together with a concrete use case or two. Depending on your needs, the approval workflow can already be well covered. Best regards -- Tibor Simko
