Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dead RDF resources #657

Open
loetie opened this issue Feb 7, 2020 · 1 comment
Open

Dead RDF resources #657

loetie opened this issue Feb 7, 2020 · 1 comment

Comments

@loetie
Copy link
Contributor

loetie commented Feb 7, 2020

When a RDF resource is created and the uri it links to is deleted, the rdf resource still exists in ginger. Leaving a dead resource (with relations within ginger).

For Erfgoed Brabant we want this, because sometimes collections are depublished and then published again. With the RDF resource still available all relations are also still available.

For CollectieGelderland it results in a non working homepage, since the data cannot be retrieved. Something you dont want.

For Geheugen van Drenthe we also keep the dead RDF resource but with a warning on the admin detail page.

What do we want to do with these kinds of resources.

@robvandenbogaard
Copy link
Contributor

I believe from the readme on https://github.com/driebit/ginger/tree/master/modules/mod_ginger_rdf that when an rdf resource is set to authoritative (normally rdf resources are not authoritative because the actual data source is external), mod_ginger_rdf would not try to retrieve the remote rdf data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants