Open ktk opened 4 years ago
Currently it is only possible to restrict the amount of datasets listed in the API by defining which graph should be used to fetch a list of datasets.
For endpoints like LINDAS where we have many dataset there needs to be another way or restricting it.
We might consider using dcterms:subject as mentioned in the RDF Data Cube spec: https://www.w3.org/TR/vocab-data-cube/#metadata-categorization.
The API would then need an option to query all datasets that are part of the same subject.
Another use case for subject(s) or similar metadata could be to allow filtering a list of datasets interactively in the client. For this we'd need to be able to match subject(s)
Example mockup:
Currently it is only possible to restrict the amount of datasets listed in the API by defining which graph should be used to fetch a list of datasets.
For endpoints like LINDAS where we have many dataset there needs to be another way or restricting it.
We might consider using dcterms:subject as mentioned in the RDF Data Cube spec: https://www.w3.org/TR/vocab-data-cube/#metadata-categorization.
The API would then need an option to query all datasets that are part of the same subject.