Open stefandesu opened 3 years ago
The current example is enough to start with but it cut get extended to a full vue component for vocabulary search and browsing (given a cocoda-sdk registry and a scheme , plus preferred language). This component could be integrated into BARTOC.org.
I added a first version of the example in
vue-browsing/
. However, it seems like STW is not the best example for that, or we need to fix the issue. If you try out the example, and you browse a few levels deep, you will notice that the notation is missing for ancestor concepts. This is because of two reasons:/broaderTransitive
endpoint we use in cocoda-sdk does not return notations for concepts.http://zbw.eu/stw/thsys/v
(V Economics), below that for examplehttp://zbw.eu/stw/thsys/70234
(V.03 Macroeconomics), and then suddenlyhttp://zbw.eu/stw/descriptor/10253-0
(10253-0 Macroeconometrics). Since oururiPattern
only works for descriptors, the notation for the first two can't be determined. And looking at the second one, the notation is not in the URI anyway.I think it would be better to have a more straightforward vocabulary. STW also seems like it isn't monohierarchical. I guess instead of ancestors, we could show broader concepts. What do you think, @nichtich? (However, this would not solve the other issue because
/broader
doesn't seem to return notations either.)Edit: Another weird thing about STW is that for the non-descriptors, the notation is inside the label. In theory, this means that not having the notation isn't too bad, but in practice, this is 1) weird because if we have the notation (like we have for the other requests), it is shown twice, and 2) if we save a mapping with one of those concepts where we don't have the notation, we can't find that mapping when searching by notation. This is unrelated to this issue, but still a problem when working with STW through Skosmos.