Open manonthegithub opened 5 months ago
also, why the artifacts are hard-coded?
2022.12.01
https://databus.dbpedia.org/marvin/generic
en
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX dcat: <http://www.w3.org/ns/dcat#>
PREFIX dct: <http://purl.org/dc/terms/>
PREFIX dcv: <https://dataid.dbpedia.org/databus-cv#>
PREFIX databus: <https://dataid.dbpedia.org/databus#>
SELECT ?file WHERE
{
GRAPH ?g
{
?dataset databus:group <https://databus.dbpedia.org/marvin/generic> .
{ ?distribution <https://dataid.dbpedia.org/databus-cv#lang> 'en' . }
{ ?distribution <http://purl.org/dc/terms/hasVersion> '2022.12.01' . }
{
?dataset databus:artifact <https://databus.dbpedia.org/marvin/generic/anchor-text> .
}
UNION
{
?dataset databus:artifact <https://databus.dbpedia.org/marvin/generic/article-templates> .
}
UNION
{
?dataset databus:artifact <https://databus.dbpedia.org/marvin/generic/categories> .
}
UNION
{
?dataset databus:artifact <https://databus.dbpedia.org/marvin/generic/citations> .
}
UNION
{
?dataset databus:artifact <https://databus.dbpedia.org/marvin/generic/commons-sameas-links> .
}
UNION
{
?dataset databus:artifact <https://databus.dbpedia.org/marvin/generic/disambiguations> .
}
?dataset dcat:distribution ?distribution .
?distribution databus:file ?file .
}
}
@m1ci
also, why the artifacts are hard-coded?
2022.12.01
https://databus.dbpedia.org/marvin/generic
en
I don't think they are :). The query is generated just like this with artefact names as consts...
there are many more artifacts and the question is why they are not in the query?
The query generator was being passed the wrong array of artifacts (the currently displayed ones instead of all) The first issue still persists, the query generator is not working correctly here.
there's no hard-coded SPARQL, the queries are generated.
Working on a fix
what @manonthegithub wrote seems duplicate to this here https://github.com/dbpedia/databus/issues/124 but @m1ci thing might be something different. but I am not sure. so maybe rename/clarify/clean up the issue if its not already fixed.
possible fix deployed on dev
On the screenshot geo-coordinates filter didn't work