storm-platform / storm-workflow Goto Github PK

The invenio API that fixes some of the bugs faced in Storm Workflow has had minor changes. This is causing errors when running the Workflow module.

In the ResearchPipelineService._transform_compendium, the permission policy is not applied! It is required the definition of the used record in the function call

In the pipeline document, returned by the Storm Pipeline, we must add a Actions section with the URL to add/remove compendium in the pipeline.

Use storm-graph for creating and managing metadata graphs.

The graph field must be read-only for the users updating the pipeline. Currently, it is required and users can use it to change the pipeline without using specific and safe methods (Add pipeline action and Delete pipeline action)

Use storm-core to control and manage the project graphs.

The links returned by these components redirect the users to an invalid address. See an example below:

GET http://127.0.0.1:5000/api/projects/<MY-PROJECT-HERE>/pipelines

{
  "metadata": {
    "title": "Research pipeline",
    "description": "Basic description",
    "version": "v1.0.0"
  },
  "links": {
    "self": "http://127.0.0.1:5000/api/records/<MY-PROJECT-HERE>"
  },
  "created": "2021-12-16T22:34:29.665373+00:00",
  "id": "<MY-PROJECT-HERE>",
  "revision_id": 1,
  "updated": "2021-12-16T22:34:29.673937+00:00",
  "graph": {}
}

Based on zenodo implementation of the communities, we can link the storm entities using an extra field into the metadata.access field.

For adding new compendia to a pipeline, we must have a rule that validates that the pipeline is not finished.