Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alyx paths relative to root dir #600

Open
k1o0 opened this issue Oct 7, 2019 · 7 comments
Open

Alyx paths relative to root dir #600

k1o0 opened this issue Oct 7, 2019 · 7 comments

Comments

@k1o0
Copy link
Contributor

k1o0 commented Oct 7, 2019

Problem:
Different computers use different protocols and mount points to access data repositories. The fields in alyx are not general enough to allow users to easily construct an absolute file path for accessing a specific data record.

Suggested solution:
Changing the current fields so that there are 'base paths' for different protocols, e.g. http, smb. These should assume the user mounts or otherwise accesses the data from the root directory so that when combined with the relative path a complete path can be constructed.

@kdharris101 suggested perhaps having a different data repository type, however this would be a many-to-many relationship.

@nsteinme may also have an opinion on this.

@nsteinme
Copy link
Contributor

nsteinme commented Oct 7, 2019

Is that really the main problem? I thought it's more like just that some part of the path is left out entirely. The folder name "Subjects" is just not represented anywhere. That's separate from the smb drive and mount (\zubjects.cortexlab.net\data) and separate from the relative path (\mouseName...) but you can't get the full path without it.

@kdharris101
Copy link
Contributor

kdharris101 commented Oct 7, 2019 via email

@k1o0
Copy link
Contributor Author

k1o0 commented Oct 9, 2019

Is that really the main problem? I thought it's more like just that some part of the path is left out entirely.

It was suggested that by simply mounting/mapping the data repo at the subject folder level we wouldn't need to provide any other parts of the path. I think this is only part of the problem: there could also be a better way of representing the scheme/syntax of the protocol. That is, I don't want to hard-code a regular expression to replace /mnt/ with \\, which I recall was a suggestion, particularly as currently there is no indication on alyx of whether the data repository is accessible by SMB.

It would be nice if there was complete information so that a naive user could look at alyx and see exactly how to access the data.

@oliche
Copy link
Collaborator

oliche commented Oct 10, 2019

Scheme change: in the data repository scheme, rename Globus_path by mount_point or server_path which shows the path on the server.

@nsteinme
Copy link
Contributor

nsteinme commented Oct 10, 2019 via email

@rossant rossant self-assigned this Dec 14, 2019
@oliche
Copy link
Collaborator

oliche commented Jan 27, 2020

This needs a synchronized release of client code and alyx code or alias the rest serializer temprarily

@k1o0
Copy link
Contributor Author

k1o0 commented Jan 31, 2020

Yes let's coordinate this with the nessessary Rigbox changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants