Orkestrator (Next)

This repository includes the Next version of Orkestrator frontend for the arkitekt platform. It is currently under development and not ready for production. If you are looking for the current version of Orkestrator, you can find it here.

Roadmap

Before the new version of Orkestrator can be merged into the main repository, the following features need to be implemented:

General Next Features

• Build around arkitekt-ts (instead of custom graphql clients)
• Move Basic UI to Shadcn/UI
• Move to Vite
• Move to React 18
• Move to new GraphQL Protocols (subscriptions based on graphql-ws, standardized error and param handling (pagination(filter))
• Basic UI Testing
• User Stories (e.g. documentation for specific user stories)
• Documentation, Documentation, Documentation
• Move to React Query (suggested)
• Move to React TanStack Router (suggested)
• Move to Tauri 2.0 when it is released (suggested)
• Lazy Load Modules (only if corresponding service in Deployment)
• Hosted Deployment (e.g. on Vercel)

Service Specific Next Features

Lok

• User Management
• Advanced App and Config Management (around Fakts)

Mikro

• Move to Mikro Next
• Establish "Views" as central concept
• Deprecated OMERO metadata support

Fluss

• Establish new Workflow UI + Engine (typesafe, wizard, ...) (looks nice)
• Move to Fluss Next
• More tighlty integrate Schedulers in UI
• Allow Resource Management in UI ( provisional UI for resource management)

Rekuest

• Move to Rekuest Next
• Build UI for scheduled tasks, and task management
• Hookify Rekuest (useNode, useTemplate, ...)

Kabinet

• Establish Kabinet
• Create App Store like Feature
• Create App Store UI

Omero-Ark

• Improve Omero UI
• Allow metadata editing in UI

Port

• Build deprecated Port UI (Port will be replaced by Kabinet)

Kluster

• Build Kluster UI
• Elaborate on Dask-Cluster integration
• Provide support for other cluster