Concordances cannot be created for all vocabularies

[nichtich]

Creation of a concordance requires both vocabularies being mapped to be available (its metadata) in JSKOS Server instance where the concordance is going to be created. The user interface, however, allows to use all vocabularies.

Just filtering out vocabularies would neither be good, so not sure about best workaround.

[stefandesu]

This is why, in our main concordance registry, we import the vocabulary metadata for all relevant vocabularies: https://github.com/gbv/coli-conc-server/blob/a402a21613cfac4a7839235aa51349fe4bc0140b/configs/vocabularies.txt#L12-L13

I guess the issue is that this isn't updated often enough, so if the list of vocabularies changes, they are not immediately reflected in the JSKOS Server instance.

[nichtich]

Things to consider:

• We will likely have more than one main Cocoda instance next year, each with their list of vocabularies
• The list of vocabularies can be changed via BARTOC but if a vocabulary is added, it would be best to directly use it for concordances
• This problem does not occur frequently