It'd be great if there were an "undo" button after you evaluate a given edit, in case you misclick.

Please for reporting errors/bugs/improvements on the Annotation Tool, use this task T344016. For discussing the model, please keep providing here.

In T341820#9084988, @Huntster wrote:

At the upper right corner there is a wiki selection drop-down. If I try to select a specific language to work in, it returns "nothing more to load". I can only work on items with "All" selected.

Thank you for these docs! They'll be very useful for my Ruby gem :)

Ah, yeah the musical notation and math types were missed by me, along with some others. I'm not sure if those currently use hyphens or not.

@WMDE-leszek yup, we can probably close this ticket in favor of that one, since this isn't really an issue with the REST API. Thank you!

I'd appreciate that! It makes it quite difficult to test my Ruby library, since I haven't built out the authentication part of things yet. I can test all the other types, but Time and GlobeCoordinate aren't testable for me right now (quantity I've just worked around by using "1" as the unit).

I think this ticket can be closed as completed?

I can confirm the abuse filter issues still exist :)

Thank you!

Thank you!

Based on how the SnakValidatorStatementValidator class seems to work, it seems like you could catch the specific exceptions raised by lib/packages/wikibase/data-model-serialization/src/Deserializers/StatementDeserializer.php and return a more specific error message for "invalid statement" in the validate method Relatively Easily™ (I'm decent at PHP, but hardly an expert, so I may very well be missing something). That might be something to look into, because the current generic invalid statement message is pretty frustrating.

It seems like there are various places in the REST API code where there are permission checks that provide specific error messages about what the problem is, but the newFrameworkAlikePermissionDeniedResponse method in repo/rest-api/src/RouteHandlers/ResponseFactory.php doesn't actually accept any arguments, so it just throws away the specific error message. Though in this case I guess the more specific error wouldn't be particularly useful anyway.

I get a 403 ({\"error\":\"rest-write-denied\",\"httpCode\":403,\"httpReason\":\"Forbidden\"}) when using a Wikidata beta site entity for the quantity unit:

I tried using the HTTP URL, but I still get a 500 error ({\"code\":\"unexpected-error\",\"message\":\"Unexpected error\"}).

Oh, that's really weird. So it has to use HTTP, not HTTPS for globe/calendarmodel? Can we just exclude the protocol entirely like //www.wikidata.org/entity/Q2?

Marking this as resolved since the hackathon is over

I managed to figure out how to generate the Swagger docs locally, and changing repo/rest-api/specs/global/request-parts.json in the Wikibase repo fixes this problem:

Released a new version (0.2.1) of the gem with add_statement, delete_statement, and an overall significantly better implementation for how datavalues are handled.

Improved the way datavalues are represented in the codebase to have dedicated classes for each type. Also started adding unit tests across the library :)

I'd like to say that - as a Wikidata contributor - this is still a much-needed tool. The current reference interface for Wikidata is still painful to use.

Apologies if this is the wrong place to mention this, but I've been using the suggestions feature for a while and my only complaint about it currently is that, when you create a new statement, qualifiers for it don't have any suggestions (e.g. when adding Steam Application ID to an item, I would expect that adding a qualifier would suggest the "platform" property as a qualifier). The suggestions only work when the statement has already been saved.

I would love this feature, I frequently add new properties that require a sibling statement (e.g. Steam Application ID requires that you add Steam as a Distribution method for the item) and this would make my life a lot easier :)

FYI, I keep getting disconnected from the site for some reason.

@greg I definitely wouldn't suggest that anyway, if I were running an open source project I wouldn't want to risk having that taken away. We do have LDAP support in CE, the difference with EE is that there are some advanced features.

@demon I was a Wikimedia contributor when everything was switched over to Phabricator, and having seen that I can't imagine this is a decision that'd be taken lightly, but as a GitLab employee I wanted to ask what features you felt were missing from CE?

Any updates on this? We'd like to use this on the PCGamingWiki if possible.