Redesign Wikidata interaction workflow
- Dominant language
- Python
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Current implementation of Wikidata interaction of adding new instrument name and image upload in #164 involves simultaneous data entry into Wikidata and the UMIL database. This faces challenges such as:
- Confusing Wikidata Authentication for user
- Lack of controlled verification of edits
I propose a new workflow design:
- User is only able to submit new instrument names and images to UMIL database
- Maintain the InstrumentName model from previous design, add that each name has a "new" boolean flag, indicating names that have yet to be added to Wikidata
- New instrument names and images undergo intermediary verification process that allows credible data to be uploaded in batches from the DDMAL Wikidata account
- Implement option from old design that allows users to sign into their own Wikidata account to make immediate edits
Critiques of this design:
- Verification should be embedded when the user enters instrument name/ image so further intermediary batch verification seems unnecessary
- Users will have to wait a certain amount of time to see their edits
Benefits of new design:
- Greater control over Wikidata edits
- Eliminates need for user Wikidata OAuth request for access token
Steps for implementation:
1. Implement user-UMIL database interaction (add new instrument name, add new image)
2. Consider how to verify instrument names and images for copyright
3. Automate batch uploads of instrument names and images to Wikidata
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.