-
Notifications
You must be signed in to change notification settings - Fork 12
Collaborations for OSrPRE API intergration #86
Comments
I took a look at the Mt Sinai reviews on their Github. It seems they're trying to standardize on a Markdown format (that's great!). A couple ideas / questions:
thoughts? |
@sajacy Thank you so much for your work and suggestions. We just got an email from the group at Mt. Sinai saying, as you mentioned, that they have the reviews are being publicly posted to GitHub as Markdowns on this repo: https://github.com/ismms-himc/covid-19_sinai_reviews. Also, they are pulling the reviews from this repo into the Observable notebook using the GitHub API: https://observablehq.com/@ismms-himc/covid-19-sars-cov-2-preprints-from-medrxiv-and-biorxiv. They suggest to directly upload the reviews to PREreview directly from GitHub. Similarly to the point you raised, Outbreak Science Rapid PREreview has a format with a structured questionnaire with two optional editing boxes. https://prereview.org, platform we would like to eventually merge, has the space for longer reviews of the type they have here. I see the following possible course of action here:
Tagging can also help make the content discoverable. Right now the user on OSrPRE has to tag the reviews with the "2019-nCOV" tag. But perhaps there is a way to search for keywords in the title of the preprint and abstract to automatically tag these preprints/reviews/requests? - refers to issue #83. |
@sajacy I've been debating a few ideas here, because the longterm goal that we need to map out is to merge the code bases supporting PREreview and rapid-prereview together. The idea that I've been discussing with @rudietuesdays @dwins and @dasaderi is to introduce a "type" or "template" to the attributes for a PREreview, and then allow for a choice of template:
where a long review can have some formatting (e.g. the Mt. Sinai format or similar to the template options on prereview.org) Then I think we want to help document/enable how the Mt.Sinai folks could post to OSrPRE using the API, where their templated long review would get posted as a prereview with the "long" review template, if that makes sense? We'd also need to expose "long" reviews in the interface on OSrPRE, which based on a conversation @dasaderi and @majohansson and I had tonight I think could look like a list reviews below the rapid review synthesis if that makes sense, and then open to a view of the one longer review. If we can sort this out, we can also merge over prereview from preview.org and actually move towards merging the platforms faster. |
Update on possible API standards that would allow for integration with preprint servers:
|
We heard back from bioRxiv. Richard said " If you can supply a feed of the articles we can add trackback links to them from bioRxiv." Can we already do this with the current API? @rudietuesdays @jheretic |
Related to PREreview/prereview-standup#111 |
ResearchGate (ongoing conversation) - so far all they have done is link to OSrPRE in their Resource page of the COVID-19 effort they just launched;
Observable notebook (Mt Sinai). They have ~100 reviews as docx files (with the DOI in the name) on Dropbox and they would like to upload these reviews to the PREreview site. They also want to be able to pull these reviews into the Observable notebook from our site after (using the DOI - which seems like this is possible).
covidpreprints.com (ongoing conversation) - covidpreprints.org: They said they want to look at how we could incorporate our API into the preprints on their timeline and asked for ideas on how to implement that. The code for their site can be found on github
SemanticScholar (Daniela needs to reach out)
bioRxiv/medRxiv (we had our meeting with Ted and Richard - see Add an API call that shows all of the reviews by preprint DOI, sorted by date #116 for follow-up)
The text was updated successfully, but these errors were encountered: