VocBench Tips & Tricks

This page reports on solutions for resolving specific needs, going further than the user manual. While the user manual plainly explains the various features of VocBench, here we go bottom-up: starting from a need, we describe how this need can be covered in VocBench through its features (possibly, through a combination of them).

Dataset Maintenance with Externally Provided Information

We are regularly adding language labels and translated the descriptors of the source vocabulary (in English only) into other languages. These updates come with new descriptors, and a few redirections, term rejections.

What strategy should we follow with VocBench?. Do we manually enter the term network for the newly added terms? or do we have any other alternate mechanical process to merge newly added terms into the VocBench?

I guess the most important questions are:

  1. Which sort of policy you adopt for maintaining your vocabulary, some questions:
    1. do you have *also* people maintaining on it natively in VB or is it only gathering new addenda from outside?
      1. In the former case, are you using validation?
      2. In the latter case, you always get a completely new version of the vocabulary or only the addenda? ‘cause from your sentence it seems you are getting a new version of the vocabulary entirely
  2. How big are the smaller parts of that new data you ingest? E.g. the rejections, redirections…
  3. How are you getting the new data? is that “source” format you described in point 1? Can you easily make a spreadsheet out of it?

Based on the above (and possibly other) questions it is possible to lay down a strategy. However, to give some possible answers in advance:

In case of 1.a.i:

In case of 1.a.ii

Concerning how to ingest the data, and besides the considerations above (which are, in short, if there’s no maintenance being done in VB3 and it comes from external sources only and if there’s no history being kept in VB, then no need to work on the delta and instead reconvert everything from scratch each time), there are several solutions in VB3:


Story: Multiple scheme and hierarchy management

I would like to manage multiple schemes within a same SKOS dataset. The schemes are managed by different groups/organizations and I would even like to have different hierarchies per each scheme.

This is indeed a complex story, for which we have created a dedicated page.