Open ChristianGerloff opened 2 years ago
Hi @ChristianGerloff, nice idea! Regarding your tags:
I think the abstract is actually one of the most important things when it comes to integration into Rayyan as the initial screening should usually be based on the abstract. Otherwise, you would have to use the DOI/URL/pubmed-id (whatever is available) to get it. So I think the abstract would best be included.
I am not sure, if I understand the "RAYYAN-INCLUSION" and "-LABEL" categories correctly. If I do, these are the user-defined labels and include/exclude/maybe decisions which are printed into the csv when it is exported from Rayyan after the screening process in Rayyan is completed? This would mean that we do not need to define content for the "INCLUSION" and "LABEL" variables if it is about creating a csv for import into Rayyan.
However, before, we also discussed the possibility to include a function that collects all the reference lists of a given subset of papers (i.e., papes, screened positively in Rayyan) and uses this a input for a "second-level" literature search. To generate a list of this subset of papers, one would either have to export only the references from Rayyan that are labelled as "include" to csv, or export all papers to csv with the labels included in the "RAYYAN-LABEL" column and select the included references afterwards. In the second case, the "LABEL" variable would make sense. However, I think the first way is actually possible - so no need for that.
Is there possibly another use for the RAYYAN-NOTES variable that I am not aware of? Otherwise I actually think one could drop it entirely.
ADDITION: Would it be possibly to include the DOI (or URL if DOI not available) in the "URL" field? This would provide direct access to a potential source of the full text, figures, etc during the Rayyan Screening process. Also, is there an actual need for the Pubmed and PMC IDs? Maybe for a function, as referred to above, to search each papers reference list as pubmed stores a full list of references with each paper? If the latter is not needed, we could maybe also drop pubmed/pmc IDs.
Hey @LeonDLotter, thank you - yes, let's drop the "RAYYAN" fields for now. We don't really need the Pubmed and PMC IDs, but it's a default from rayyan, but I think it's fine if the field is empty. The notes will include the doi/url. For cross-refs, I would suggest to open a new issue.
Hey @LeonDLotter & @kashyapm94 , To enable a feasible integration with rayyan, we want to add a csv export. :smiley: Therefore, we can utilize the rayyan example csv. The column
Notes
contains several rayyan specific fields. Before we integrate all the fields, I would like to ask you for your thoughts on that. What do you think we really need, what can we leave out?suggestion
publication
objpublication
objpublication
objpublication
objpublication
obj -- check! @ChristianGerloffpublication_date
publication_date
publication_date
publication
objpublication
objpublication.category
Example