Here's my similar first-step idea. You are browsing the web, and find a page on any other site about an item that should have a Wikidata item. You click a bookmarklet, which instantly tells you in a side panel which identifier property should be linked, and if it is linked, which Wikidata item the ID is linked from.

The idea was spurred by User:rdmpage in this video (thanks!).

As far as I can see it should be technically possible, but I'm sure you friendly hivemind can improve dramatically on this in-principle sketch:

Bookmarklet runs javascript to open a side panel or overlay div, in which the content is an iframe containing an auto-running WDQS query which takes a single input, the current URL.
The SPARQL query finds out whether that URL matches a formatter URL (P1630) or a third-party formatter URL (P3303), and if so, extracts the ID from the URL.
Then it queries whether that ID is listed for that property, and returns the Wikidata item(s) with that ID for that property. QED.
I've worked on this a bit, and while I'm good enough at SPARQL, and have written a working demonstration query, (this shows the result from 4 different URLs - I'm aware that it doesn't work for *all* URL schemes, but I think it already covers over 90% of them). I don't have sufficient .js skills to get the bookmarklet working at the moment, and I'm sure some of you can do a much better job anyway.

Here's a video demo of my first version.

Hey! This looks super interesting! Is there a link to the extension code anywhere?

Eek, scary. Yes, here you go https://github.com/99of9/Wikidata-Connect . Please be gentle, it's still very rough, and I'm totally new to this game!

Thanks! It's an awesome idea :)

The name was rejected because it's "best to avoid using "Wikidata" (or other project names) as the first word in the app title". Has anyone got any other suggestions?

Random ideas:

• Show me the web
• Explore the web
• WebExplorer
• WebConnector
• Show me more
• Link the web
• SpiderWeb
• Weave the web

Seconding "WebConnector":

• It is sufficiently unique, both in the Chrome Store and Among Firefox Extensions
• It is a compact name that I could see people writing a Medium post about
• It currently has only a few (<300K) Google search results
• It still communicates the idea of the plugin without overlapping with other established brands/concepts (Explorer, Spider)

Other ideas in a similar direction:

• DataFinder
• ConnectionFinder
• DisplayDataConnections
• DataConnections

Thanks for this. I like all your criteria, although I think I want an even tighter limit on #3, and am hoping for a little more pizzaz. For me "web" is a bit bland in that every extension is interacting with the www.

The Facebook group are onto this too. My shortlist is currently:

Entity Explosion
ID.entity
Linkipedia
Web Connector
Linky-Linky
99 Links

In other news, you know testing is going well your code complains about tiny problems with regexes in Wikidata: https://www.wikidata.org/w/index.php?title=Property%3AP6993&type=revision&diff=1240888486&oldid=997662566

In T253201#6341017, @99of9 wrote:

In other news, you know testing is going well your code complains about tiny problems with regexes in Wikidata: https://www.wikidata.org/w/index.php?title=Property%3AP6993&type=revision&diff=1240888486&oldid=997662566

Ah, the differences in PHP vs JS regex evaluation! Your edit is fine as it doesn't change what the regex matches, but do note that the regex [1-9]\d*+(\-[a-z]+)* is valid/compatible PCRE, which seems to be the relevant standard for P1793. I wonder if having a requirement that those regexes must be both valid PCRE and work in ECMAScript would be sensible? 🤔

Available in the Chrome Store: https://chrome.google.com/webstore/detail/entity-explosion/bbcffeclligkmfiocanodamdjclgejcn
On-wiki documentation and discussion: https://www.wikidata.org/wiki/Wikidata:Entity_Explosion
Open-source code: https://github.com/99of9/Entity-Explosion
Introduction video: https://www.youtube.com/watch?v=eRnqoJyi92w
Facebook page: https://www.facebook.com/EntityExplosion

Wohoooooo! I think you can close this ticket then ;-)

Excellent concept, extension and also the video by User:rdmpage mentioned

I did some tests and I feel we need also have a way for a webpage using something like schema.org to say this item is same as

• this subject is same as
• this artist is same as
• this location is same as
• this painting is same as
• .....

and also as said in the video by User:rdmpage using Identifiers like DOI or Handle open up possibilities to e.g. like for scientific publications do citation graphs

Question A @Lydia_Pintscher : any initiative to get webpages say same as ??
I like the way Open Street Map do with tag Wikidata eg. artist:wikidata=* , subject:wikidata=* ,architect:wikidata=*.

Question B @SandraF_WMF Shouldnt we as in the video push for DOI in Structured Data on Commons? I feel GLAM today is "spray and pray" we need to identify objects same as using a Handle/DOI so we can do data roundtrips with Linked data create statistics, compare metadata added...

Example: I added good metadata to M92977337 (JSON)

• aggregator as Europeana item 916124
• aggregator Digitaltmuseum 021018392452
• aggregator Kringla referens=S-XLM/photo/XLMU03395

With a tool like Entity Explosion we could easier start track were the same entity is located if we used DOI as we have seen with Scientific Publications....

I tried to start a dialogue with Europeana lead devs in 2020 about Linked data lifecycle management but it has died see T251225: Change management of entities created and deleted in Europeana but my guess is step 1 is start using PID/DOI/Handle for identifying objects I know Welsh Portrait Collection do that see T243907#5914827

I guess the vision of Linked data and lifecycles of GLAM should be something like DOI:10.5334/dsj-2019-054 "Proper Attribution for Curation and Maintenance of Research Collections: Metadata Recommendations of the RDA/TDWG Working Group"