Changes between Version 22 and Version 23 of Ticket #525, comment 10
- Timestamp:
- Apr 12, 2016, 12:09:36 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #525, comment 10
v22 v23 1 1 Design discussion: 2 2 3 * It was decided to perform the INCA data import in a single session, using the complete set of INCA data files as input, since this allows a check to made, whether some INCA data annotation types are missing in a specific import session.3 * It was decided to perform the INCA data import in a single session, using the complete set of INCA data files as input, since this allows a check to be made, whether some INCA data annotation types are missing in a specific import session. 4 4 * The INCA import wizard should perform an initial check of each INCA data file, after which the results are presented to the user. It should be possible to initially select a simple file check, that skips an intricate database consistency check (part "`C.`" in the table below), and therefore can be performed much faster. 5 5 * Properties of the INCA file checks:[[BR]][[BR]]a. If critical problems are encountered, import should be blocked.[[BR]]b. If problems with individual headers/data lines are encountered, the corresponding data columns/lines might be skipped during import; it is then the user's decision whether to fix the problems in the data file, or proceed with import of the eligible data.[[BR]]c. Basic results from the file check should be presented in the web form. In addition, it should be possible to open/download a text file with more detailed information from the file check by clicking on a button. The file should include the information presented in the web form, but also optional information on what headers or data lines problems were found with.[[BR]]d. In the report file, due to the sensitive type of information in the INCA data file, temporary patient ID values should be used instead of personal numbers to identify entries in the INCA file.
