Skip to content
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

[BUG] Candidate namer broken #734

Closed
virajkaram opened this issue Jan 22, 2024 · 1 comment · Fixed by #763
Closed

[BUG] Candidate namer broken #734

virajkaram opened this issue Jan 22, 2024 · 1 comment · Fixed by #763
Labels
bug Something isn't working

Comments

@virajkaram
Copy link
Collaborator

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?

@virajkaram virajkaram added the bug Something isn't working label Jan 22, 2024
@virajkaram virajkaram changed the title [BUG] Candidate namer broken for reprocessing images from previous year [BUG] Candidate namer broken Jan 22, 2024
@virajkaram
Copy link
Collaborator Author

virajkaram commented Jan 22, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant