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
Currently Skosmos supports showing a single notation code for a concept. If we had two notation codes on the same concept, the behavior in Skosmos is not defined.
Who are the users that would benefit from the enhancement and how?
The feature is speculative in a way that such a situation is specified in the SKOS documantation, but we don't have a use case for it yet.
What new functionalities would the enhancement make possible?
We could have a SKOS browser that supports SKOS data structures!
The question remains, how to show an arbirary number of notation codes next to the concept label both in the title of a concept page and in the sidebar, like alphabetical listing and hierarchy views.
It is also possible to arrange concepts in an ordered list according to notation code, but we would need to specify how to handle the case of several notation codes on one concept.
Why is the enhancement important?
It is a SKOS feature we don't currently have support for.
The text was updated successfully, but these errors were encountered:
Description of the enhancement
Currently Skosmos supports showing a single notation code for a concept. If we had two notation codes on the same concept, the behavior in Skosmos is not defined.
Who are the users that would benefit from the enhancement and how?
The feature is speculative in a way that such a situation is specified in the SKOS documantation, but we don't have a use case for it yet.
What new functionalities would the enhancement make possible?
We could have a SKOS browser that supports SKOS data structures!
The question remains, how to show an arbirary number of notation codes next to the concept label both in the title of a concept page and in the sidebar, like alphabetical listing and hierarchy views.
It is also possible to arrange concepts in an ordered list according to notation code, but we would need to specify how to handle the case of several notation codes on one concept.
Why is the enhancement important?
It is a SKOS feature we don't currently have support for.
The text was updated successfully, but these errors were encountered: