Skip to content

Request - Make attribute search in Agents consistent with other attribute sesarches #440

@Jegelewicz

Description

@Jegelewicz

Help us understand your request (check below):

  • search or data request (help with SQL or provide the specific fields you are trying to retrieve for your collection)
  • add a new Github user to the Arctos Users team
  • a new barcode series
  • a new term for data entry or management
  • a change or new report or label
  • update to an Agent (split, merge, or other type of change)
  • bulkload changes (to Agents, Identifiers, etc that are not already available as a bulkloading tool)
  • new feature or otherwise a good idea to make Arctos even better
  • quarantine taxon name and suggested replacement (please supply links)
  • API key request (see https://handbook.arctosdb.org/documentation/api.html for requirements)
  • error or bug (please include enough specific information to reproduce)
  • general inquiry (or email arctoscontact@googlegroups.com)
  • access issue (see https://arctosdb.org/faq/)
  • other

Searching agents one attribute at a time makes getting to potential duplicates difficult. If I have the agent "R. Bernstein" and I want to know if they are in Arctos, I can put that string into the Agent name search field and I will get no results. If I put Bernstein into the attribute value and last name into the attribute type, I will get 6 results, only one of which MIGHT be a match to my agent - Robin Bernstein.

While the second method is better for catching potential duplicates, it fails with more common last names. Searching last name Smith will only return 75 matches, even though there are far more potential Smith agents to review.

Image

If the attribute search in agents worked like the one in locality:

Image

I could search

first name R
last name Bernstein

and get a more limited and better suited list of results to review. In addition, I believe that in most cases it would help get past the 75 record limit.


Please review the Arctos Code of Conduct to ensure respectful communication, and see https://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html for more information about submitting and managing Issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions