Open ddelpiano opened 1 year ago
Need to fix a few details about the user experience of this
My understanding is that we can implement an endpoint/link where the user is asked to login/register and something automatic takes the user to a ready to use workspace.
What's not clear is which workspace should we show to the user, whether a new one or any other preexisting workspace from the user (if any) or created for all the users passing through that link.
@ddelpiano There are 2 options: A) the user gets a fresh netpyne-ui to play with, build a model from scratch or open hardcoded tutorials, and B) the user goes deep into an existing OSB workspace which is loaded into netpyne-ui
B) is further down the line, and is a general function to add to osb: create a link to open application XXX with workspace YYY and file ZZZ from inside that workspace (which is in a format known to that application), e.g. https://www.v2.opensourcebrain.org/workspace/open/YYY/XXX?file=ZZZ
I thought A) was already enabled by http://netpyne.opensourcebrain.org, but this now has a username/password required for login (due to unsecure connection). Was that intentionally added @filippomc? I'm happy for now to still keep that site open for nonlogged in users (until there is a time cutoff: https://github.com/OpenSourceBrain/OSBv2/issues/599).
that deployment was updated unintentionally on netpyne release, rolling back
hi @pgleeson , the A looks fine to me but my understanding is that this won't be available for much longer. Then in that case I would say that we would need 'create a link to open application XXX with workspace YYY' where instead the part related to the file should be responsibility of the application itself rather than the OSB infrastructure, OSB should be able to pass that information down the line but I think @filippomc mentioned to me that something like that is already available in NWB explorer.
Hi, yeah I believe what we discussed is to have an option to go directly to netpyne-ui with a workspace, i.e. fully featured, since just the netpyne-ui without a permanent file system is not that useful.
I like filippo's suggestion of ´resuming the last netpyne workspace used by this user, and if none is available then creating a new one'. But just creating a new one would be ok if simpler. Also open to other suggestions.
As discussed at the last netpyne sprint call, OSB should support a straight access to the UI upon registration of the user, removing all the steps in the middle. This will then be used by netpyne.org/gui to provide a direct access point to the netpyne-ui