Relationship restrictions for potential dupe agents

[adhornsby]

Error Text

ERROR: "bad duplicate of" and "potential duplicate of" agents cannot be in other relationships. Delete all relationships to or from this agent and save before proceeding.

Where it happened

https://arctos.database.museum/agents.cfm

Steps to get there

Trying to set up "potential duplicate of" relationship between Pipe Holzemer and Richard Holzemer, which are also both "associate of" Bell Museum.

Problem

The error and solution are clear. I'm just wondering why this needs to be the case and if we can lift the restriction. It's useful for us to have both the associate and potential dupe relationships.

Solution

Community response with directions for how to correct the problem

[dustymc]

The idea is that any sort of relationship should stop merging; something with that much information needs a human's close look - all developed before 'potential duplicate' was added.

I would like to see how #6813 plays out first. If we're going to demand high-quality Agent data then this won't matter: mergers should be exceedingly rare and completely unambiguous. (Neither of your examples look like they need to be agents from here.) If on the other hand we're going to devalue Agents then I think we should probably remove about all restrictions, they just get in the way from that viewpoint.

[Jegelewicz]

"potential duplicate of"

should be available even when other relationships exist? It doesn't DO any merging - just indicates that someone thinks the agents might be the same.

Still, I agree about #6813

[adhornsby]

Gotcha, and I can stop making agents with that little info going forward. I have tended to make them when I know they're going to show up for us a lot, regardless of how much info we have at the moment.