Adding additional statements to Wikidata property

Hi,
I’m trying to add additional statements to Wikidata properties when the item already exists in Wikidata.
For example… What’s the value of a house: wait, struggle, and improvement in a militia-controlled(?) area in Rio de Janeiro - Wikidata I added the article using https://bhl2wiki.herokuapp.com/ (because it will add cites works statements for the article).
It doesn’t include all the statements I want in the resulting Qid for the article, so I used a spreadsheet of the DOIs in OpenRefine and created a schema that would add the additional statements I wanted. Some things have worked - eg adding statements that didn’t previously exist, such as main subject or copyright licence.
But where the property already existed, eg instance of or published in, and I wanted to add a second value, that hasn’t worked. Initially I tried using configure–add, and when that didn’t work I tried configure–add or merge, but that added a 2nd reference without actually adding the value.
Can anyone see what I’m doing wrong?
I also wanted to change the label to sentence case (which I’ve done successfully), and split title into title (also transform to sentence case) and subtitle. I’ve successfully added the subtitle, but can’t see how to overwrite the title - again, I’ve tried both the add and add or merge options, and also tried just matching on property.
Any advice would be appreciated!
Thanks
Helen

But where the property already existed, eg instance of or published in, and I wanted to add a second value, that hasn’t worked. Initially I tried using configure–add, and when that didn’t work I tried configure–add or merge, but that added a 2nd reference without actually adding the value.
Can anyone see what I’m doing wrong?

Beyond the “Add” or “Add or merge” setting, it is important that you configure the matching strategy as well. The stricter this strategy is (meaning, the more bits of information it considers when comparing two statements), the more likely OpenRefine will be to create an additional statement even though there is one already. For instance, the “Qualifiers” strategy with either the “Add” or “Add or merge” editing mode should always create a new statement unless you are adding one with the exact same value and qualifiers as an existing one:

When you change those settings, it might be worth making sure the changes you made are properly saved, by hitting the “Save schema” button in the top right corner of the schema editor (if it is greyed out, it means that it is already saved).

If that still does not work, you could export your schema (in the Wikidata/Wikibase menu in the top right corner) and share it with us so that we can see what exact settings you are using.

Thanks for taking a look at this Antonin. That’s really helpful info… I hadn’t previously grasped that that by using the strategy with qualifiers included I should always get a new statement. However, in practice I still seem to be having the same issue I described above and despite following your guidance the changes have not appeared on Wikidata. The plot thickens as I also notice this afternoon that the revisions I’ve applied aren’t showing in the Wikidata view history tab - that’s showing JIED vol 4ꓹ issue 3 revision 1 as the latest edit, but in an attempt to get it to work I’ve just uploaded revision 2, 3 and 4 - none of which are showing in the history. I’ve exported my schema to share, but get a message here to say new users cannot upload files… perhaps there is an alternative method I could use to share it with you?
Thanks again
Best wishes
Helen

JIED - edits revision schema.tar.gz (4.0 KB)
Had an email that suggested I might now be able to upload…

Thanks for following up! Looking at your schema, I cannot see any obvious problem: only the last statement (publication date) uses the “Property and value” merging strategy, but that is probably fine.
It’s hard to say what is going on here without looking at the data you are trying to upload too and the state of the corresponding items. It could be that edits are not made at all because of some other issue. You could find that out by looking at the server logs of OpenRefine (after a session with an attempted upload), which could contain errors that might put you on the right track.
The documentation to see those logs is here:

Thanks Antonin,
Can I check I’ve understood the ‘property and value’ merging strategy, as I thought I had applied that to each statement… but you mention you can only see it on publication date, so I’m wondering if I’m not looking at quite the right thing. This is what I see on publication date


but I see the same on each of my other statements too - the only thing missing is the tick in ‘lax value matching’ - would that make a difference? I’ve tried ticking that on the other statements and uploading again. It looks as if it’s working as usual, but yet again no edits are showing in the item histories on Wikidata. This is what I see in my OpenRefine log
09:28:37.147 [ refine] POST /command/wikidata/perform-wikibase-edits (19ms)
09:28:37.165 […mWikibaseEditsOperation] Performing edits (18ms)
09:28:37.165 […ting.EditBatchProcessor] Requesting documents (0ms)
09:28:41.093 […baseapi.WbEditingAction] We are editing too fast. Pausing for 5969 milliseconds. (3928ms)
09:28:47.436 […baseapi.WbEditingAction] We are editing too fast. Pausing for 34 milliseconds. (6343ms)
09:28:48.080 […baseapi.WbEditingAction] We are editing too fast. Pausing for 57 milliseconds. (644ms)
09:28:48.708 [ refine] GET /command/core/get-history (628ms)
09:28:48.740 [ refine] GET /command/core/get-project-metadata (32ms)
09:28:48.749 [ refine] GET /command/core/get-models (9ms)
09:28:48.765 [ refine] POST /command/core/get-all-preferences (16ms)
09:28:48.780 [ refine] POST /command/core/get-rows (15ms)
09:28:48.829 [ refine] POST /command/core/compute-facets (49ms)
09:28:48.854 [ refine] GET /command/core/get-preference (25ms)
Does that give any clues about what might be going wrong?
Thanks
Helen