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

Guidelines for the users to resolve the priorities between SeqCode and ICNP names #90

Open
uqmchuvo opened this issue Dec 1, 2022 · 1 comment
Labels
documentation Improvements or additions to documentation for-large-team-discussion
Milestone

Comments

@uqmchuvo
Copy link

uqmchuvo commented Dec 1, 2022

Draft a workflow showing how date of priority is determined by ICNP and how it should be treated to resolve priority issues between ICNP and SeqCode names.

GTDB will take care of this as part of the species clustering pipeline.
Therefore, once GTDB get an idea how to get the dates and times for the ICNP names published after 2022, we should be able to implement a similar wf for the registry where users can quickly resolve priorities conflicts (smth like an extra tool that can be part of the Useful Links on the main page).

The date and time of the name published in IJSEM needs to be processed for this. Validation lists include sequence numbers to determine the priority, if the sequence number is the same - one need to check the order of the name in the original ms. This is manual part of the work. But the reference from the validation list can be given to access it faster via the registry. Comes down convincing IJSEM to give an access to the record and not to their lists in the journal...I will try to involve both IJSEM and LPSN since the latter have money and can maintain a db for them...

@lmrodriguezr lmrodriguezr added this to the v2.0 milestone Dec 8, 2022
@lmrodriguezr lmrodriguezr added documentation Improvements or additions to documentation for-large-team-discussion labels Apr 1, 2023
@lmrodriguezr
Copy link
Member

Hi @uqmchuvo

With the changes introduced to rule 23d, I'm now revisiting this issue. Do you think this is doable/viable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation for-large-team-discussion
Projects
None yet
Development

No branches or pull requests

2 participants