nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Wrong (CMIS) version status after simply importing a document file?

Edgar_

Hi,

I wonder about the version status (CMIS nuxeo:isCheckedIn) after I uploaded a file via the web interface. isCheckedIn is FALSE, which prevents a CMIS user to check out the requested document subsequently. Currently the CMIS user must first check in the 'checked out document' to get around.

Regards

Find more posts tagged with

Accepted answers

ron_1

By default, documents created via the Nuxeo Web UI are not yet archived and therefore not yet formally versioned. They are considered initial "Working Copies" in this state and are displayed in the UI with "version" 0.0. This is similar to CMIS document creation with a versioning state of NONE.

In Nuxeo, you must select the the "Edit" tab for the document, select "Increment version" radio button, and then Save in order to version the document. See Nuxeo Versioning for more information.

Once NXP-8965 is resolved, it would seem useful to include the versioning widget on the create form in addition to the edit form. Then a Nuxeo Web user could version the document as part of document creation just like CMIS.

All comments

ron_1

In Nuxeo, you must select the the "Edit" tab for the document, select "Increment version" radio button, and then Save in order to version the document. See Nuxeo Versioning for more information.

Edgar_

Thanks for the documentation hint.

ron_1

There is a reason why the CMIS versioning state of NONE exists. For example, in some scenarios an optimistic locking scheme is more appropriate to manage concurrent access to documents than the pessimistic check-in/check-out version-centric model. CMIS supports optimistic locking using a changeToken. In many of these scenarios, there is no need to archive the document at every change so the overhead required to store every document version is avoided.

Florent_Guillau

The default Nuxeo versioning scheme is "web-oriented", where people create documents with metadata through a web interface and when they're satisfied with it, record a snapshot through versioning. The initial creation can take several steps, go through a workflow or validation, and that's why we don't record a version at this stage.