Problem
Upon uploading some new mismatches, something that I'm realizing is that the description field for the mismatch file isn't very apparent within the Mismatch Finder UI. This doesn't allow for the person uploading the data to provide information about the context of the upload that would help a Wikidata editor fix the mismatches. To me there are as of now two situations for mismatches:
- It's a simple mismatch and one value should be chosen
- The mismatch AND other things on the item in question should be addressed
Examples are:
- The mismatch is pretty clear on one property: external source says date of birth for a person is 1969, and Wikidata says 1970
- The mismatch has lead to an understanding that there are more problems than just the mismatch: external source says date of birth of a person is 1969, Wikidata says 1970, and it's because there's a wrong identifier on the item that is leading to a soccer player also being a chess player so the items need to be split
A screenshot of the current UI is:
Having a more apparent description that could also be renamed Description / Directions or something along those lines would allow an uploader to provide more context so that issues in the second case could be addressed. Without this an editor would potentially just fix the mismatch, with the other data issues not being addressed.
Solution
There are various ways that the description could be made more apparent. To me marking it also as "directions" in the UI would be helpful, but I'm definitely not suggesting that another field should be added to the upload API. Description and directions should be in one text to simplify the work to be done. We could also leave the description in the last column and add some spacing between the username for the upload and date above it.
Interested to see what UX thinks on this!
Open questions
How to best deal with the space considerations for the Mismatch Finder UI is definitely something that needs to be accounted for.
Acceptance criteria
- The description field is a bit more apparent such that users would be able to see that there might be hints on how to best deal with the mismatch