Latest Version of a collection ambiguity

[datalogism]

Hello folks!
I just wanna give you feedback concerning the "latest version" option of the databus.
That is an issue that i notice this month as the last snapshot release only contains mappings data for the english version.
I was expecting to get all the latest data for the french chapter, but as the "latest version" option seems to be fixed to the latest version created i cannot get the entire dataset i wanted to obtain.
The "perfect solution" in my point of view would be to be able to grab all the collections i selected in the databus even if one of them is older than the other. Because in my case i was constrained to download the missing artifact manually. (i have got the option to custom also directly the SPARQL query but i think that it could break all the GUI possibilities)
That is not a "hot issue" for me but i preferred to report you before forgetting it !

[JJ-Author]

hello :-). I agree. I think that we changed the behavior on the Databus 2.0.x however I am not sure whether the new behaviour is exactly what you are looking for. I dont know how familiar you are already with it ? maybe you can build a minimal example on the dev databus and see if it works as expected for you or you wait a little and maybe @holycrab13 can run the migration script again so that the new releases also appear on the dev databus.

by the way you can combine a custom query with the graphical selection maybe as quick workaround.

[datalogism]

Hello @JJ-Author,
I have to admit that it is a little bit time consuming to recreate the databus collection on the databus dev version.
I wanted to test it but instead of if I found new issues on https://dev.databus.dbpedia.org/dbpedia/mappings/ :

• the 09.2022 release is not available on it, so @holycrab13 didn't push the new release
• that seem to be not possible to select the variant (=lang) of the mappings page
• When i choose "last version" of the generic "fr" data i obtain the version of 2018, even if a 2022.03 version is currently available this is an exemple based on the generic page, but that issues occurs on every collection

I hope that i could help you with that feed-back !