You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is a bit of brain dump of ideas for other features...
It'd be nice to know how many codes are in each codelist (at an aggregate level). The query for that isn't too slow but it may still want to be in a separate request (and possibly with async update after the components are loaded). We might alternatively have a separate codelists index. Knowing which codes are used is also useful. We don't need a page for the codes/ codelist itself as we have this on PMD itself.
It'd be nice to distinguish dimensions, attributes and measures. This could be through separate pages or by filtering on one page. Having all components on one page means you don't need to know if advance which type you're looking for (e.g. with "CTRL-F").
It'd also be nice to see a list of units.
More generally, it'd be good to see the class hierarchy as we begin to flesh this out.
We might also have a URI deference tool or perhaps some sort of URI search (this would likely need to be powered by OOK/ ES as substring search on Stardog times out).
The text was updated successfully, but these errors were encountered:
Ideally we'd gather the URI templates but if we provide example codes for each class then people might be able to guess the URI patterns. We might want one example per codelist or class (not including skos:Concept).
This issue is a bit of brain dump of ideas for other features...
It'd be nice to know how many codes are in each codelist (at an aggregate level). The query for that isn't too slow but it may still want to be in a separate request (and possibly with async update after the components are loaded). We might alternatively have a separate codelists index. Knowing which codes are used is also useful. We don't need a page for the codes/ codelist itself as we have this on PMD itself.
It'd be nice to distinguish dimensions, attributes and measures. This could be through separate pages or by filtering on one page. Having all components on one page means you don't need to know if advance which type you're looking for (e.g. with "CTRL-F").
It'd also be nice to see a list of units.
More generally, it'd be good to see the class hierarchy as we begin to flesh this out.
We might also have a URI deference tool or perhaps some sort of URI search (this would likely need to be powered by OOK/ ES as substring search on Stardog times out).
The text was updated successfully, but these errors were encountered: