Missing functionality to be equal to classic app

[Heiss]

Classic app functionality needs to be replicated and implemented in RDS web:

• [x] research project management (tested)
  • [x] create new research project
  • [x] remove research project
  • [x] list research project
  • [x] view and configure research project (tested)
  • [x] list service configured in research project
  • [x] add service configured in research project
  • [x] remove service configured in research project
  • [x] select folder (e.g. via https://github.com/owncloud/file-picker), see https://github.com/Sciebo-RDS/RDS-Web/pull/6
  • [x] edit metadata
  • [x] integrate describo online in workflow
    • currently manual installation
  • [x] trigger publish & finish project
• [x] service management (tested)
  • [x] list all available services
  • [x] "add services to user" workflow (tested)
  • [x] oauth2 workflow
  • [x] credentials workflow
  • [x] remove services from user
  • [x] revoke access permission for RDS with one click
• [x] owncloud integration
  • [x] add vue to owncloud classic (add vuejs to existing project)
  • in path owncloud/classic
  • [x] settings page to specify frontend server url
  • [x] subpage for rds to load vue script which does not enforce login, because usage of requesttoken
  • [x] /informations endpoint with requesttoken
  • [x] add vue to OC web (workshop needed)
  • [x] RDS management
  • [ ] file context integration concept
  • [ ] classic
    • [x] connect to websocket in file context
    • [ ] trigger publish
    • [ ] create project for selected folder
  • [ ] web
    • [ ] connect to websocket in file context
    • [ ] trigger publish
    • [ ] create project for selected folder

[Heiss]

After the workshop with owncloud, we now know, that we should use "yarn workspaces" to create a separation between oc classic, web and standalone frontends. But this needs a refactoring of the components logic.

Steps:

1. we need to exchange the vuetify implementation against the oc design system
2. we need build scripts for oc web and oc classic, which places the resulting files in the correct folders
   • especially oc classic needs this, because it is a php app.
   • Idea: configure package.json to built to the root-folder of oc classic, because it should place img, css and js into the correct folder. (Assumption: It overwrites the files, not delete the folder first...)
   • The web and standalone app should be simple, because they are already an vue app and can depend on it via yarn workspaces.
3. the codebase for all 3 implementations needs to be frontend agnostic. Means:
   • no router, store etc. initialization, when runs in oc web,
   • otherwise init the plugins and the vue app to replace the div-container.

Another problem with oc classic: The local fonts cannot be loaded from php backend. :( External style files are not supported.

[Heiss]

The separation of codebases is now done. The integration was done via iframe.

[Heiss]

mostly done