You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's an apparent bias towards a substantial portion of the data being biomedical related due to how the data was sourced https://arxiv.org/abs/2209.00693 , but I was able to pseudo-randomly click on projects in map-of-github and find some that had data in papers.ecosyste.ms from other fields.
Repository vs. Package centricism.
The map of GitHub is repository centric where as packages.ecosyste.ms is package centric. A hacky approach would be to use GitHub metadata to guess at package manager and use repository name for probable package name. This would take one API call. However, a better approach would be to use exact full repository name => https://repos.ecosyste.ms/ => https://packages.ecosyste.ms/ => https://papers.ecosyste.ms/ as this would be an exact mapping.
Example projects in both map of github & papers.ecosyste.ms:
The text was updated successfully, but these errors were encountered:
JustinGOSSES
changed the title
Wonder if detailed project view could pull in papers that reference code projects from ecosyste.ms
Wonder if detailed project view could pull in papers that reference code projects from ecosyste.ms API
Dec 19, 2023
Basic idea:
I am wondering if the detailed project view could also list published papers that reference the code projects from ecosyste.ms when they exist?
https://papers.ecosyste.ms/ maps between code projects and published papers.
Intended behavior
When a user clicks on tidyverse/dplyr at https://anvaka.github.io/map-of-github/#11.2/43.5686/20.2982 , they see in the sidebar a list of papers that reference the code project, or maybe just a link to the papers.ecosyste.ms page for that package, in addition to the current GitHub sourced content.
Extent of available data
There's an apparent bias towards a substantial portion of the data being biomedical related due to how the data was sourced https://arxiv.org/abs/2209.00693 , but I was able to pseudo-randomly click on projects in map-of-github and find some that had data in papers.ecosyste.ms from other fields.
Repository vs. Package centricism.
The map of GitHub is repository centric where as packages.ecosyste.ms is package centric. A hacky approach would be to use GitHub metadata to guess at package manager and use repository name for probable package name. This would take one API call. However, a better approach would be to use exact full repository name => https://repos.ecosyste.ms/ => https://packages.ecosyste.ms/ => https://papers.ecosyste.ms/ as this would be an exact mapping.
Example projects in both map of github & papers.ecosyste.ms:
The text was updated successfully, but these errors were encountered: