Hi Dimuthu, Let me bring back the questions we discussed at the call to a discussion thread. We currently see the following requirements from MFT. Let's discuss further here.
1) Transferring files from the microscopes to the users storage. In this, there's no authentication layer between the users other than a root level authentication (if there's anything possible). The user and folder structure has to be understood from the folder or file path specified at the microscope. Eg: if the file path at the microscope is "./abce-microscope/dinuka/session-36/bacteria-sample.png", It should be uploaded to the user "dinuka" to the folder "./abce-microscope/session-36" in his user drive. @Marru, Suresh <[email protected]> @Kuruvilla, Tanya Elizabeth <[email protected]> I would +1 for above. I believe it's good to let the users share the files to the groups manually instead of taking that also from the microscope file path. In my perspective, I would like not to share directly. Instead I would like to go back to my computer and see the files and do any modifications if needed and then share with the PI groups. 2) For file management, there's the need of managing folder structure for individual users. And the users should be able to share the files or folders to individual users or groups. @Christie, Marcus Aaron <[email protected]> I think for the user storage management within the diravata-django-portal also, we could use MFT if these requirements are satisfied from MFT. 3) Form the microscopes, since there's no way of getting individual user authentication processed and it has to be deeply coupled with the path of the files created (1) and also since the creation of the files is continuous ,there's a need of having a folder syncing capability which has to keep watching the file changes. Regards, Dinuka
