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

Changing the project configuration deletes all activities #24

Closed
esyriani opened this issue Apr 22, 2020 · 1 comment
Closed

Changing the project configuration deletes all activities #24

esyriani opened this issue Apr 22, 2020 · 1 comment
Assignees
Labels
Projects

Comments

@esyriani
Copy link
Member

Describe the bug
ReLiS is supposed to support iterative systematic reviews. Therefore, we should be able to change the projection configuration (for example the classification scheme). It should allow me to add new categories, delete exiting categories, or update the configuration of existing categories. However, currently, if I re-generate my configuration and re-deploy it, it erases all previous activities: screening, QA, and classification data. Only the papers, authors and venues remain.

To Reproduce
Steps to reproduce the behavior:

  1. Create an initial configuration
  2. Screen one paper
  3. Classify that paper
  4. Modify the configuration
  5. Go back to see the screened papers and classified papers, or any statistics about screening and classification. Everything is erased

Expected behavior
If we want to "reset" the project, then we can delete all papers (see #19). But modifying the configuration should not delete the previous information. It should try to modify what exists. Especially for the classification scheme. We should allow anything the database allows to modify. So if we are modifying a table that has rows, we let MySQL tell us it is allowed or not.

@esyriani esyriani added the bug label Apr 22, 2020
@esyriani esyriani added this to Needs triage in ReLiS via automation Apr 22, 2020
@esyriani esyriani moved this from Needs triage to Critical in ReLiS Apr 22, 2020
@esyriani
Copy link
Member Author

esyriani commented May 8, 2020

Add the keyword keep_screening right after SCREENING in the configuration file to only modify the classification part, and keep the screening part untouched.

@esyriani esyriani closed this as completed May 8, 2020
ReLiS automation moved this from Critical to Closed May 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Closed
ReLiS
  
Closed
Development

No branches or pull requests

2 participants