We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Currently, if we reprocess 2023 data in 2024, any new candidate-naming will start from WNTR23aaaaa (and so on).
Proposed solution Query last_name as the name assigned to the last candidate in the year that the candidate-to-be-named was detected?
The text was updated successfully, but these errors were encountered:
It actually doesn;t work for sources in the same year too, as it assumes candid is ordered similarly as objectid but that is not true
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
Currently, if we reprocess 2023 data in 2024, any new candidate-naming will start from WNTR23aaaaa (and so on).
Proposed solution
Query last_name as the name assigned to the last candidate in the year that the candidate-to-be-named was detected?
The text was updated successfully, but these errors were encountered: