Userfeedback #765
Contribution Duplikate
| Status: | Neu | Start date: | ||
|---|---|---|---|---|
| Priority: | Niedrig | Due date: | ||
| Assignee: | Alexander Blum | % Done: | 0% | |
| Category: | - | Estimated time: | 0.50 h | |
| Target version: | Repertoire 2) Testing phase II |
Description
Ich kann Beiträge mehrfach für denselben Artist und denselben Contribtution Type anlegen. Sowohl für dieselbe VG als auch für unterschiedliche VGs, das ist verwirrend. Könnte man das unterbinden?
Related issues
Associated revisions
tried to avoind dupes in contributions; ref #765
at least, I added a multi-field validator on the frontend side; ref #765
History
#1 Updated by Thomas Mielke over 5 years ago
- Related to Userfeedback #768: Duplikate Tariff Category added
#2 Updated by Thomas Mielke over 5 years ago
- Assignee set to Werkeverwaltung
- Target version set to 2) Testing phase II
#3 Updated by Alexander Blum about 5 years ago
- Estimated time set to 0.50
On submission the data can be checked.
#4 Updated by Alexander Blum about 5 years ago
- Priority changed from Normal to Niedrig
#5 Updated by Thomas Mielke almost 5 years ago
- Assignee changed from Werkeverwaltung to Alexander Blum
Tried something like this in edit_creation (and add_creation):
dupe_found = False
for item in _contributions:
if (item['artist'][0].id == create['artist'].id and
item['role'] == create['role']):
dupe_found = True
break
# append contribution
if not dupe_found:
CreationContribution.create([create])
But the role in the sequence is an int whereas the role in the _contributions dict is a uuid. What's the raison d'être?
#6 Updated by Alexander Blum over 4 years ago
- Target version changed from 2) Testing phase II to Repertoire 2) Testing phase II
#7 Updated by Alexander Blum over 4 years ago
- Project changed from repertoire to collecting_society