Clean up loading scheme/concept data in front end

[stefandesu]

• [ ] In VocabularySearch, kostypes and licenses are loaded:

https://github.com/gbv/bartoc.org/blob/b76a0aaaf3ff539a52f1a46eb1167d8292d0a2d3/vue/components/VocabularySearch.vue#L93-L101

• [ ] Hardcoded scheme/API URL in LanguageSelect:

https://github.com/gbv/bartoc.org/blob/b76a0aaaf3ff539a52f1a46eb1167d8292d0a2d3/vue/components/LanguageSelect.vue#L37

• [ ] Loading kostypes/licenses/formats/access/registries in ItemEditor:

https://github.com/gbv/bartoc.org/blob/b76a0aaaf3ff539a52f1a46eb1167d8292d0a2d3/vue/components/ItemEditor.vue#L390-L399

• [ ] Hardcoded indexing schemes in utils.js:

https://github.com/gbv/bartoc.org/blob/b76a0aaaf3ff539a52f1a46eb1167d8292d0a2d3/vue/utils.js#L24-L51

• [ ] Different ways of loading concepts/initializing registries/etc.:

https://github.com/gbv/bartoc.org/blob/b76a0aaaf3ff539a52f1a46eb1167d8292d0a2d3/vue/utils.js#L53-L71

Questions:

• Can we preload some of these on the server (or during build of the front-end) and provide the data on page load? If yes, do we want to do that or should we let the client do it?
• Does it make sense to clean this up in a way that the server can use the same code? Are we even using cocoda-sdk on the server side of things?
• Is there a need of putting some of this into the configuration?

[nichtich]

Concept loading from schemes internally used in BARTOC (licenses, languages, DDC100...) is used

1. for display of human readable labels (server side also in https://github.com/gbv/bartoc.org/blob/main/views/item.ejs).
2. for selection (in search and editor)

Some schemes are fairly small so they could be embedded in the page. Search form seems slow at the moment, but possibly for other reasons, so it's unclear whether embedding a full vocabulary in the page is worth the effort.

All schemes except ILC and EuroVoc are locally available, it makes sense to also get them into the local jskos server instance used by BARTOC, so we can use the same cdk registry for all of them.

How about removing loadConcepts and move loading of concepts into the select component just as done with ItemSelect and LanguageSelect? I think it makes sense to put the list of these schemes into the configuration (or a non-configurable JSON file) such as indexingSchemes, so .

[stefandesu]

All schemes except ILC and EuroVoc are locally available, it makes sense to also get them into the local jskos server instance used by BARTOC, so we can use the same cdk registry for all of them.

My thought was rather that the metadata for those vocabularies should be statically provided and have the API information included so that the client knows how to access it. In my opinion, this would be the most elegant solution. Hosting them inside the BARTOC database only because they are used for subjects seems overkill to me.

Search form seems slow at the moment

Looking at the network tab, it seems to be that it actually might be related to having to load top concepts for several vocabularies before the search can be used.