shofstet
commented
2 weeks ago For us it would be the local filesystem also important (f.e. over SMB or NFS-mount).
Open kdarras opened 2 years ago
shofstet
commented
2 weeks ago For us it would be the local filesystem also important (f.e. over SMB or NFS-mount).
To enhance integration of multiple platforms and collaboration it should be possible to retrieve recordings from other servers.
A sub-button "Connect" should be added to the "Add" button of the recordings addition function (#412 ) so that users are prompted with a choice of parameters just like Filezilla offers: user, password, host, port, protocol, etc.
Thus the system should allow using remote instead of local files. Recording meta-data and sites would be stored in the database just the same.
We should discuss which protocols should be offered instead of just SFTP, and how to enable interoperability with CEPH/S3 storage types.
This must be secure, and the credentials stored to enable a persistent, read-only connection. The remote server will typically belong to a partner institution.
After integrating the remote files, the usual integration steps prompting the user for the parameters that are filled into the recordings table follow.
These recording files can accordingly not be deleted. If they are selected, it should instead be possible to disconnect them, and the warning message should tell the users that the meta-data (the data inside the recordings table) will be deleted, and the remote connection removed.
In the future, we will want to be able to add entire remote collections that store the meta-data in a standard way. Already-linked folders should also be automatically scanned for new recordings in the future.
We should also find a more manual workflow to make sure that currently internally-stored recordings can be served instead by an external server after this transition, while preserving tags and relationships.