-
-
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
Feature Request - Find low quality data when collection/identification dates are outside birth and death range of the agent #4551
Comments
Agents Committee discussed that this tool would be really useful for helping with a first pass of all Agent clean-up. |
collecting dates are in https://arctos.database.museum/Reports/cat_record_reports.cfm?report_name=dates:%20collecting%20vs.%20collector, need new report for identification dates |
Here is an example of some stuff that could be cleaned up Collector = Joseph William Winthrop Spencer (Note - the identification dates and specimen event dates are also 1840-01-01!) Affected records - https://arctos.database.museum/saved/1660169124103 To Do:
@dustymc this seems like a lot - but it would be great if we could "make it so"! |
From #4550
Is your feature request related to a problem? Please describe.
Our data looks less than "research grade" when we are attributing actions to people who have not been born or are dead at the time of the action.
Describe what you're trying to accomplish
Increase data quality. Disambiguate agents.
Describe the solution you'd like
If any date associated with an agent action is before they were born or after their death, it should raise a red flag that either the date or the agent is incorrect.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
This could also be very helpful when trying to determine which agent is YOUR F. Stephens
Priority
Please assign a priority-label. Unprioritized issues gets sent into a black hole of despair.
The text was updated successfully, but these errors were encountered: