Overview

Currently (by Nov 21), we have the app implemented as a prototype; for the v1 release, we need to improve the codebase internally, add help messages, warn of some missing functionality etc. So we need to make the app look finished within the current scope.

Overview

Currently, all the metadata editors relies on an additional isUpdated flag also it might be replaced by shallow descriptions comparison (?)

Overview

TBD

Overview

It's quite common for good UIs to provide a step-by-step visual hints for the new users (add an example)

Overview

Instead of having a white screen we need to add buttons:

• Upload File
• Create Data Package
• etc

Overview

It's described here - #19

We need to apply it for other view components:

• Resource
• Dialect
• Schema
• Checklist
• Pipeline

Overview

Source code of component: src/components/Views/Package

Current State

Desired State

• name field
• title field
• description field for the long test (open modal / enlarge on clicking)
• homepage field
• image field (url)
• version field
• created field (date)
• resources editor (will be polished by @roll)
• keywords editor
• contributors editor
• sources editor
• licenses editor
• profiles editor (will be done by @roll)
• when we have focus on a filed a help text should be shown in the right panel (for example, when "description" is selected the help should be Package ("description" instead of "overview") with the help text from the standard
• the component accepts a height prop that allows moving buttons to the window bottom (when the component is used within the Application)
• the component is covered by basic unit tests in Jest
• rebased UI on vertical tabs

Implementation

This component is just a visual representation of the Data Package Standard - https://specs.frictionlessdata.io/data-package/. Please read this to understand better what we're trying to achieve.

Please start by implementing the simplest fields like image/version/etc

Currently, we have implemented the resources editor but we also want to have keywords/contributors/etc -- ping @roll to bootstrap these editors.

Overivew

• use a "Gear" icon at the top right corner
• on a click open a model with Config Editor (the same design as metadata editors)

Exact configurations and server implementation is TBD

Overview

We need to make sure that multi-component editors work together as expected

Overview

E.g. if a schema has many fields it conflicts with the action buttons visually (we need to have a scroll)

Overview

As the last step before v1 release, we need to set up a simple documentation unit, connect the app with the fd.io site, add tests and create issues as a future development plan.

PS.
Also, we need to decide the way we will be publishing the components library.

Overview

When a user selects a filed in Schema Editor we'd like to highlight by some color this column in the Table Editor

Overview

We need to support providing dialect/schema/etc by a path (according to the standards)

Overview

Currently, if a file changed outside of Open Data Editor it will bring the application into the inconsistent state. There should be a polling call to the server to listen for changes and update the state accordingly

Overview

After frictionlessdata/frictionless-py#820 is done we can add it to the app. Currently, the Inquiry component is a mess but it should be reasonably easy to add this check just taking as an example one of the existent (don't forget to update ICheck interface).

Overview

We need to play with the app trying opening different files and doing different actions (changing schema/pipeline/etc; reloading the file; clicking buttons). For every problem or group of problems, we need to create an issue which I'll triage for us to work on. We need to add a quick steps to reproduce and share server error messages if any.

Overview

Source code of the component: src/components/Editors/Files

Current State

Clicking on "Move" doesn't do anything

Desired State

• Client
  • when we click on Move a dialog window opens
  • the dialog window shows available directories to move file in
  • the dialog window provides a button to create a new dir
  • the dialog window has two buttons - move/cancel
  • move button is only available when a destination is chosen
  • after clicking on the move button in the dialog, the dialog is closed and the file is moved to a new directory
• Server
  • new endpoint project/move-file
  • new endpoint project/create-directory

Implementation

Note, that after adding new endpoints to the server you need to wrap them in the application/src/client.ts

Overview

It's quite a common Frictionless integration when Frictionless is inserted into a resource upload flow as in OpenSpending, Dryad, or ckanext-validation. We need to investigate if we can provide a really high-level component for it including an upload button, report renderer, and a metadata editor.

Overview

• support all possible data types from Table Schema
• support inline editing (with corresponding widget e.g. dates)
• TBD

Overview

Bootstrap everything, make it work, demo and release for internal feedback.

Overview

For Files editor we need 3 buttons on the actions panel:

• "+ New" (dropdown)
  • File Upload
  • Data Package
  • Folder (move here from the "Move" button logic)
• Move (already implemented)
• Delete (already Implemented)

Overview

Everything is implemented server-side but the client has to store a session id in LocalStorage

Overview

We need:

• app.frictionlessdata.io (Google Cloud / Docker)
• ui.frictionlessdata.io (instead of components?)
• metadata.frictionlessdata.io (instead of create.frictionlessdata.io)?

Also, we need to publish on NPM

Overview

Review if we still need it after the switch to vertical tabs

Overview

Currently, it's just an empty white rectangle

It will be better if it says "No resources" or something like this (under the tabs)

Overview

Initially, we implemented the app as an in-browser application but we also need to ship it as a standalone app using Electron as a wrapper.

After the integration, let's move frictionless.server to this codebase as it's highly coupled with the application

Overview

It's hard to consume when there are many files and errors. Also, we need to get a read of some not-needed styling like zigzag picture usage etc. Also, it will be good to migrate it to MUI

Overview

Currently, we can "Move" but no copy

PS.
Also, we need to ensure that move/copy works for both files and folders.

Overview

On a click it should to open a model window with 3 vertical tabs: CKAN, Zenodo, Github at the left and publishing settings (Control) at the right. The modal has to have 2 buttons: Cancel and Publish. When we click on Publish it should show an URL of a published dataset.

The button should be textual with a proper icon at the right top corner the same as for tables:

Plan

• Add error navigation
• Allow fixing error cells
• Support cell/error linking
• Sync cell error color with theme