Closed awagner-mainz closed 2 years ago
I pushed @literarymachine's fix to dev
. With #115 implemented this was automatically deployed to test.skohub.io. (It worked, @dr0i. Thanks!). I triggered a new build from my fork of the vocab and it looks fine, see https://test.skohub.io/acka47/vocabs-polmat/heads/main/w3id.org/rg-mpg-de/polmat/n01.4esp.5.e.de.html So +1 from me.
@awagner-mainz, please test it yourself and let us know if we can deploy this to production.
@literarymachine said in https://github.com/skohub-io/skohub-vocabs/pull/158#issue-1008520253:
I am not entirely sure how it might impact performance.
The static site for https://github.com/acka47/vocabs-polmat was built in two minutes so I think this is fine. The HTML is fast as always too.
Yes, it's working now: https://test.skohub.io/rg-mpg-de/vocabs-polmat/heads/main/w3id.org/rg-mpg-de/polmat/n01.4esp.5.e.02.en.html. Thank you so much ... and sorry for the delay in testing this.
This may be an idiosyncratic need, but my SKOS has exactly one level more than Skohub supports. While the subconcepts are listed in the Json-LD view, they are not displayed/navigable/searchable in the web view.
Would it be possible to increase the depth of the SKOS tree processed by Skohub (by one would be sufficient in my case)? Or can this be made to be configurable somehow?