Getting the property answers from the API and check for
http://www.wikidata.org/entity/Q309996
http://www.wikidata.org/entity/Q1194689

Are the above entities are it's properties or not?

Check this example.

https://www.wikidata.org/wiki/Q15716313#

The text is "american" but the object entity should be "United States of America":

the backend API should call the endpoint and retrieve the label of the entity. In this case:

http://www.wikidata.org/entity/Q30

the query is:

select ?label ?disambiguation where {
OPTIONAL {http://www.wikidata.org/entity/Q30 http://www.w3.org/2000/01/rdf-schema#label ?label .
FILTER (lang(?label)="en")}

OPTIONAL { http://www.wikidata.org/entity/Q30 http://schema.org/description ?disambiguation . FILTER (lang(?disambiguation)="en") . }
}

I suggest also that the object entity should be "United States of America (sovereign state in North America)" so that it is more clear for ambiguous entities

Example: https://www.wikidata.org/wiki/Q1248738

However, this fact already exists:

DoD

• additional checks are implemented, s.t., to prevent pre-existing facts as being shown in the example are prevented.

It suggests a https://www.wikidata.org/wiki/Property:P407 statement when the item already has https://wikidata.org/wiki/Property:P364
Ex:
https://wikidata.org/wiki/Q1249131

https://github.com/WikidataComplete/Wikidata-Complete-Gadget/blob/main/WikidataComplete-Gadget.js#L280
these API URLs should be replaced with new backend service

as per talk page message by user we need to fix UI for mobile devices

I suggest to change the boarder solor to #0645ad when we click it looks like this

while when approving the statement we really need to reload the page, when rejecting we should not, we should just remove it from the list ....

To change the entities to their name and showing the data to user in systematic way.

I do not like this ...

I propose to put everything in the grey box, more or less like this:

but with nicer css ...

The boarder of the box with the statements to approve is slightly off.

To debug maybe it helps to unset the boarder, then the box is not looking as expected. I guess the problem starts from there.

https://github.com/WikidataComplete/Wikidata-Complete-Gadget/blob/main/WikidataComplete-Gadget.js#L246
change this with backend date

DoD

• Duplicate suggestions are prevented

Example

At https://www.wikidata.org/wiki/Q10085467 just one suggestion should be shown.

# one example to reject the fact (id: 3410)
curl -X POST \
  'https://qanswer-svc3.univ-st-etienne.fr/fact/correct?userCookie=c51f3c6f-ef1c-41ff-b1ca-7a994666b93e&factId=3410&correction=2' 

The API is used to reject an item.
URL: https://qanswer-svc3.univ-st-etienne.fr/fact/correct
POST HTTP REQUEST
3 query params:
userCookie: c51f3c6f-ef1c-41ff-b1ca-7a994666b93e (String type) [Fixed]
factId: The 'id' field you will get from the API of #8 (Integer type)
correction: 2 (Integer type)

Definition of Done

• a Wiki page was created providing a step-by-step (easy-to-follow) description of the installation process
  • each step as described
  • for important steps, a screenshot is provided too
• update the repository with an up-to-date script required for the installation

When user clicks on the approve or reject button an animation should appear.

DoD (definition of done):

• Make animations available from technical side (any animation can be used in this step)
• Agree on the exact approve/reject animations that will be used

The last fact on the list doesn't show any results on the list .
for eg: https://www.wikidata.org/wiki/Q103665

The last value doesn't accepts the fact. It redirects to top of the page.

On UI add a button (links to https://github.com/WikidataComplete/Wikidata-Complete-Gadget/issues/new) to create new issues in the repo. So that users can raise new issues.

For a given page, it is showing only 1 approvable fact even if it has more than 1 fact to approve.
eg: https://www.wikidata.org/wiki/Q11567530

copy here some notes of guo

For the new statement, use jquery find the statement list and !temporarily add the approved statement.
same for delete the statement in the proposed list and decrease the number by one.

ASK if you need more help! it's not a problem!

please double check, but I approved two statements and they are not inserted

the claim is not getting created because of empty numeric-id in payload

uri: https://www.wikidata.org/w/api.php

Payload:

action: wbcreateclaim
format: json
entity: Q16161947
property: P136
snaktype: value
value: {"entity-type":"item","numeric-id":""}
summary: Edited with Wikidatacomplete
token: sampletoken+\

Response:

{
    "error": {
        "code": "invalid-snak",
        "info": "Invalid snak data.",
        "messages": [
            {
                "name": "wikibase-api-invalid-snak",
                "parameters": [],
                "html": {
                    "*": "Invalid snak data."
                }
            }
        ],
        "*": "See https://www.wikidata.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
    },
    "servedby": "mw1421"
}

Definition of Done

• a visualization of the Wikidata complete suggestions was established that looks very similar (or equal) to the property visualization of Wikidata (see the following screenshot)
  • the CSS classes of the Wikidata visualization was used
  • the suggestion box should have a border to indicate to users that this is not a statement but a suggestion to create a new statement
  • the buttons "approve" and "reject" are shown below the box reusing the border color (s.t., people can easily recognize that the buttons serve the purpose of interacting with the suggestion box)

Example: https://www.wikidata.org/wiki/Q1248738 (see below)

There the proposed fact is correct. However, the evidence is wrong. The correct evidence would be:
"Gitanas is a Mexican telenovela which aired in 2004."
However, the text of the evidence is not changeable. A better option would be to allow users to change the values.

See the following screenshot regarding the described problem:

DoD

• As user, I would like to edit all suggested values
  • proposed solution: there should be an edit symbol besides the values. If clicked, the value is put into an input attribute and the value can be changed by the user.
    • see the following screenshot regarding the described solution:

one can use the existing API of wikidata complete for this ...

this should not happen.

1. Since you currently refresh the page it means that it is given back again by the API. So probably you call the API only when the statement is rejected and not when it is accepted ..... please check this!

2. When not refreshing the page (next step where guo is helping) then you can reduce the counter and you remove the statement, but still you need to call the API otherwise then when you reload the page we will have the same problem.

If only one statement write:

There is 1 statement to approve.

when clicking on the reference we would like to have this:

https://en.wikipedia.org/wiki/Gakuen_Alice#:~:text=Hotaru%20Imai

(try it out in google chome!) The text containing the answer is marked. We would like to have this, i.e. the user clicks on the reference and gets there. To do this you can use a code that is similar to this. This generated the URL:

<a target="_blank" rel="noreferrer" href={${url}#:~:text=${encodeURIComponent(evidence.slice(0, offset_start))}-,${answer.answer}}>

Check this screenshot "United Kingdom" in the evidence, it also shows the HTML:

Hello, @Dhairya3124 I hope you're doing great, I just want to let you guys know that, this gadget is a very wonderful tool, at least I've used it several times on Wikidata, and it's amazing using it.
Thanks to all the dev team members.

Can this gadget be used on a non-WMF wiki? it's Gratisdata and it's also a wiki like Wikidata, which uses the same software (MediaWiki, Wikibase) as Wikidata.

I am very much interested in hearing from you, thank you for your anticipated cooperation in this matter.

from: You have these number of statements to approve: 1
to: "There are N statements to approve".

If there is none then put the text and the link to:

"Go to entity with statements to approve"

Well structured code = well structured mind.

Please, refactor the code with respect to the following suggestions:

• Make consistent indentations in the files (https://google.github.io/styleguide/jsguide.html#formatting-block-indentation)
• Use standard naming convention (https://google.github.io/styleguide/jsguide.html#naming)

Also, please check the entire document for your information: https://google.github.io/styleguide/jsguide.html

There should be a service web call for the entity Q7889 : https://qanswer-svc3.univ-st-etienne.fr/fact/get?id=11534&category=EMPTY&property=EMPTY

[Not Working] https://en.wikipedia.org/wiki/Let_Your_Hair_Down_(Grimm)#:~:text=I'm%20along%20for%20the%20ride,%20and%20any%20episode%20that%20features%20-,silas%20weir%20mitchell

(Delete the content before comma, comma included)
[Working]
https://en.wikipedia.org/wiki/Let_Your_Hair_Down_(Grimm)#:~:text=%20and%20any%20episode%20that%20features%20-,silas%20weir%20mitchell

Basically, check the api documentation how to handle the situation when prefix contains comma(,)