oSPARC: S4L-Lite

[odeimaiz]

• Landing-page: update company name
• Add Licensing to cookie disclaimer
• Feedback by email and Link to forum
• Studies/Projects Templates/Tutorials organization
• 2FA, improve UX
• Edit study name from Navigation Bar
• Download logs from NavBar
• Dashboard button with home icon
• Information button in Navigation Bar with study-service merged info
• Quick start guide
• Advanced e2e for s4l-lite
• Create Account button: Pops up link to Z43 registration form
• Version Number in service information popup should be displayed more prominent
• Make sharing features more prominent
• Product-specific everyone organization
• Dashboard related documentation in ZMT github
• ? References to the osparc software (such as in 'about'): Wording shall be changed.

Requires backend/devops

• Refactor product related data @pcrespov
• Move tags ownership to groups @pcrespov
• Restrict users to open only one study @sanderegg
• Edit Templates #777
• ? New license server: ideally, we use env vars on the platform for this @GitHK @mguidon, see also this
• 2FA @pcrespov
  • Resend code -> ✨ Is3318/resend 2fh handler (⚠️ devops)  osparc-simcore#3658
  • Provide an alternative solution -> ✨ Is3318/resend 2fh handler (⚠️ devops)  osparc-simcore#3658
  • 2FA env-var needs to go in the Data Base -> ✨ Products: Is765/2fa settings per product (⚠️ 🗃️ devops) osparc-simcore#3673
• Include s4l-lite registered users in product-specific everyone organization
• How to generate invitations? Creation of invitations osparc-simcore#3683 @pcrespov
• Add how to get an invitation link to vendor info in DB. S4L-Lite should point to the zmt website form. @pcrespov
• Maintenance: Use the new messaging system to announce scheduled downtimes
  • ✨ Maintenance scheduler osparc-simcore#3768 @odeimaiz
  • Broadcast notifications to front-end osparc-simcore#1828 @pcrespov @sanderegg
• Timeout after a few idle hours/minutes: S4L state is auto(saved) after X minutes of idling in a temporary file. Then there is 5 Minute warning popup. Then it closes automatically @odeimaiz ✨ Idle timer: close study after 30' osparc-simcore#3544
• Service startup: show progress @sanderegg @GitHK (or change the wording) NK says we need to make the startup of s4l-light faster. The progress bar needs to be more verbose and nicer. It should 'flood' the user with more information about the state so it seems like the webpage is "responsive"
• Make sure invitation (oetikers) is sent email from zmt.swiss
• For JupyterNotebooks, they currently open in a second tab with the current UUID-based domain-name-based traefik routing approach. We need to audit if this is viable from a security / scalability point-of-view. From a security point of view, maybe start creating auth. token. @GitHK

[mrnicegyu11]

Must-Have

• Trial Accounts are not needed
• @odeimaiz Talk to Anja and NK about logos and branding
• Frontend: On landing-page: Remove osparc-simcore mentions and change itisfoundation to ZMT
• Frontend: Add cookie disclaimer to landing page
• Frontend: Add a link to S4L Forum page to GUI
• Timeout without logout or study-closure (discuss this with s4l team) after idling for a few hours
• Use the new messaging system to announce scheduled downtimes
• 2FA is set up
• NK says we need to make the startup of s4l-light faster. The progress bar needs to be more verbose and nicer. It should 'flood' the user with more information about the state so it seems like the webpage is "responsive"
• Distinguishable pictures (thumbnails) for the tutorials are needed.
• A "first usage" Tutorial or Movie like in tip.itis.swiss is needed
• We restrict s4l-web-light-product users to open only one study. This should be handled by the oSparc backend.
• The Issues/Feedback Button will trigger a email popup to sim4life support (possibly including user_id, project_uuid, ... at our discretion)

To be discussed / decided

• NK: "We shall disable accounts after half a year of users not using them" --> What does this mean technically, when is an account considered unused? Will we disable them manually from time to time or have a (semi)automatic procedure?
• Where should the documentation live? --> The manual will likely live in github... Erdem will talk with @mguidon about this separately
• Question by EO: Is the 'one-project == one-file' agreed upon? --> It is not yet clear, there are various pros/cons. This needs to be decided
• For s4l-web-light JupyterNotebooks, they currently open in a second tab with the current UUID-based domain-name-based traefik routing approach. We need to audit if this is viable from a security / scalability point-of-view. A possible blocker could be is s4l-light lives under a zmt.swiss subdomain, such as s4l.zmt.swiss/light.

Not fully committed to these features yet:

• Registration via a zmt.swiss form, possibly automated sign-up link generation via black/white list?