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

remove graphs for removed files #1

Closed
retog opened this issue Dec 17, 2022 · 3 comments · Fixed by #6
Closed

remove graphs for removed files #1

retog opened this issue Dec 17, 2022 · 3 comments · Fixed by #6
Assignees

Comments

@retog
Copy link
Collaborator

retog commented Dec 17, 2022

This query shows a graph for a file that doesn't exist.

SELECT * WHERE {
graph <https://github.com/raw/plazi/treatments-rdf/main/data/03/D2/AB/03D2AB06FFCE5139F8EC2395DCE9E30A> 
   {
      ?s ?p ?o .
   }
}
@retog retog changed the title remove graphs for removed graphs remove graphs for removed files Dec 17, 2022
@retog
Copy link
Collaborator Author

retog commented Jul 11, 2024

@nleanba : I hoped this would have been fixed with the refactoring, but the graph is still there. Should we delete all graphs and make a full update?

@nleanba
Copy link
Collaborator

nleanba commented Jul 12, 2024

I feel like this is the only real option. However, if we are going to replace all graphs, I think we should use that moment to change the graph uris to some that actually go somewhere (I suggest https://treatment.plazi.org/id/...)

nleanba added a commit that referenced this issue Jul 12, 2024
@nleanba nleanba linked a pull request Jul 12, 2024 that will close this issue
nleanba added a commit that referenced this issue Jul 25, 2024
@nleanba
Copy link
Collaborator

nleanba commented Jul 25, 2024

Currently, this full update is running. While it is running, https://treatment.ld.plazi.org/sparql only has a partial dataset (slowly growing). After the update is complete, it should have a full, correct, current dataset without any old/wrong graphs.

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

Successfully merging a pull request may close this issue.

2 participants