Skip to content

Create documentation mapping full Dataset publishing lifecycle #89

@maxsibilla

Description

@maxsibilla

We want to document the full process to convert a "new" Dataset to the status of "published"

We want to note 2 key things:

  1. In the portal, what buttons should be present depending upon the various statuses the Dataset could be in when editing it
  2. Which endpoints should be hit from the portal to facilitate status updates/launching pipeline processing

Currently we support modifying the status from "new" to "processing" via a submit button in the portal, then the process gets set to "qa" or "error" once the pipeline process finishes. We have no UI element to change the status from "qa" to "published" or to revert a published dataset back to a state which can be edited (revisions).

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions