-
Notifications
You must be signed in to change notification settings - Fork 53
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
Potentially relevant papers ranked for curation #1165
Comments
This issue contains monthly updates to an automatically ranked list of PubMed papers as candidates for curation in the Bioregistry. Papers may be relevant in at least three ways: These curations can happen in separate issues and pull requests. The full list of ranked papers can be found here. If you review any of these papers for relevance, you should edit the curated papers file here; these curations are taken into account when retraining the ranking model. New entries for 2024-07-10 to 2024-08-09:
|
This issue contains monthly updates to an automatically ranked list of PubMed papers as candidates for curation in the Bioregistry. Papers may be relevant in at least three ways: These curations can happen in separate issues and pull requests. The full list of ranked papers can be found here. If you review any of these papers for relevance, you should edit the curated papers file here; these curations are taken into account when retraining the ranking model. New entries for 2024-08-02 to 2024-09-01:
|
This issue contains monthly updates to an automatically ranked list of PubMed papers as candidates for curation in the Bioregistry. Papers may be relevant in at least three ways: These curations can happen in separate issues and pull requests. The full list of ranked papers can be found here. If you review any of these papers for relevance, you should edit the curated papers file here; these curations are taken into account when retraining the ranking model. New entries for 2024-09-01 to 2024-10-01:
|
Updated curated papers list with all papers identified from Aug 9th in #1165. Curated new provider for PDB Structure called 'furna'. PMID: [39074139](https://bioregistry.io/pubmed:39074139) --------- Co-authored-by: Mufaddal Naguthanawala <[email protected]> Co-authored-by: Charles Tapley Hoyt <[email protected]> Co-authored-by: Benjamin M. Gyori <[email protected]>
This pull request updates the `curated_papers.tsv` file with all PubMed papers identified till 2024-10-01 in #1165. Here are some statistics about the classification of each paper based on relevancy_type so far: **Relevant (1) classifications: 14** - new_prefix: 3 - new_provider: 4 - new_publication: 2 - unclear: 2** - existing: 3 **Irrelevant (0) classifications: 40** - irrelevant_other: 31 - no_website: 2 - not_identifiers_resource: 7 ** 1. [39104285](https://bioregistry.io/pubmed:39104285) is a provider for UniProt IDs but was not curated due to the variable nature of the `uri_format`. 2. [38991851](https://bioregistry.io/pubmed:38991851) was curated as a prefix but there was some discussion about whether it should be a provider instead. See #1194. Regardless, both of these were curated as relevant (1) which seems to be the more important classification. --------- Co-authored-by: Mufaddal Naguthanawala <[email protected]> Co-authored-by: Charles Tapley Hoyt <[email protected]>
This issue contains monthly updates to an automatically ranked list of PubMed papers as candidates for curation in the Bioregistry. Papers may be relevant in at least three ways:
(1) as a new prefix for a resource that can be added to the Bioregistry,
(2) as a provider for an existing prefix, or
(3) as a new publication for an existing prefix already in the Bioregistry.
These curations can happen in separate issues and pull requests. The full list of ranked papers can be found here. If you review any of these papers for relevance, you should edit the curated papers file here; these curations are taken into account when retraining the ranking model.
Entries for a batch of papers from 2022:
The text was updated successfully, but these errors were encountered: