Discussion: SkoHub Vocabs Index Page

[sroertgen]

As already being started to discussed in #214 I'm opening the discussion here for the further design and functionality of the index page.

I'm copying over @acka47 arguments

+1 for following the approach in the screenshot of #214 (comment) for now. We should then put some general thought into this and adjust further.

• I don't see the need to have the name of the software on such a prominent place like we have now.
• It doesn't seem intuitive that the software name links to an overview of vocabularies in the same GitHub repo.

We should invite @kaena83 to the conversation as she has some experience with UX design.

and

One last thought.

Premises:

1. My general problem is with the list showing vocabularies from one specific GitHub repo. This seems arbitrary but might encourage people to publish all their vocabs from one repo which – from my point of view – should not become best practice.
2. We want to encourage people to set up their own –institutional or personal – SkoHub Vocabs instances.

I conclude with a question:

Shouldn't the overview page then show all vocabularies published via the specific SkoHub instance, regardless of the git repo they are residing in? (With a possibility to filter the list for organisations with a larger set of vocabs.)

[sroertgen]

regarding

• I don't see the need to have the name of the software on such a prominent place like we have now.
• It doesn't seem intuitive that the software name links to an overview of vocabularies in the same GitHub repo.

I totally agree. I think this will be more intuitive if we think of replacing "SkoHub Vocabs" with the name of the institution / project which hosts the vocabularies. With solving #188 and #185 it should be easy to change the name and therefore it will be more intuitive to click on it and get directed to an vocabs overview page.

Shouldn't the overview page then show all vocabularies published via the specific SkoHub instance, regardless of the git repo they are residing in? (With a possibility to filter the list for organisations with a larger set of vocabs.)

That sounds really interesting. Maybe this can also be thought of in context of #185. If the info about vocabularies that should be shown on a index page is given there, we could further list them.

In general I'm more in favor of thinking about what benefits that index page can add to SkoHub Vocabs instead of removing it. I think it is a nice feature to browse different vocabs without having to manually go to a different URL, but to navigate within the application. So this might be in line with your last raised question.

[nichtich]

For BARTOC we need a machine-readable list of vocabularies published via a given Skohub instance to integrate data about its vocabularies with information in BARTOC. At the moment we have indexed six vocabularies in BARTOC with their Skohub URL but this data has been collected manually and sure there are more.

Apart from the technical solution this is about documentation. It should be made clear "Skohub" is a software and "SkoHub Vocabs" is just one instance. Maybe the index page could also link to other Skohub instances?