-
Notifications
You must be signed in to change notification settings - Fork 172
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
[Docs] EEG Uploader doesn't load data for EEG Browser #9191
Comments
@laemtl said there's a cron job to be set up to make it work, that should be documented in the Configurations section of the README. |
this is more complex than initially thought: found in loading partial datasets troubleshooting Samir to try re-resourcing (eeg meeting, may 17) |
Documentation patch to resolve #9293. Let users and admins know that they will encounter a known issue (#9191), not a bug with their setup: This does this by: - Adding text visible to Users at the top of the module - Adding README message - Adding Help text note for users This does not resolve #9191, but it clarifies the state for LORIS users.
Found and confirmed during 26 testing, it's an undocumented (non-)feature that should be explained to users until there is a solution. Per Testing meeting April 4:
EEG uploader module will upload but not insert(?) data into LORIS in a way that makes it visible in the EEG Browser module.
The current Readme of this module implies that the data should be visible in the EEG Browser (invokes same permissions, etc) even if it doesn't say it outright, which is misleading enough.
This is also contrary to pretty normal user expectations, so it should be addressed in the documentation, and also flagged as a To do issue for the next release (if only to avoid bug reports).
Actual solution might include (see Imaging for examples of each):
The text was updated successfully, but these errors were encountered: