Mesort issueshttps://gitlab.informatik.uni-bremen.de/ZeMKI.Gitlab/mesort/-/issues2019-10-30T12:09:31+01:00https://gitlab.informatik.uni-bremen.de/ZeMKI.Gitlab/mesort/-/issues/23Classifiers2019-10-30T12:09:31+01:00ZeMKIClassifiersWe need to create classifiers, technically little images that can be assigned to each token to better categorize it.
In the backend, create a folder with pre-made classifiers and give it a name to sort them.
In the interview find a spac...We need to create classifiers, technically little images that can be assigned to each token to better categorize it.
In the backend, create a folder with pre-made classifiers and give it a name to sort them.
In the interview find a space to show them and make the interactions as follows:
1. click on the classifier
2. click on the token
3. We need to create an interaction if you want to move the classifier or delete it from a token, here some ideas:
* click on the classifier -> click on the token.
* to remove: click on a button "remove classifiers" then remove any classifiers you want. Then click again the button to remove this "mode".
Ask for images.1.1.0-BetaZeMKIZeMKIhttps://gitlab.informatik.uni-bremen.de/ZeMKI.Gitlab/mesort/-/issues/22Adapt the new interview result to multiple sortings and classifiers2020-01-30T12:59:11+01:00ZeMKIAdapt the new interview result to multiple sortings and classifiersNow an interview can have multiple sortings, later classifiers and it's necessary to show them in the interview result page.
In addition, we need to update the single sorting view to show the pdf file ready to print.Now an interview can have multiple sortings, later classifiers and it's necessary to show them in the interview result page.
In addition, we need to update the single sorting view to show the pdf file ready to print.1.1.0-BetaZeMKIZeMKIhttps://gitlab.informatik.uni-bremen.de/ZeMKI.Gitlab/mesort/-/issues/21Now 1 interview can have multiple sortings2019-10-21T09:51:49+02:00ZeMKINow 1 interview can have multiple sortingsNow the researcher is able to add a new sorting by clicking a button "save and add sorting".
Introducing this, we need to remove the "discuss sorting" phase and write down that researchers should discuss the sorting in that section, whe...Now the researcher is able to add a new sorting by clicking a button "save and add sorting".
Introducing this, we need to remove the "discuss sorting" phase and write down that researchers should discuss the sorting in that section, when the user say finished the sorting.
Consider adding a sorting_phase field (default value 1) in the tokens table that indicate in which sorting the token was created.
**Since Mesort is already in production, add the column in a new migration file.**1.1.0-BetaZeMKIZeMKIhttps://gitlab.informatik.uni-bremen.de/ZeMKI.Gitlab/mesort/-/issues/20Now the user can create tokens2019-10-21T09:57:10+02:00ZeMKINow the user can create tokensDuring the sorting phase of the interview, the user can define its own tokens. Implement an according interface to leave the calculation of the circles and the token position correct and well defined.
Backend-wise, create tokens on the ...During the sorting phase of the interview, the user can define its own tokens. Implement an according interface to leave the calculation of the circles and the token position correct and well defined.
Backend-wise, create tokens on the go, while giving on the created_by field a dummy user-id (that has to be migrated) that indicates "user during interview created the token".
Moreover, the user can also delete the token, for example by dragging it over an area that appears on-drag of the created token.1.1.0-BetaZeMKIZeMKIhttps://gitlab.informatik.uni-bremen.de/ZeMKI.Gitlab/mesort/-/issues/18Now the supervisor can *always* delete a study or an interview2019-09-16T11:57:35+02:00ZeMKINow the supervisor can *always* delete a study or an interviewImplement the always delete for the study and the interview.
Each time the user has to **confirm** and the text needs to be clear and concise.Implement the always delete for the study and the interview.
Each time the user has to **confirm** and the text needs to be clear and concise.1.1.0-BetaZeMKIZeMKIhttps://gitlab.informatik.uni-bremen.de/ZeMKI.Gitlab/mesort/-/issues/17Implement Actions Log2019-10-21T09:49:22+02:00ZeMKIImplement Actions LogThis action log should be visible in the admin area, and it needs to consult
When - Who - What was deleted.
Use a middleware or manually add the functionality at the end of each delete function.This action log should be visible in the admin area, and it needs to consult
When - Who - What was deleted.
Use a middleware or manually add the functionality at the end of each delete function.1.1.0-BetaZeMKIZeMKIhttps://gitlab.informatik.uni-bremen.de/ZeMKI.Gitlab/mesort/-/issues/15Debug mode for interview sorting2019-08-08T12:48:20+02:00ZeMKIDebug mode for interview sortingCreate a debug mode where you can see all the time the values you save.Create a debug mode where you can see all the time the values you save.ZeMKIZeMKIhttps://gitlab.informatik.uni-bremen.de/ZeMKI.Gitlab/mesort/-/issues/12Remove delete button from yourself in edit study's user part2019-06-04T14:11:41+02:00ZeMKIRemove delete button from yourself in edit study's user partA user can delete himself from the user part, remove this option.A user can delete himself from the user part, remove this option.1.0-BetaZeMKIZeMKIhttps://gitlab.informatik.uni-bremen.de/ZeMKI.Gitlab/mesort/-/issues/9Token are not saved in a study directory2019-05-15T15:34:37+02:00ZeMKIToken are not saved in a study directoryAll tokens are saved in the same directory, consider to create a folder structure like
`app/study{x}/tokens`All tokens are saved in the same directory, consider to create a folder structure like
`app/study{x}/tokens`1.0-BetaZeMKIZeMKI