Problem

When this extension is installed, it breaks the Extension popup-menu.

Broken popup-menu/button:

Working:

Regards, Antoine

Some RDF triple stores offer a Linked Data Fragments endpoint. This is a query interface which is much simpler than SPARQL and is therefore often faster and more reliable (since it is cheaper for the service). Importantly, it supports paging, which lets a client download large sets of results without running into timeouts.

Proposed solution

It would be nice if OpenRefine supported importing from a LDF endpoint, similarly to how SQL databases are supported.

Alternatives considered

This is similar to the request for a SPARQL importer, OpenRefine/OpenRefine#1212 (because a lot of services offer both endpoints).

This is a feature request for a specific subcase of OpenRefine/OpenRefine#1212. This will be helpful for users who want to edit structured data of existing Wikimedia Commons files with the help of OpenRefine.

Through the SDC project for OpenRefine, users will be able to edit and upload files with structured data on Wikimedia Commons. See more info about this project on meta.wikimedia.org.

In some cases, it may be very handy for users to start an OpenRefine project with a SPARQL query from the Wikimedia Commons Query Service (WCQS). However, this specific SPARQL endpoint requires Wikimedia OAuth authentication.

It would be great if the work done on OpenRefine/OpenRefine#1212 also includes this use case, or alternatively we add support for WCQS after that general task has been completed.

Proposed solution

I have no idea at all about the technical difficulties re: this request. Curious to hear considerations around this!

Additional context

• General info about WCQS, including some pointers re: dealing with authentication from external tools https://commons.wikimedia.org/wiki/Commons:SPARQL_query_service
• The authentication for WCQS is controversial in the Wikimedia community, see https://phabricator.wikimedia.org/T297995. However, it is very unlikely that authentication is removed anytime soon (think in the upcoming years)

Description

• Autocompletion (Cntl-Return) for entities and properties like in the WDQS
• Add color syntaxing like in the WDQS

Example

Now:

Desired:

Description

In OpenRefine, we use Weblate to translate the numerous strings of text. The extension database and wikidata have the own Weblate's componants.
https://hosted.weblate.org/projects/openrefine/

Could this extension, and the CommonsExtension extention, have their own componant?

This extension should work with OpenRefine v3.5.x, nothing more to describe… ;-)

Description

The step where you choose the JSON import level can be skipped, it's always the same.
The column name should come from the JSON fields name of the first record.

So the project name and tags could/should be asked the step before.

Screenshot

Prepare documentation that will help guide users, stakeholders, and OSS community developers around importation of data from a SPARQL query.

• Show an example of query from the Wikidata end-point.
• Put that documentation in a subpage of https://www.wikidata.org/wiki/Wikidata:Tools/OpenRefine
• Explain the pre-reconciliation

The HTTP request to the Query Service could be sent from the back-end, and not the Front-End (JavaScript). In most scenario, it may be better.

The current text field for end-points show no suggestions.

It would be good to have a list of suggestion of end-points.
The suggestions could come from a file on our GitHub repository, or gathered from the services’ manifest.

Description

The extension currently does not have any tests. Skipping tests gives a false impression that the project is progressing well.

Description

If a column contains entities, they should be reconciled instead of showing the URL.

Example

item_original column is the URL, but the second column, item, is what should be expected.

Description of the problem

End-point: http://kg.artsdata.ca/sparql/

# Upcoming events in Artsdata.ca

PREFIX schema: <http://schema.org/>
SELECT DISTINCT  ?start ?status ?mode (sample(?label) as ?name)  (sample(?url) as ?webpage)
WHERE {
  ?e a schema:Event ;
     schema:startDate ?start ;
     schema:name ?label ;
     schema:url ?url ;
     schema:eventStatus ?status ;
     schema:eventAttendanceMode ?mode .
  FILTER(?start > '2022-08-10T01:47:07.569Z'^^xsd:dateTime)
} 
GROUP BY ?start ?status ?mode
LIMIT 1000

This will trigger an error: « Unable to parse preview ».