Upload with websockets and integrated client side pseudonymization about adit HOT 3 OPEN

Addition to the PSN process: Dept+ID Strings should be padded to ensure the same length before hashing, otherwise there's a small risk of being able to relate pseudonyms to departments, which is undesirable

from adit.

Documentation of workflow as it stands:

• Client is given files to upload
• Override FileHandler to forward files to pseudonymization method
• Pseudonymize Files using Lucas dcmjs implementation (embed using Alpine.js)
• Post Files into a tempdir on server (using ajax, but could, more easily, probably be implemented by providing a temp dir to the Django FileField? ref method handle_uploaded_file on https://docs.djangoproject.com/en/4.1/topics/http/file-uploads/ )
• On the server side, create a Batch Transfer Job, using the adit node as source and desired destination
• Run the job using TransferUtils
• Clean up tempdir

@medihack I think that is how we devised it, if there are any problems with this let me know 👍

from adit.

• setup new Upload app
• registration in menu bar
• Form view
• data transfer view
• asynch
• doesn't send data to same URL as Form comes from
• checks destination of institute and uses it as transfer destination
• view safety
• User login
• Insitute access
• destination available
• check if uploaded files all belong to same patient -> only single patient uploads are allowed
• Html Template
• File search Field
• Text Field for PatientID which will be used with FixedValueAnonymizer
• embed Anonymization with Alpine.js
• Anonymization
• usage in JS File (which will be referenced in Template)
• use with seed to guarentee identical anonymization outputs
• Data Transfer
• test with Orthanc as receiving node
• check and use existing transfer implementation

from adit.