Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: advanced validation options #109

Open
geritwagner opened this issue Jan 3, 2023 · 0 comments
Open

feat: advanced validation options #109

geritwagner opened this issue Jan 3, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@geritwagner
Copy link
Collaborator

geritwagner commented Jan 3, 2023

Feature Request

Describe the Feature Request

The validation should be extended and provide the option to validate the type of review.

Describe Preferred Solution

The review types should be required by the endpoint interface to implement a new method (validate()).

The following validation options should be implemented:

Operations-specific (implemented as methods of the validation operation):

  • search:inclusion-percentage (i.e., the number of papers that were prescreen-included relative to the number of all papers that were retrieved) should be in a particular range (e.g., 0.1 < inclusion-percentage < 0.5).
  • pdf-get: percentage of papers for which PDFs are not-available should not exceed 0.1.

Review types (based on Templier and Paré 2018):

  • Review types requiring multiple search techniques should include a citation search (a SearchSource with SearchType=BACKWARD_SEARCH|FORWARD_SEARCH)
  • For review types focusing on emergent topics, the average age of papers in the sample should not be higher than 10 years.
  • For review types requiring authors to minimize publication bias, the sample should contain unpublished ENTRYTYPE
  • For review types requiring parallel independent prescreen or parallel independent data extraction, the git history should contain merge commits

The data required for the validation is available in the review_manager.settings, the records (review_manager.dataset.load_records_dict()), and the git history (via review_manager.dataset.get_repo()).

Expected Effort Required

2 months, 5 people.

@geritwagner geritwagner added the enhancement New feature or request label Jan 3, 2023
@geritwagner geritwagner modified the milestone: v0.7.0 Jan 3, 2023
@geritwagner geritwagner added this to the v0.8.0 milestone Jan 14, 2023
@geritwagner geritwagner added the good first issue Good for newcomers label Feb 6, 2023
@geritwagner geritwagner removed this from the v0.8.0 milestone Feb 7, 2023
@geritwagner geritwagner added this to the v0.10.0 milestone Feb 24, 2023
@geritwagner geritwagner removed this from the v0.10.0 milestone Jun 2, 2023
@CoLRev-Environment CoLRev-Environment deleted a comment from RobertAhr Aug 18, 2023
@CoLRev-Environment CoLRev-Environment deleted a comment from Lexi04 Aug 18, 2023
@geritwagner geritwagner removed the good first issue Good for newcomers label Oct 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant