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
Currently the labels in the SYNERGY dataset tell if a record is included during the full text screening.
For some research it might also be useful to have a dataset where the inclusions indicate a title/abstract inclusion.
The first 2 ways to include this information that come to mind are:
Alter the definition of a dataset so it can contain both the full text inclusion label as well as a title/abstract label.
Add an additional dataset for the title/abstract inclusions.
The first option requires some changes in the Synergy pipeline, as well as some changes which inclusion type to select for use in ASReview. It is also good to note that not all datasets have both types of labels available.
The second option would work in the current style, but would create a lot of duplicate data.
The text was updated successfully, but these errors were encountered:
For new datasets I will add an additional column "label_abstract_included".
This will not hurt the rest of the pipeline.
For this issue I would like to alter the datasets in Synergy 1.0 to included this column as well and fill it if the data is published.
EmilyWes
changed the title
Add labels for title/abstract inclusions
Add labels for title/abstract inclusions for current datasets
Nov 29, 2024
Currently the labels in the SYNERGY dataset tell if a record is included during the full text screening.
For some research it might also be useful to have a dataset where the inclusions indicate a title/abstract inclusion.
The first 2 ways to include this information that come to mind are:
The first option requires some changes in the Synergy pipeline, as well as some changes which inclusion type to select for use in ASReview. It is also good to note that not all datasets have both types of labels available.
The second option would work in the current style, but would create a lot of duplicate data.
The text was updated successfully, but these errors were encountered: