You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: