As a CLARIAH service, I want to be able to harvest LD from the media suite, so I can import this in the CLARIAH core

jblom commented 6 years ago

Prerequisites

investigate what would be the selection criteria for isolating triples that need to be harvested
investigate what harvesting protocol/service is required for WP2 (it should be something using a sitemap)

Acceptance criteria

[ ] implement the supplier for the harvest endpoint and make sure it filters out triples that are not meant to be harvested by following the investigated selection criteria
[ ] implement the harvesting endpoint for the WP2 harvester
[ ] test whether the endpoint indeed puts new data "on the top" by keeping track of the import date of each record
[ ] deploy the harvesting endpoint in the test environment

wmelder commented 3 years ago

It seems that this functionality is (at least partly) implemented in the lod-importer. See: https://github.com/beeldengeluid/lod-importer/wiki

wmelder commented 2 years ago

@jblom Do we need to keep this issue? I think we provide now a SPARQL endpoint that could be used by Clariah, or when we need an endpoint containing ALL NISV data, we would have to work on an endpoint providing ALL properties, but this would probably also have to be done using the NISV internal ontology.

beeldengeluid / beng-lod-server

As a CLARIAH service, I want to be able to harvest LD from the media suite, so I can import this in the CLARIAH core #2