search

zazuko / amos

Archiv Museum ohne Schliesszeiten
1 stars 0 forks source link

Fix broken IIIF manifests #89

Closed ludovicm67 closed 2 years ago

ludovicm67 commented 2 years ago

We have a Trifid plugin who is in charge of building the right IIIF manifest. But we currently have some issue: they look broken.

When I investigated last time, the issue was coming from the way the triplestore was handling the blank nodes. CLEAR the graph, triggering the pipeline again and clearing the cache was solving the issue last time.

Maybe using PUT instead of POST when writing in the graphs may solve this issue?

ktk commented 2 years ago

That's probably because bnode IDs are preserved right now on the amos DB, so we create clashes if we re-use IDs. This can be fixed by taking the DB offline, change the preserve.bnode.id setting to off & re-write the data (after a clear).

See https://docs.stardog.com/operating-stardog/database-administration/database-configuration#preservebnodeids

ludovicm67 commented 2 years ago

The setting is already off, so this is not the issue. Maybe the fault of some old data? I will clear everything in that database and deploy everything back there by running the deploy step from the pipeline.

ludovicm67 commented 2 years ago

It's now able to generate working manifests again.