Champion
•
5.1K Messages
•
118.7K Points
contribution form should screen for duplicate cast
NB: this post is _not_ a request to clean up a specific contribution, but a report of a deficiency in the contribution _system_.
Yesterday I added a 2012 title where the cast was listed In Order of Appearance _and_ several cast members played multiple roles.
I didn't catch one of those, and entered the second role as a new cast member.
The form did not complain.
It should have.
Now I have 2 pending contributions: 1 is part of the original Add Title #210527-213424-940000, and another is a modification to the Character (to add the second role (and cast order)) #210527-231012-000000.
Ugh. Just checked the statuses. The original contribution had second item pending, and _that_ item (2012 release date) has been declined, seemingly for the reason the cast member should have been declined.
adrian
Champion
•
3K Messages
•
72.5K Points
5 years ago
This is an interesting bug. If you enter a cast member who is already a cast member, you will get an error. However, if you enter a cast member twice, it does not flag this as an error.
0
0
Peter_pbn
Champion
•
15.7K Messages
•
344.2K Points
5 years ago
Similarly, a warning if you enter the same order number twice would be helpful. But I don't think the form was designed to check what you type in one field for one credit against what you type in another field for another credit, so it's probably one for the suggestion box rather than a bug.
1
Michelle
Employee
•
18.2K Messages
•
321.3K Points
5 years ago
Hi bderoes & All -
Thanks for sharing these observations within the Contribution form, I have filed a ticket with the applicable technical team to review this issue/suggestion, once I have an update I will share the status here.
Cheers!
0
Fran
Employee
•
3.6K Messages
•
36.3K Points
2 years ago
Hello bderoes,
Thanks again for reporting, I wanted to provide an update on the issue. We are so sorry it has taken this amount of time to resolve, due to our backlog we can't provide an exact timeframe as to when the issue at hand will be prioritized, for this reason we are closing this thread. But know that we are still tracking this issue and it will be picked up. Again, I apologize for any inconvenience this may cause, and we will make sure to revist it as soon as possible.
0
0