Open Source Document Management System | OpenKM

Hi,

I want to change file versioning from 1, 1.1, 1.2 ....etc to 1, 2, 3 etc ...
Please tell me how to do it .


Thanks
Ravi Kiran

Must be implemented and extension for doing it. It's not complicated but must be written. The idea is transform default jackrabbit version numbers to yours.

Document versioning is handled by the underline repository management engine (aka Jackrabbit). You need depth Jackrabbit source code knowledge to make this change. And this would not be JSR-170 compliant, of course.

On a related question....

How do you create a version 2.0 of a file? It seems a bit silly if you are only able to create versions 1.0 ... 1.n

Dean

Recently we have developed an extension for a costumer which a special version schema requirement. In the next major release of OpenKM will be easier to change this default behaviour, but for now you have to create an extension.

So how would we go about changing the major version number with that? Where do I get that extention?

I am looking into implementing openKM to manage Standard Operating Procedures (SOP) in the healthservice laboratory I work in but it needs to be able to update the version number to 2.0 whenever we are happy that the next document version is finished. The x.0 version numbers would be the "effective" versions of the SOP with the x.n versions being revision versions. Ones the document has been revised and approved it would move to x+1.0, etc..

I suppose I could have a section in openKM with effective versions of the documents and a section of revision work. Then move the documents from revision to effective when ready. Any advice?

OpenKM use Jackrabbit as content repository. Version naming in Jackrabbit is a bit weird, because there no an easy way of change the versioning schema. This is one of the reasons to leave Jackrabbit in the next major OpenKM release.

We just have made a custom extension for a costumer which use a personalized x.y.z document version. To achieve this, we had to work with database metadata, core extensions (to intercept the commit event and increase the custom document version depending on its state), a property group where store the document state and a couple of tweaks in OpenKM source code.

Not easy, but not impossible. The procedure is harder to explain than implement.

For these reasons, I don't recommend to try to implement it yourself. But if you don't want to expend a lot of time on it, go ahead. The cheaper way is to contact us and we can develop this costumization for you.

Thanks. I think I will go for the effective, old and revision section method. That way the document version problems doesn't really matter.

We are using Windows version 5.1.10 ( build 7564 ) . This is one of the best document management system (DMS) i came across.

We were just about to finalize this but the file versioning system is one of the requirement for us. I have just created 1.10 versions of the same document to check when it reaches 2.0, but after seeing this thread it seems that it will never change the version to 2.0

I think for any DMS this should be one of the requirement, because by seeing version we should be able to define as its a draft version or final approved version. So version control should be added to OpenKM.

Request : If possible please add the extension in community version also.

Regards,
SV

Version numering acts as three, start with node 1. the first version will be 1.0, next 1.1, 1.2 ( the 1. will never be changed you should imagine as tree nodes ).
When you go to older version for example you're in 1.2 and want to return to older then you are in node 1.1.1 the next version will be 1.1.2 etc... that's the idea of the version numering.

We have explained several times in this forum, from version 6.0 it's possible to create a class and decide the way you want to change version number.

About draft, approved etc... really this is more nearly from metadata than version number, for example other way to see it is minor changes and major changes ... as you can see there're a lot of ways to imagine numeric versioning, that's why the reason we decide in version 6.0 extending it, give someone by default and leave it available to be build in the way each user decide ( there's no valid numeric version for all users, we can not implementing all reason why is open to all users who will decide how build it ).

Comunity version 6 is still not availalble, and until september I think will not be available to release it ( in july / august some of us are on holidays and we're more involved on supporting and minor features than major releases ).

Hi,

I have just installed ver 6.2.0 (build 13077 ) on Windows XP machine. As you said above

"from version 6.0 it's possible to create a class and decide the way you want to change version number."

I am trying to find class to change the version number, but unable to do so. Please let me know where to do it?

thanks,

com.openkm.vernum.MajorMinorVersionNumerationAdapter at the package src/main/java/com/openkm/vernum you'll find what you need

As you can see, need to implement an interface. After, that set the version.numeration.adapter configuration property to your class.

Hello ,

Just downloaded 6.2.2 community version , build 7815 and installed in windows XP machine. I can see version.numeration.adapter setting in Administration->config.

I have read through Document version numeration in http://wiki.openkm.com/index.php/Applic ... figuration, and it states that for BranchVersionNumerationAdapter the version will be like 1, 2, 3, 2.1, 2.2, etc. But if i use this adapter, it starts with one and continue increasing like 1,2,3,4,5 etc.
how we can control the initial version like 1, 2 and the next version like 2.1 and 2.2.

Thanks for your help.

You need to determine when should change every major/minor version number. For example, a property group value or add a checkbox to the file upload dialog.