For example, in IDMapper.py, there is a trailing main function that is not used anymore with the new GUI.

When saving in the ID Mapper, the data in Gender, CandidateStatus and PhoneNumber fields will be erased from the XML file.

Have a check if this value exists in the XML file. If so, keep the same value, else value would be " ".

• Main page of the scheduler is now reading the XML file. (done)
• Modify ID Mapper to be able to read the new XML structure and IDs. (done)
• Write to the XML file. (done)
• Implement opening of an existing XML file. (done)
• Implement creation of an new XML database file based on a template.
• Get rid of pickle dependency. (done)

The need for PyDICOM or the dicom tool kit should not prevail from opening DICAT (especially when one just wants to use the scheduler). Modify the code to check whether the tools needed are installed and display the error message in the DICOM anonymizer window instead.

• Instead of having the visit displayed as labels in the Calendar section of the data window, have them displayed as Entries/Dropdowns and disable the edit by default
• Clicking on the Edit button next to the row should enable the fields of that row to be edited and saved.
• Replace edit button by save button when in edition mode
• Add cancel/delete buttons next to the edit/save button. When in edition mode, save and cancel buttons will be on top. When in readonly mode, Edit and Delete button will be on top.
• Implement delete button action (display message are you sure? If yes, delete the visit from XML file and data tables)
• Implement cancel button action (display a message are you sure? If yes, refresh the visit row with old values, if not, stay in edit mode.
• Implement save button action (grep new values from the row, save them in the XML file and update the data tables)

This was brought up by @MounaSafiHarab. In order to be able to use DICAT and not remove every non-editable field entries we could allow the fields to be zapped to be edited or kept during deidentification.

Solution: On the page where we see the fields with their value, add check boxes that would allow to keep or edit the fields, changing the dictionary with the list of fields to zap or edit.

Once a visit is set to "completed"

• automatically check when next visit should be scheduled
• create the new visit in the XML file and data table views
• set status of this new visit to "to schedule" (datatable.py)

User could change the background used to highlight active candidates, excluded candidates etc...

Remove menus at the top of the scheduler except for:

• settings
• help
• about app
• quit app?

Investigate how we could add password protection to the XML file that stores the patient information.

• Have a pop up calendar a bit like google calendar where you are able to enter subject directly into the calendar
• Automatically open to today's date

Might need to refresh data table to include new candidate (line 100 of scheduler_application.py).

See all TODOs and exception listed in the code. For now, it usually prints in the console.

• Make language selection dynamic
• Extend the language selection to other tabs that just the scheduler
• In datatable.py, around line 173: change for non-language parameter for visit status active & tentative that are hard-coded.

Hey this should have a license! Maybe GPLv3 like LORIS?

This error will occur if PatientName left blank and clicking De-identify

python DicAT_application.py
Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1413, in __call__
    return self.func(*args)
  File "/home/gluneau/DICAT/dicat/dicom_anonymizer_frame.py", line 245, in collect_edited_data
    self.dirname, self.field_dict)
  File "/home/gluneau/DICAT/dicat/lib/dicom_anonymizer_methods.py", line 244, in dicom_zapping
    subdirs_list)
  File "/home/gluneau/DICAT/dicat/lib/dicom_anonymizer_methods.py", line 420, in create_directories
    os.mkdir(original_dir, 0755)
OSError: [Errno 17] File exists: '/home/gluneau/aaa/bbb/CCC6029_902717_V24_RES/'

See pull request #81

List of DICOM tags: https://dicom.nema.org/medical/Dicom/2017e/output/chtml/part06/chapter_6.html

• Implement automatic range for next visit to be scheduled based on latest visit completed (datawindow.py)

Using the mass_deidentify.py, white space can be introduced in edited fields which might cause some failure when submitting the DICOM studies to LORIS-MRI.

Solution: remove the white leading and trailing spaces from the edited fields.

When searching a candidate, display only the candidates that matches one of the fields in the data table instead of selecting just one.

• ID Mapper
• Scheduler

See how could have a date widget instead of a text field for date of birth (would be nice to be able to select a date based on a calendar).

See pull request #65:
This functionality has been added by copying code made available at https://github.com/moshekaplan/tkinter_components.

Not sure if it is ok...

• DICOM de-identifier tab
• ID mapper tab
• Scheduler tab

Currently, when creating a new candidate with the same ID, it will overwrite the already existing candidate instead of sending out a warning that the ID already exists.

Right now, it only refreshes the data table that was used to open the data window.

• have the values of status_options list for candidate status drop down customized based on project information ( #39)
• lots of other stuff to do and think about

Move the dict_match and array_match functions from the datamanagement.py to the utilities.py file.

• implement a drop down for the candidate status
• have the values of the drop down customized based on project information => this has been added to the project information ticket (#41)

Add a customization functionality to choose which DICOM field to zap or edit

DICOM de-identifier uses the first file in the directory to read DICOM fields. Should check if that file is indeed a DICOM.

At the moment, the scheduler greps the date information with time with one single XML field:
2015-05-05 13:50

Modify the code so that it takes that information in two different fields:
2015-05-05
13:50

Installation of PyDICOM is documented here: https://pydicom.readthedocs.io/en/stable/getting_started.html#installing

Implement field checking for data entry errors:

• duplicate identifier
• date format
• required field to save

Hi,
I am trying to additionally delete a data field. I have added it to the XML:

But after running it’s still there:

Have a section in the README to document how to mass run de-identification using PyDICOM and add links to the PyDICOM Github repo / how to section.

• Code clean up
• Find better title for the data window
• Around line 248: add logic "foreach" to create a table showing each visit

• Create the new visit button
• Call check_visit_data with options (self.candidate, 'new') (in visit.py)
• Modify save_visit_data function in datamanagement.py to save new visits for a given candidate

Now that PyDICOM is used for the DICOM deidentification, remove the dcmtk methods since we do not support it anymore (neither document it).

Check that the following scripts are not used anywhere. If not used, remove it.

• newcandidatewindow.py script (removed)
• create_alldata.py script (removed)
• remove *kwargs option from scheduler_candidate.py

Comment and clean up the code of the following scripts:

• lib/init.py
• lib/config.py
• lib/datamanagement.py
• lib/dicom_anonymizer_methods.py
• lib/multilanguage.py
• lib/resource_path_methods.py
• lib/utilities.py
• ui/init.py
• ui/datatable.py
• ui/datawindow.py (#50)
• ui/dialogbox.py
• ui/menubar.py
• ui/projectpane.py
• DICAT_application.py
• dicom_anonymizer_frame.py
• IDMapper.py
• scheduler_application.py
• scheduler_candidate.py
• scheduler_visit.py
• welcome_frame.py

Could have an option to re-organize a DICOM folder into sub-folders containing the different series.

Main folder
-> t1 folder
-> flair folder
-> t2 folder etc...

In the DICOM de-identifier tab, after clicking "De-identify" the only way to tell that it's currently working is by hovering the mouse over the "Dicom Field" column of the table and seeing that the cursor changes to a spinning wheel.

If you hover anywhere else, the cursor goes back to normal and it looks like the progress is done but nothing has happened.