Hi Jean-Fred, Integraality is an awesome tool and I'm enjoying using it. I also can't see a need for property_threshold, so I set it to 1, meaning I want numbers to be shown if there is at least one item with that property- that's what a threshold of 1 would mean to me. Instead, it shows cells with at least 2 and the cells with 1 show as 0.0%. This is easy to fix for my case by setting the value to 0, but I just wanted to highlight that, when it is used, the current behaviour is off by one from what I think is the natural expectation.

In T223773#5195422, @Smalyshev wrote:

As for the second one, it's unfortunately a limitation of the current API - only one result per page (<page> tag in generator) can be returned. In general, only one result per XPath match - i.e. if XPath matches more than one thing per page it won't work.

Further finding: with no mwapi:ellimit property it returns 10 results. With mwapi:ellimit "max" it returns one result. With a numerical mwapi:ellimit property it returns varying (small) numbers of results. With a nonsense mwapi:ellimit property (e.g. "xam" "qwerty") it returns a set of 92 results which seems complete. So I only get the desired result when entering a nonsense input.

The second query doesn't return all the external links that are present in the article (and visible in the REST query). It may be returning a different number of results at different times- the bug is that it's less than the full number. Adding an mwapi:ellimit property seems to produce fewer results.

Thanks for pointing that out: ranks are now set correctly in the item and an end date has been added for the old value.

Thanks for testing in Opera. The bug is definitely happening on Chrome for Windows.

I don't get the confusion. John has explained why he is asking these questions: an important feature of Wikidata, used in an ongoing project, is not working properly and he's just trying to find out what steps are necessary to get it fixed. You've been asked because you've been recommended as someone with relevant knowledge. He's just looking to take the next step to get the problem fixed, whatever that step is. Discussing his employer doesn't identify that step.

Glad this has a High priority: I'm running a training session for the query service for Oxford University staff tomorrow morning. It'll be a lot more stressful if these features aren't working. Lesson learned that I should in future immediately raise the issue here on Phab.

Iimage upload done. Thanks for your help.

The director of the museum has emailed an authorisation. The OTRS ticket number is #2018081610006925
Cheers,

@Framawiki : I'm the Wikimedian In Residence at the University of Oxford, working across the university's libraries and museums. In that capacity, I've met with the Director of the museum, and she has given me the go ahead to share those images on Commons, which I would do as part of that job. Making the change on the museum's web site would require tagging the images individually: I wouldn't expect that to happen soon, especially in the summer when staff are likely on holiday. So I want to get the image upload done soon without waiting for a notice to appear on the site. Hope this clarifies,

I'm doing my job today as a Wikimedian In Residence. I don't often have access to the server which generates the XML, and I've come today to the office from where I have access specially to do some uploads, although I'll have access tomorrow, so for me this is an urgent problem.

Note that it's not the XML itself that triggers the behaviour. In the GWToolset form, after I've chosen the file, one of the form entries asks for categories that will be applied to all the uploaded files. When I enter the category "Files uploaded by the Bodleian Libraries' Wikimedian In Residence" (without quotes) the next step is the example three metadata records, and it's at this stage that I get the error.

Learned from further testing: the category itself survives the transfer to Commons Beta intact. This error only shows up in the metadata *preview* (when GWToolset parses the first three records and shows the results). Hence this is a more minor error than my first message suggested.

Just noticed the extra requirements in the instructions: As well as an employee of The Bodleian Libraries, University of Oxford, I am already an experienced contributor to Commons, with about 900 uploads. The first batch upload will be from this collection: http://digital.bodleian.ox.ac.uk/inquire/Discover/Search/#/?p=c+,t+,rsrs+0,rsps+10,fa+ox%3Acollection%5EEphemera,so+ox%3Asort%5Easc,scids+,pid+,vi+ for which I've already converted JSON metadata into flat XML. (JSON metadata files are obtained by selecting an image then clicking the IIIF icon on the right)

I'm pleased to see updates on this: I'm presently Wikipedian In Residence at the Bodleian Libraries in Oxford, UK and in contact with other organisations that have lots of text. I'm trying to persuade cultural organisations to take Wikisource seriously and to make it part of their workflow for sharing free text. This is an awesome opportunity for Wikisource, but of course these organisations want the same kind of reporting tools for shared text that they rely on for monitoring hits on their images.