Ticket created after a discussion in the GLAM-Wiki Global Telegram group.

After hearing reconciliation service (re)users, hearing emerging ideas, and seeing the reality of the Wikimedia movement's capacities, I decided to also create this ticket: T362149: Alternative, affordable, lower-barrier approach(es) to reconciliation

(Repost from meta:Talk:Artificial_intelligence/Bellagio_2024)

Works perfectly fine for me in my own PAWS installation by the way.

I referred to this ticket here https://github.com/OpenRefine/CommonsExtension/issues/99

In T337023#9425675, @Jarekt wrote:

I can revisit the Module:License code and work on supporting more cases. If someone wants to help I could use a tester adding cases to Module:License/doc cataloging cases where current code gave adequate result and when it did not

A main issue to make this work in a clear way: the different layers of authorship, dates and copyright in such files.

Update: apparently there is a template {{License from structured data}} started by @Jarekt in 2021 (?) which has the basics for this.

Oops, duplicate of T352865 which I had failed to find here!

This task was not done during the hackathon, but still very valid!

Showing the structured data by default (not in a separate tab) would IMO very much help with its broader adoption.

It would be very helpful to find some examples of files to try to model. Digitized recordings of older but notable songs? Maybe members of Wikidata-WikiProject-Music have suggestions?

Getting started here: https://commons.wikimedia.org/wiki/Commons:Structured_data/Modeling/Works_without_Wikidata_item

Related:

• T326244: Investigate using Search API Facets from ElasticSearch
• T251573: (Tool idea) Build a prototype / proof of concept faceted search for Structured Data on Commons (I also created that ticket a few years ago but I am certainly thinking I want more than prototyping and more than an external tool)

Also mentioned this ticket on the general SDC talk page: https://commons.wikimedia.org/wiki/Commons_talk:Structured_data#Faceted,_SDC-powered_MediaSearch_for_Wikimedia_Commons

I created a high-level task so that community and stakeholders can weigh in on the general topic of faceted search for Commons. T337106: Faceted, structured data-based MediaSearch on Wikimedia Commons

Created overarching task for faceted search. I would really like to see that implemented and it would be great to get a conversation going: T337106: Faceted, structured data-based MediaSearch on Wikimedia Commons

In T335910#8864538, @Susannaanas wrote:

• Most of the media files are about creative works without a Wikidata item.

I have started here - the page can of course be moved and named differently. https://commons.wikimedia.org/wiki/Commons:Structured_data/Minimalist_Wikitext_information_templates

I plan to work on this project at the Wikimedia-Hackathon-2023 and it seems relevant here: T335910: Improve Structured Data on Commons data models (and their documentation) as a basis for Lua Infobox templates

In T244847#8502964, @Pintoch wrote:

Here is the current status of this issue:

The team at TIB (headed by @Loz.ross) is now maintaining the current wrapper and has contributed improvements to deploy it on other Wikibase instances:
https://gitlab.com/nfdi4culture/ta1-data-enrichment/openrefine-wikibase
Thank you to them!

Hi @Spinster ! We can certainly at least investigate if we will be able to get the extension installed! Could you open a dedicated ticket for that? With any details on what you see as making it tricky to get into PAWS?

Yay, it's amazing that you spotted the version update. Thank you for filing this :D

Yay! So many kudos to everyone who helps with the PAWS version of OpenRefine! 😁

Is this task still valid? Does it make sense to do "other OpenRefine cloud Wikimedia things" besides the PAWS installation?

We haven't had action on this topic for a while, so changing status. I think it's still relevant?

Thanks for reporting this! I recently did the steps above using OpenRefine 3.7 beta2, and the problem persists.

In T290088#8519473, @Eugene233 wrote:

@Spinster Please what is the state of this task?

In T325964#8490641, @whanley wrote:

I think this is solved, but I'll let better informed parties decide.

People on wikibase.cloud telegram group told me to add that tag as a local admin and it worked.

Thanks for spotting and reporting this! I have transferred this ticket to GitHub where it will be easier to act upon: https://github.com/OpenRefine/openrefine.org/issues/170

We did this !!!! 🎉

We're almost there! The upcoming OpenRefine 3.7 release will include full Wikimedia Commons upload functionalities.

It's possible, but not straightforward. With a few Wikimedians we're trying to figure it out.

I did a quick test, here's a very simple one I just created! https://commons.wikimedia.org/wiki/User:Spinster/Map_test

This task is nearly finished. The project got an extension until end October 2022, and around that time we hope to release an official OpenRefine version that supports file upload. (It is already possible via snapshot releases, see https://commons.wikimedia.org/wiki/Commons:OpenRefine)

FWIW, I filed this ticket because I was using the public https://board.net/ Etherpad instance, and saw all those features there (test board at https://board.net/p/testboard3). This public instance is run by
https://www.fairkom.eu/en and I assume they also did a good check of all extensions / would not just install risky garbage. So I think it would be nice to do a fresh check of reliability of plugins indeed.

While there's some attention here, I'd like to bump T136744: After Code of Conduct is approved, Etherpad footer should link to it. too - although it's an old ticket, I think it would be really great to do this as well.

This task, even if old, still looks pretty relevant to me / would still make a lot of sense.