Closed lwjohnst86 closed 2 years ago
I think that a final document that can be easily parsed by R is the way to go. I was thinking of a table with references as rows and the following columns: URL, year, journal, project-tag, notes. Additionally, the database where it was found/terms used to find it, though maybe that info is redundant.
@MarioGuCBMR yea, I had been thinking of a csv table too... I'm going to think about it more though...
Modified some things to fit with our new approach. Merging and closing.
Related to https://github.com/science-collective/admin/issues/5. Here is one way of tracking and adding references and website urls of resources we find.
I thought this way might be best because it makes it easier to add things to GitHub/through Git. The common way of doing systematic reviews etc is to add things to a bibliography manager like e.g. Zotero, Mendeley etc and than sharing access to this through e.g. Dropbox (or sending via emails :vomiting_face:). Of course the most common way in research is not to use Git. I did some googling around and there isn't much information on how we can work together collaboratively via Git/GitHub.
With this way, we only need at least the URL or DOI and we can use scrapping tools in R to get more info about the resources. Plus, we can add our own project tags and notes to each reference.
Thoughts? Check out the
data-raw/README.md
file for an explanation for adding references.