When identical records are created in a transaction in two different places, the user is unable to disambiguate in WorkBench

[tlammer]

From @grantfitzsimmons:

In a case recently FirstName LastName was created as a determiner, but then later added as a collector in a different row in the same data set. It doesn't recognize that the determiner was created, so it tries to create it again as a collector. My theory is that it then creates 2 temporary (not yet in existence) agents in the transaction that no longer exist when you try to disambiguate them.

---

Describe the bug
In the Workbench, if:

• multiple agent roles are in the Data Mapping for a data set, such as determiner, preparator, and collector
• and an agent new to the database is entered in different roles
  the Workbench will flag the agent (other than the first and second reference) as requiring Disambiguation. When you click to disambiguate, you are notified the agent cannot be disambiguated.

There is no way to resolve the issue within the data set.

To Reproduce

1. Create a data set with multiple agent roles
2. Add information for an agent that is NOT in the database already.
3. Add the same agent information to multiple agent roles in multiple records, so the agent is listed at least 3 times in various roles and records.
4. Validate the data set.

Expected behavior
The new agent should match the agent created previously in the data set, regardless of role.

Please fill out the following information manually:

• OS: Windows
• Browser: Chrome
• Specify 7 Version: 7.11.3
• Database Name: kufishnntest
• Collection name: KU Fish Voucher
• User Name: abentley
• URL: [e.g. https://ku_fish-v7.test.specifysystems.org/specify/workbench/215/]

Reported By
Theresa

Additional context
Visible on the test server: https://kufishnntest-v7113.test.specifysystems.org/specify/workbench/29