-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agent Merge Request - Velero #6679
Comments
ridabrams just force-created agent J. H. Lindholm III. That's probably a bad idea. |
well she did add an associate of relationship and both agents have issued identifiers now so I would say a little better than no-data. They are legacy so if we figure out their names in time we will update! |
I would like to remove that relationship. This is doing nothing a verbatim agent can't do, except preventing us from being able to accurately reflect the names our collaborators would like us to use. @ArctosDB/agents-committee |
Well that's a separate issue... which I'm not opposed to since it's pretty vague but more importantly very sporadically applied to be quite useless honestly! |
Use this template when you discover two agents that you believe represent the same person or organization.
Agent that should remain after the merge
This agent should represent the same person or organization as the agent below, but be of higher quality (more complete name, or includes additional information such as dates, relationships, addresses). Navigate to the agent page, copy the url and paste it below:
unknown
Agent that will no longer remain after the merge
This agent should be of lower quality than the agent into which it will be merged. Navigate to the agent page, copy the url and paste it below:
ridabrams just force-created agent Velero.
That's probably a bad idea.
Reason for merge
Please provide the reason you believe that these two agents represent the same person or organization.
no-data agents should not exist
Please add this issue to the Agents Project
@ArctosDB/agents-committee
@mkoo
The text was updated successfully, but these errors were encountered: