home.social

#scholia — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #scholia, aggregated by home.social.

fetched live
  1. #Forschungssoftware auffindbar machen: Im Online-Editathon der NFDI4Objects-Cluster „Semantic Modelling & Linked Open Data“ und „Research Software Engineering“ arbeiten wir mit #Wikidata, #SPARQL und #Scholia an besseren Verknüpfungen zwischen #Software, #Publikationen, #Daten, #Personen und #Institutionen.

    Mit Quarto-OER zum Nacharbeiten.

    📅 18.08.2026, 14–16 Uhr
    👥 max. 10 Teilnehmende

    Vorkenntnisse in Wikidata/semantischer Modellierung sehr wünschenswert.

    ℹ️ Infos: nfdi4objects.net/events/n4o_ac

  2. #Forschungssoftware auffindbar machen: Im Online-Editathon der NFDI4Objects-Cluster „Semantic Modelling & Linked Open Data“ und „Research Software Engineering“ arbeiten wir mit #Wikidata, #SPARQL und #Scholia an besseren Verknüpfungen zwischen #Software, #Publikationen, #Daten, #Personen und #Institutionen.

    Mit Quarto-OER zum Nacharbeiten.

    📅 18.08.2026, 14–16 Uhr
    👥 max. 10 Teilnehmende

    Vorkenntnisse in Wikidata/semantischer Modellierung sehr wünschenswert.

    ℹ️ Infos: nfdi4objects.net/events/n4o_ac

  3. #Forschungssoftware auffindbar machen: Im Online-Editathon der NFDI4Objects-Cluster „Semantic Modelling & Linked Open Data“ und „Research Software Engineering“ arbeiten wir mit #Wikidata, #SPARQL und #Scholia an besseren Verknüpfungen zwischen #Software, #Publikationen, #Daten, #Personen und #Institutionen.

    Mit Quarto-OER zum Nacharbeiten.

    📅 18.08.2026, 14–16 Uhr
    👥 max. 10 Teilnehmende

    Vorkenntnisse in Wikidata/semantischer Modellierung sehr wünschenswert.

    ℹ️ Infos: nfdi4objects.net/events/n4o_ac

  4. #Forschungssoftware auffindbar machen: Im Online-Editathon der NFDI4Objects-Cluster „Semantic Modelling & Linked Open Data“ und „Research Software Engineering“ arbeiten wir mit #Wikidata, #SPARQL und #Scholia an besseren Verknüpfungen zwischen #Software, #Publikationen, #Daten, #Personen und #Institutionen.

    Mit Quarto-OER zum Nacharbeiten.

    📅 18.08.2026, 14–16 Uhr
    👥 max. 10 Teilnehmende

    Vorkenntnisse in Wikidata/semantischer Modellierung sehr wünschenswert.

    ℹ️ Infos: nfdi4objects.net/events/n4o_ac

  5. #Forschungssoftware auffindbar machen: Im Online-Editathon der NFDI4Objects-Cluster „Semantic Modelling & Linked Open Data“ und „Research Software Engineering“ arbeiten wir mit #Wikidata, #SPARQL und #Scholia an besseren Verknüpfungen zwischen #Software, #Publikationen, #Daten, #Personen und #Institutionen.

    Mit Quarto-OER zum Nacharbeiten.

    📅 18.08.2026, 14–16 Uhr
    👥 max. 10 Teilnehmende

    Vorkenntnisse in Wikidata/semantischer Modellierung sehr wünschenswert.

    ℹ️ Infos: nfdi4objects.net/events/n4o_ac

  6. yesterday evening work with @EvoMRI on the @wdscholia instance on Toolforge. We noted that our main instance only shows half of the results, only @wikidata 'main' part. The 'scholarly' articles part are no longer there. That day has been pending.

    We seem very close. I wrote up a status 3 weeks ago: chem-bla-ics.linkedchemistry.i

    For this week, plz use qlever.scholia.wiki/

    We put a banner on the #toolforge instance

    #openscience #wikidata #sparql #scholia

  7. yesterday evening work with @EvoMRI on the @wdscholia instance on Toolforge. We noted that our main instance only shows half of the results, only @wikidata 'main' part. The 'scholarly' articles part are no longer there. That day has been pending.

    We seem very close. I wrote up a status 3 weeks ago: chem-bla-ics.linkedchemistry.i

    For this week, plz use qlever.scholia.wiki/

    We put a banner on the #toolforge instance

    #openscience #wikidata #sparql #scholia

  8. yesterday evening work with @EvoMRI on the @wdscholia instance on Toolforge. We noted that our main instance only shows half of the results, only @wikidata 'main' part. The 'scholarly' articles part are no longer there. That day has been pending.

    We seem very close. I wrote up a status 3 weeks ago: chem-bla-ics.linkedchemistry.i

    For this week, plz use qlever.scholia.wiki/

    We put a banner on the #toolforge instance

    #openscience #wikidata #sparql #scholia

  9. yesterday evening work with @EvoMRI on the @wdscholia instance on Toolforge. We noted that our main instance only shows half of the results, only @wikidata 'main' part. The 'scholarly' articles part are no longer there. That day has been pending.

    We seem very close. I wrote up a status 3 weeks ago: chem-bla-ics.linkedchemistry.i

    For this week, plz use qlever.scholia.wiki/

    We put a banner on the #toolforge instance

    #openscience #wikidata #sparql #scholia

  10. yesterday evening work with @EvoMRI on the @wdscholia instance on Toolforge. We noted that our main instance only shows half of the results, only @wikidata 'main' part. The 'scholarly' articles part are no longer there. That day has been pending.

    We seem very close. I wrote up a status 3 weeks ago: chem-bla-ics.linkedchemistry.i

    For this week, plz use qlever.scholia.wiki/

    We put a banner on the #toolforge instance

    #openscience #wikidata #sparql #scholia

  11. There will be changes in the week of January 20th 2026 regarding the WDQS graph split and sunsetting of the legacy service. There is a qlever.scholia.wiki/ mirror running with QLever as backend with the full Wikidata content. This mirror is part of an evaluation of alternatives to Blazegraph.

    #wikidata #scholia #qlever

  12. There will be changes in the week of January 20th 2026 regarding the WDQS graph split and sunsetting of the legacy service. There is a qlever.scholia.wiki/ mirror running with QLever as backend with the full Wikidata content. This mirror is part of an evaluation of alternatives to Blazegraph.

    #wikidata #scholia #qlever

  13. There will be changes in the week of January 20th 2026 regarding the WDQS graph split and sunsetting of the legacy service. There is a qlever.scholia.wiki/ mirror running with QLever as backend with the full Wikidata content. This mirror is part of an evaluation of alternatives to Blazegraph.

    #wikidata #scholia #qlever

  14. There will be changes in the week of January 20th 2026 regarding the WDQS graph split and sunsetting of the legacy service. There is a qlever.scholia.wiki/ mirror running with QLever as backend with the full Wikidata content. This mirror is part of an evaluation of alternatives to Blazegraph.

    #wikidata #scholia #qlever

  15. There will be changes in the week of January 20th 2026 regarding the WDQS graph split and sunsetting of the legacy service. There is a qlever.scholia.wiki/ mirror running with QLever as backend with the full Wikidata content. This mirror is part of an evaluation of alternatives to Blazegraph.

    #wikidata #scholia #qlever

  16. News about Scholia:

    "it looks like we will have a working replacement in time before the WDQS instance with all the Wikidata triples in a single SPARQL endpoint goes down, likely in a week or so"

    "scholia.toolforge.org has seen ridiculous abuse by scrapers"

    "So, plenty of work is left to be done in the next few days. But we are getting close. So, please give qlever.scholia.wiki a go, and let us know your observations. "

    chem-bla-ics.linkedchemistry.i

    #scholia #wikidata #wikibase

  17. News about Scholia:

    "it looks like we will have a working replacement in time before the WDQS instance with all the Wikidata triples in a single SPARQL endpoint goes down, likely in a week or so"

    "scholia.toolforge.org has seen ridiculous abuse by scrapers"

    "So, plenty of work is left to be done in the next few days. But we are getting close. So, please give qlever.scholia.wiki a go, and let us know your observations. "

    chem-bla-ics.linkedchemistry.i

    #scholia #wikidata #wikibase

  18. News about Scholia:

    "it looks like we will have a working replacement in time before the WDQS instance with all the Wikidata triples in a single SPARQL endpoint goes down, likely in a week or so"

    "scholia.toolforge.org has seen ridiculous abuse by scrapers"

    "So, plenty of work is left to be done in the next few days. But we are getting close. So, please give qlever.scholia.wiki a go, and let us know your observations. "

    chem-bla-ics.linkedchemistry.i

    #scholia #wikidata #wikibase

  19. News about Scholia:

    "it looks like we will have a working replacement in time before the WDQS instance with all the Wikidata triples in a single SPARQL endpoint goes down, likely in a week or so"

    "scholia.toolforge.org has seen ridiculous abuse by scrapers"

    "So, plenty of work is left to be done in the next few days. But we are getting close. So, please give qlever.scholia.wiki a go, and let us know your observations. "

    chem-bla-ics.linkedchemistry.i

    #scholia #wikidata #wikibase

  20. new blog: "Rescuing Scholia: will we make it in time?" doi.org/10.59350/yh369-rr787 chem-bla-ics.linkedchemistry.i

    "What started out in 2016 on Twitter became a (small) award winning decade long collaborative project. Unfortunately, the future is not clear. We are at odds if it will survice the growth of Wikidata and in particularly the SPARQL graph split."

    #wikidata #scholia #openscience

  21. new blog: "Rescuing Scholia: will we make it in time?" doi.org/10.59350/yh369-rr787 chem-bla-ics.linkedchemistry.i

    "What started out in 2016 on Twitter became a (small) award winning decade long collaborative project. Unfortunately, the future is not clear. We are at odds if it will survice the growth of Wikidata and in particularly the SPARQL graph split."

    #wikidata #scholia #openscience

  22. new blog: "Rescuing Scholia: will we make it in time?" doi.org/10.59350/yh369-rr787 chem-bla-ics.linkedchemistry.i

    "What started out in 2016 on Twitter became a (small) award winning decade long collaborative project. Unfortunately, the future is not clear. We are at odds if it will survice the growth of Wikidata and in particularly the SPARQL graph split."

    #wikidata #scholia #openscience

  23. new blog: "Rescuing Scholia: will we make it in time?" doi.org/10.59350/yh369-rr787 chem-bla-ics.linkedchemistry.i

    "What started out in 2016 on Twitter became a (small) award winning decade long collaborative project. Unfortunately, the future is not clear. We are at odds if it will survice the growth of Wikidata and in particularly the SPARQL graph split."

    #wikidata #scholia #openscience

  24. new blog: "Rescuing Scholia: will we make it in time?" doi.org/10.59350/yh369-rr787 chem-bla-ics.linkedchemistry.i

    "What started out in 2016 on Twitter became a (small) award winning decade long collaborative project. Unfortunately, the future is not clear. We are at odds if it will survice the growth of Wikidata and in particularly the SPARQL graph split."

    #wikidata #scholia #openscience

  25. "QLever is the fastest engine overall, but is slower for distinct answers. Virtuoso is fast but diverges the most by far mostly due to several known causes. MillenniumDB and Blazegraph are the slowest. MillenniumDB is fast on simple queries, but slow on complex queries." ceur-ws.org/Vol-4108/paper3.pdf

    #wikidata #sparql #scholia

  26. "QLever is the fastest engine overall, but is slower for distinct answers. Virtuoso is fast but diverges the most by far mostly due to several known causes. MillenniumDB and Blazegraph are the slowest. MillenniumDB is fast on simple queries, but slow on complex queries." ceur-ws.org/Vol-4108/paper3.pdf

    #wikidata #sparql #scholia

  27. "QLever is the fastest engine overall, but is slower for distinct answers. Virtuoso is fast but diverges the most by far mostly due to several known causes. MillenniumDB and Blazegraph are the slowest. MillenniumDB is fast on simple queries, but slow on complex queries." ceur-ws.org/Vol-4108/paper3.pdf

    #wikidata #sparql #scholia

  28. "QLever is the fastest engine overall, but is slower for distinct answers. Virtuoso is fast but diverges the most by far mostly due to several known causes. MillenniumDB and Blazegraph are the slowest. MillenniumDB is fast on simple queries, but slow on complex queries." ceur-ws.org/Vol-4108/paper3.pdf

    #wikidata #sparql #scholia

  29. "QLever is the fastest engine overall, but is slower for distinct answers. Virtuoso is fast but diverges the most by far mostly due to several known causes. MillenniumDB and Blazegraph are the slowest. MillenniumDB is fast on simple queries, but slow on complex queries." ceur-ws.org/Vol-4108/paper3.pdf

    #wikidata #sparql #scholia

  30. #ClimateKG will be used for the #IPCC #AR6 corpus of 7 main reports of 10,000 pages. For corpus browsing, republishing, community enrichment. The constructed knowledge graph in Wikibase/MediaWiki allows browsing using the familiar #MediaWiki interface with #Wikidata enhancements like infoboxes, and #scholia like interfaces scholia.toolforge.org/ | Republishing is intended for sharing or reviewing search results on climate topics | Enrichment is for data scientists to make use of reports >>>

  31. #ClimateKG will be used for the #IPCC #AR6 corpus of 7 main reports of 10,000 pages. For corpus browsing, republishing, community enrichment. The constructed knowledge graph in Wikibase/MediaWiki allows browsing using the familiar #MediaWiki interface with #Wikidata enhancements like infoboxes, and #scholia like interfaces scholia.toolforge.org/ | Republishing is intended for sharing or reviewing search results on climate topics | Enrichment is for data scientists to make use of reports >>>

  32. #ClimateKG will be used for the #IPCC #AR6 corpus of 7 main reports of 10,000 pages. For corpus browsing, republishing, community enrichment. The constructed knowledge graph in Wikibase/MediaWiki allows browsing using the familiar #MediaWiki interface with #Wikidata enhancements like infoboxes, and #scholia like interfaces scholia.toolforge.org/ | Republishing is intended for sharing or reviewing search results on climate topics | Enrichment is for data scientists to make use of reports >>>

  33. #ClimateKG will be used for the #IPCC #AR6 corpus of 7 main reports of 10,000 pages. For corpus browsing, republishing, community enrichment. The constructed knowledge graph in Wikibase/MediaWiki allows browsing using the familiar #MediaWiki interface with #Wikidata enhancements like infoboxes, and #scholia like interfaces scholia.toolforge.org/ | Republishing is intended for sharing or reviewing search results on climate topics | Enrichment is for data scientists to make use of reports >>>

  34. #ClimateKG will be used for the #IPCC #AR6 corpus of 7 main reports of 10,000 pages. For corpus browsing, republishing, community enrichment. The constructed knowledge graph in Wikibase/MediaWiki allows browsing using the familiar #MediaWiki interface with #Wikidata enhancements like infoboxes, and #scholia like interfaces scholia.toolforge.org/ | Republishing is intended for sharing or reviewing search results on climate topics | Enrichment is for data scientists to make use of reports >>>

  35. it takes quite a bit of effort to update all the SPARQL queries (we have more than 300) to accommodate for the RDF graph split of @wikidata

    Want to help? Check out wikidata.org/wiki/Wikidata:Sch

    #wikidata #scholia

  36. it takes quite a bit of effort to update all the SPARQL queries (we have more than 300) to accommodate for the RDF graph split of @wikidata

    Want to help? Check out wikidata.org/wiki/Wikidata:Sch

    #wikidata #scholia

  37. it takes quite a bit of effort to update all the SPARQL queries (we have more than 300) to accommodate for the RDF graph split of @wikidata

    Want to help? Check out wikidata.org/wiki/Wikidata:Sch

    #wikidata #scholia

  38. it takes quite a bit of effort to update all the SPARQL queries (we have more than 300) to accommodate for the RDF graph split of @wikidata

    Want to help? Check out wikidata.org/wiki/Wikidata:Sch

    #wikidata #scholia

  39. Bei der etwas anstrengenden #Orcid Maske ist man ja versucht, seine Literatur einfach nur in #WikiData zu erfassen und im Orcid auf einen #Scholia Link zu verweisen. Nur hat man dort wiederum meist das Problem, dass die übergeordneten Werke zuerst modelliert werden müssen....

  40. Bei der etwas anstrengenden #Orcid Maske ist man ja versucht, seine Literatur einfach nur in #WikiData zu erfassen und im Orcid auf einen #Scholia Link zu verweisen. Nur hat man dort wiederum meist das Problem, dass die übergeordneten Werke zuerst modelliert werden müssen....

  41. @stuartyeates @wdscholia
    this doi-lookup in #Wikidata uses citation.js
    if i understand the source code correctly citation.js uses the MediaWiki-API and not any SPARQL-endpoint. So you can trust, if the doi is added, it would be found by #Scholia.

  42. @stuartyeates @wdscholia
    this doi-lookup in #Wikidata uses citation.js
    if i understand the source code correctly citation.js uses the MediaWiki-API and not any SPARQL-endpoint. So you can trust, if the doi is added, it would be found by #Scholia.

  43. @stuartyeates @wdscholia
    this doi-lookup in #Wikidata uses citation.js
    if i understand the source code correctly citation.js uses the MediaWiki-API and not any SPARQL-endpoint. So you can trust, if the doi is added, it would be found by #Scholia.

  44. @stuartyeates @wdscholia
    this doi-lookup in #Wikidata uses citation.js
    if i understand the source code correctly citation.js uses the MediaWiki-API and not any SPARQL-endpoint. So you can trust, if the doi is added, it would be found by #Scholia.