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

"Local save" location isn't clear #241

Open
driusan opened this issue Aug 21, 2018 · 3 comments
Open

"Local save" location isn't clear #241

driusan opened this issue Aug 21, 2018 · 3 comments
Assignees

Comments

@driusan
Copy link

driusan commented Aug 21, 2018

When using the NDA Editor or Instrument Builder and you try and save locally instead of a "Save as" dialog it gives you a message like "Terms Information Saved in uploads/termforms/terms-abcd_cbcls01-m11-test.json!", but there's no information about where that path is relative to or how to find it, making it hard for end users to find instruments after saving them. (It seems to be relative to ~/Documents/, at least on a Mac, but I'm not sure if that's always true or just coincidental in this case..).

@sanuann sanuann self-assigned this Aug 21, 2018
@sanuann
Copy link
Collaborator

sanuann commented Sep 19, 2018

all data is saved in ~/Users/username/Documents/uploads/ and then in corresponding sub-folders. The /uploads/ directory is always created in /Users/username/Documents and is not just coincidental in this case.
I agree the local save locations isn't clear, perhaps the message on saving the instrument should include the full path information?

@sanuann
Copy link
Collaborator

sanuann commented Feb 3, 2019

@satra any suggestions?

@satra
Copy link
Contributor

satra commented Feb 3, 2019

@sanuann - i think there should be a place where BrainVerse saves its things, and then a place where a user can export the database or save an item or items. and correspondingly there should be a way to import these bundles. we can chat more about this when we discuss details next week.

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

No branches or pull requests

3 participants