Note that for some users(like myself) an instruction on how to set up Curious Facts locally might be sufficient.

ResourceSync is indeed a protocol for informing other databases about one's contents or changes(similar scope as OAI-PMH) and as far as I know, it hasn't had many implementations.

Details are now available at https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021/Data_Challenge

That was a very fun challenge to participate in and the format or just a part of it could as @Fuzheado say be an opportunity for engagement. I'm happy to volunteer(together with others) to make this happen.

From my perspective, there could be more than one alt-text per image and language in the SDC data. It would then be up to consumers to select which alt-text they would like to use.

@ChristianFerrer could you exemplify what functionality other tooling is missing for your particular use-case? Sometimes it's a matter of lacking documentation, for example, Pattypan can upload files from URLs but few people know about that capability.

There is now a property proposal: https://www.wikidata.org/wiki/Wikidata:Property_proposal/alt_text#alt_text

The template documentation has now been updated.
https://commons.wikimedia.org/w/index.php?title=Template:Fornminne/doc&oldid=460069658

Thanks @Lokal_Profil!

Looks good to me!

Nowadays other license options are hidden in UploadWizard unless one clicks the small link at the bottom of the form, so is this still a concern?

Actually following this someone will need to update the Campaign. So the UUID is presented as an alternative input.

Aren't the referenced patch blocking access to all services on maps.wikimedia.org and not only osm-intl? This issue and the deprecation message sent to maps-l only addresses maps.wikimedia.org/osm-intl/.

@Eric_Luth_WMSE yes per my comment in T260971. I do however not have the rights on commons to make or test the fix. Also I think some documentation might still need an update if implemented.

Yes it's broken. There is at least a "this is how a solution could look like" suggestion from me over at https://commons.wikimedia.org/wiki/Template_talk:Fornminne.

Workflow between Wikimaps Warper and the Map template. The Map template has a value for the warp status of the image in Wikimaps Warper. Warper writes to the Map template the changed value when it alters the map image.

Confirming it works and resolves my particular issue. Thank you @zhuyifei1999!

@Xqt when pwb is installed with "pip install pywikibot" I get a more recent version. Is the PAWS pwb actually up to date? To me it looks like the docker file were initiated with the stable branch but might have gotten out of date.

Closing as it's deployed and confirmed.

Worth noting is that this would make the template usages that pull data from Wikidata incompatible with many of the map tools including Wikimaps Warper.

@brion worked on glTF support a while ago. Looks to me like it got quite far, maybe possible to rebase it and take a stab at it.

In T246901#5965504, @Mrjohncummings wrote:

In T246901#5965272, @Ainali wrote:

In T246901#5965141, @Abbe98 wrote:

Could a solution similar to the one for MP3 files make sense? It would allow GLAMs to share vetted 3D content while still lock abusers out.

(To upload a MP3 file to Commons you need a specific user right.)

I think definitely this should be brought up as a possible solution for 3. in a community discussion. It essentially removes the burden from the sysops by only assigning the rights to users in good standing.

I also recall another more technical but yet similar reason, and that is that some 3D-formats allows for scripts also (which could possibly have malicious purposes). But I guess that is easier in a way by just saying that we will not support them at all (yet).

Does anyone know how or where the MP3 discussions happened?

Could a solution similar to the one for MP3 files make sense? It would allow GLAMs to share vetted 3D content while still lock abusers out.

There have been previous discussions on the subject of sanitation of 3D formats over at T131723.

The repository has moved so the patch is no longer relevant and I'm not sure if it's the Gerrit or Github mono repository that's the master nowadays.

I have created an initial patch for this. GPS locator can now be enabled on a wiki with $wgKartographerGPSLocator = true; Following that the <mapframe> tag now takes an additional argument "gps" that adds the gps button/control to the map.

FYI: I'm about to import about 15000 "new" monuments to Wikidata but won't touch the lists.

Turns out this is also a problem within WDQS. When it comes to IDs and URIs is there a reason for encoding this type of information in the first place instead of leaving that to applications?

@AxelPettersson_WMSE thanks for the poke! Nothing for the Swedish article but for the Danish one this month on my side.

That's one of the use cases for Wikidata. As I say Tora does not match our use cases at all.

@Salgo60 merged items in Wikidata gets sameAs statements and are redirected. Tora does not contain all of the parishes in K-samsök and would not be suitable for our Europeana use case.

1. No one else has asked for additional documentation. Regarding these URIs we have only had minor support questions.
2. No that is not good practice in this case, but the modeling will be updated with owl:sameAs statements(see below).
3. Yes we will add Wikidata identifiers to support de-referencing by Europeana, if nothing unexpected comes up this will happen during November or early December.
4. No that's an issue with Wikidata, the link is correct but Wikidata incorrectly encodes it.

@Salgo60 I will now close this issue again.

@Urbanecm Thanks!

@AxelPettersson_WMSE if there is any public documentation of the Wikidata workshop co-hosted with us and Europeana it would be nice to have a link in there.

@Abbe98 The fact that you can neither see nor search using the old ids means that the WLM workflow is broken for anyone using new Fornsök. Do you know what the plans are around this, alternatively could you put us in touch with someone who might?

We are very close to redirect the links(ETA late September), the in October all new Fornminne data will be available in K-samsök/Wikidata.

By default it's not possible to navigate to non text-input elements in Safari. Such a behavior can be enabled under Preferences->Advanced.

@Ciencia_Al_Poder yes, I'm thinking I could just change the default value of MediaWiki:Accesskey-ca-nstab-project...

Switching the default access key is trivial, but the old one wouldn't work. Is this okay?

Closing this as the hackathon is over and all relevant links seems to be present here.

So was thinking about moving the georeference data from Wikimaps Warper to Commons or Wikidata a few years back the main options were:

@Salgo60 Phabricator is not a place for your personal opinion nor a place for your feedback to a government agency. You know from the ongoing discussion on this subject that there is no consensus on this subject in your favor. Please do not try to run people over by moving the discussion here.

Dropping this resource here:
https://www.wikidata.org/wiki/Wikidata:WikiProject_Maps/Historical_map_properties

This seems to be fixed.

As we now have a data field "Visible above ground" I would like to remove all items where this value is set to false, feels like a start and is doable already this year.

@Abbe98 please do it I feel SMVK looks having a lot of data plus also some good structures in SMVK

"SMVK-EM" is SMVK Etnografiska, "name" referrers to their person authorities and "1070548" is an ID.

@Salgo60 I have a bot for this, (Carlottas data can be accessed from SOCH and references SOCH URIs).

@Salgo60 there is a SOCH REST instance on tool labs for use on Wikimedia projects if you would like to implement something like this.

I'm fully aware of what ShEx is and how it's used.

What has this to do with ShEx?

What do you mean by this? The RAÄ parish data(SOCH(SOCH does however use ShEx for other data)) has no need for ShEx for because the data is static and can only be edited after review by "experts" I think the same is true for Riksarkivets parish data.

Does the frontend need to URL encode external IDs? If they are meant to be resolvable there should be no need to do so in the first place right?

@AxelPettersson_WMSE, @Susannaanas is onto that!

@Salgo60 it does contain that information there is even an API endpoint: http://www.kulturarvsdata.se/ksamsok/api?method=getServiceOrganization&value=all&x-api=test

What are you trying to show with your last comment? It works as expected. The accept header is ignored in the first case because you have said you want HTML in the URL and in your second example you get 404 because the URI does not exist...

What is this issue about @Salgo60? "objectid" does not exist in the new Fornsök and the old links will be redirected when the old instance is retired. RAA Nummer is just a part of the session URL similar to "tab" because RAA Nummer is not unique.

Kulturarvsdata kommer automatiskt att peka rätt när den gamla tjänsten är ner släckt. BBR exemplet beror på att objektet i fråga inte har skördats till Kulturarvsdata.