Open nichtich opened 3 years ago
The data structure is:
prefLabel
(multilingual name of the link target)url
(URL template)Open question which JSKOS field to put them in.
A search link is basically JSKOS Occurrence with prefLabel
in database
and the url
filled out as template with {notation}
or {uri}
.
In addition to links based on URL templates, we can also support Occurrences API. The current API is not formally specified query parameters are:
uri
(s) of a concept(s))voc
)limit
)notation
(not supported yet)BARTOC could also aggregate search links into an occurrences API.
For cataloging search links we need
database.preflabel
).template
?)and/or
api
)search links for K10plus can be determined automatically via CQL key.
Maybe better start by managing search links in a repository of its own to facilitate inclusion in BARTOC, Cocoda, Occurrence API and other applications.
See https://github.com/gbv/occurrences-api/blob/main/links.json for a start.
These are best managed in BARTOC instead of Cocoda. See https://github.com/gbv/cocoda/issues/565