Project management and model versioning

[Peter Viskup]

Dear vocbench community,

we do struggle with proper project management and model versioning.

ATM we do have new project for every version e.g. project name of "egov-2026-q1" which seems like not proper handling and use of vocbench as the number of projects is growing fast.

Could you, please, point out the functionality we might use and how 'data models' are regularly released?

Tried to find it in guides, but with no luck.

We have vocbench 10.x deployed and just plan to upgrade it.

Thank you.

Best regards,

Peter Viskup

[stel...@uniroma2.it]

Dear Peter,

 

Thanks for rising this up. I’ve two answers, one with the current VB (and I think it is valid for the version you have now as well) and one for the forthcoming version of VB.

 

Current version of VB (10.x included) :

You can use the “versioning” support. This allows you to store a read-only snapshot of the current status of your dataset into a different repository, yet still within the same project. You can open it from here:

https://vocbench.uniroma2.it/doc/user/global_data_management.jsf

Apologies, the site is currently down due to network issues today in my university but you cam figure it out very easily directly from VB

Additional functionalities are available, such as a time machine and the possibility to move in between stored versions. There is also a time machine for reconstructing (if you are using history) the status of any resource at any point in time, but the TM based on versions is way faster and more complete (just limited to stored versions, hence the existence of both options).

 

Next version of VB (ETA: end of January/first days of February)

There will be the possibility to have different editable versions (branches) stored on different repositories but all managed within the same project. New editable branches can also be generated from stored read-only versions. More details will follow but that’s the general improvement.

 

I didn’t fully get the question about release of data models. However, in case you don’t know, there is another system: ShowVoc, which is the perfect companion to VB for data dissemination. https://showvoc.uniroma2.it (again, sorry for the temporary situation on the sites). It supports content negotiation (at least handles most of the negotiation, demanding obviously to your front servers the initial routing of your URI requests to SV), and offers a UI similar to VB but focused on content provision rather than editing, and several cross-dataset functionalities.

Even for SV, the next release will feature the possibility to have several versions under the same project and there will be an improved metadata registry providing global metadata about all the hosted datasets and their versions.

 

Kind Regards,

 

Armando

 

 

 

 

 

 

Da: vocben...@googlegroups.com <vocben...@googlegroups.com> Per conto di Peter Viskup
Inviato: martedì 13 gennaio 2026 20:02
A: vocben...@googlegroups.com
Oggetto: [vocbench-user] Project management and model versioning

--
You received this message because you are subscribed to the Google Groups "vocbench-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vocbench-use...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vocbench-user/CA%2BGAPA6fmYDortq-OVsCDbFo5nRyw08cJAoMEHM-2s3fdsvc7w%40mail.gmail.com.

[Peter Viskup]

Thank you for your prompt answer.

We will have a look on it on our side.

The other questions are...

What are the consequences of our suboptimal use of separate projects for model versions?

Is there any way to merge them with pertaining the complete history of changes?

Unfortunately I don't know the process used for creating new project/version in our current setup. Thus just trying to complete inputs for the upcoming discussion with the responsible team.

Is there anybody open to voluntarily help us with clean this up? We are public administration agency in Slovakia.

Best regards,

Peter

Dňa st 14. 1. 2026, 15:37 <stel...@uniroma2.it> napísal(a):

[stel...@uniroma2.it]

Dear Peter,

 

can’t assure 100% that all options will be available in the forthcoming version but:

 

1. You will be able at least to bring different projects under the same “dataset” (almost for sure)
1. Different projects, even under the same dataset, won’t give you the time-machine, at least on the new release, but will in any case present all versions under the notions of a same dataset
2. Possibly from next release too, you will be able to save the data of one project and load it into another one as a stable (non-editable, but browsable) version

 

Kind Regards,

 

Armando