Transactional Query when Adding a New Instrument Translation - Inquiring Wikidata through Frontend

When adding new instrument names, the titles are first queried from Wikidata in the frontend. This data is then sent to the backend to check whether i. the list contains any duplicate entries and ii. any of the items already exist in the UMIL database. Finally, the verified entries are added to the database. However, I believe the some points should be considered:

**1. Lack of unified database querying**: Wikidata queries are handled in the frontend, while UMIL queries are handled in the backend.
**2. Potential circumvention of Wikidata querying**: Since Wikidata querying occurs in the frontend, it can be disabled or bypassed by the user. Moreover, this separation undermines the "transactional" integrity of adding new entries, as checking Wikidata and adding to the database are not performed within a single transaction. This issue is directly related with the “Confirm Publish” window.
**3. Loss of information when removing duplicate entries**: When duplicate instrument names and languages are submitted (either within the same query or across consecutive ones), the later duplicates have no effect on the dataset. However, each entry’s “source” information could be valuable for reviewers when evaluating these submissions.