Hi, I tested the ISA Tool today (campaign 187), and I keep getting the error described above: Whenever I try saving the page after adding or removing tags, I am getting the "Oops, something went wrong" message.

When I tried it out about 15 minutes ago, it seemed to work and I could navigate through the campaigns, but I got the "Oops, something went wrong" message, when trying to save my tags. So I can confirm that it is not working for me neither.

@Cparle They work on our sample files which I checked. Everything look ok. Thanks a lot.

@CBogen Thank you for this. As far as I can tell, it worked, the JPEG files show up in the ISA Tool with tag suggestions. We are however still working on resolving the issue related to the processing of TIFF files by the ISA Tool (most of the files uploaded by the ETH Library are in TIFF format).

Hi @CBogen, note that we are currently in the process of setting up a project from which many more of such requests are expected to arise.
@NavinoEvans and I are still very much interested in discussing possibilities to automatize this process, e.g. by submitting requested categories through an API that could be called by the ISA Tool.

Here is a first list of bottom-level categories for inclusion in Machine Vision:

@CBogen I met the students last Friday, and we decided that they will work on a different assignment due to two issues: 1) This one. 2) The Commons API apparently not allowing to retrieve JPG files where the orignal file is a TIFF file.

@CBogen May I ask you to add the following category for starters? - https://commons.wikimedia.org/wiki/Category:Photographs_by_Uwe_Gerig

I am about to put a team of students on testing the ISA Tool in connection with machine vision. Our main institutional partner for this has so far been the ETH Library, which has been friendly enough to provide us with high resolution TIFF images. They are also using entity recognition internally, so they would probably be a good partner to run some benchmarking tests. Unfortunately, we won't be able to run tests on their collections on Commons until this bug is fixed.

In T277301#6944532, @Pigsonthewing wrote:

I have concerns about this approach. Structured Data on Commons is meant to be, well, "structured". It is not for "tags".

For example, a photograph of the White House in Washington DC might be tagged "white" and "building", but in terms of structured data it depicts Q35525, which is the item about that single specific building. The item tells us that the subject is a building, and that it is white in colour.

Our main need consists in being able to activate Google Vision on the images in specific categories in order to use them in an enhanced version of the ISA tool that includes tag suggestions from Google Vision (which is currently not the case for older uploads).

I would suggest actively trimming down/emptying that group pro-actively. Especially for those that haven't used it in 2020 (I can definitely be removed for example)

Only 20 have log entries

Same problem here. Using Open Refine to edit Wikidata didn't work today when I tried to do a small ingest of 5 items (2 existing, 3 new).

The Swiss National Library got a request by research platforms providers to support the IIIF standard and raised the issue at the last meeting of the Swiss GLAM-Wiki Contact Group. IIIF support could be an extra argument for institutions with public domain material or freely licensed material to make their content available through Wikimedia Commons. Especially smaller institutions are not expected to support the standard on their own platforms in the near future.

Yes, being able to download the contents of the various monuments list templates that are harvested by erfgoedbot would be very useful in view of the data migration to Wikidata (until all the monuments lists have been switched to pulling their data directly from Wikidata).

In T117349#1893447, @Bawolff wrote:

Hmm, the above patch seems not to be enough to fix https://upload.wikimedia.org/wikipedia/commons/thumb/a/a0/UBBasel_Map_1569_Kartenslg_AA_3-5.tif/lossless-page2-2057px-UBBasel_Map_1569_Kartenslg_AA_3-5.tif.png :(

Error message is usually a varnish 503, so looks like its hitting a timeout and not a memory limit.

We need to get a proper set of guidelines put together to determine which of these requests are okay and which are not before I am happy with dealing with them routinely.

Couldn't whitelisting domains be made a regular routine for someone to do every 24 or 48 hours?
Waiting times of up to 3 weeks for just copy-pasting a domain into a list are hilarious and difficult to communicate to GLAM institutions...
Giving write access to more people to the whitelist might be a solution... ?!

Further examples of this issue can be found here:
https://commons.wikimedia.org/w/index.php?title=Special%3AListFiles&user=Kunstmuseum_Appenzell&ilshowall=1