storm-platform / storm-project Goto Github PK

There are functionalities and utilities that are repeating themselves in the API modules.

Should we generalize these functions and create a storm-base library, with specific functionality for services ?

Rename package to storm-project

AccessSchema is defined with generated_by, but in the jsonschema, this field is named to contributed_by.

Permissions Generators is doing checks at the record level, leaving out project information.

We need to find a way to fix this problem. With this, even those outside the project can access the resource as long as they have a valid ID.

• ProjectOwner generator;
• ProjectColaborator generator.

A project should not be removed! This could cause problems for its history. Users can only finish the project.

Improve the records metadata (Draft and Records). The metadata should contain a general description of the context of its creation, which includes:

• creator;
• date;
• version used.

In the currently implementation of the ProjectRecordUser, the needs method return [] when record is None. I think we should generalize this and only return the needs of the project.

Change __tablename__ to project_projects.

• Move the following init_config options to the storm-ws:

  • JSONSCHEMAS_*;
  • RECORDS_*.

• Include invenio mappings and jsonschemas

• Record link model;
• Record link model (Pagination).

The users can't list the records when the record don't have parent (for the UserInProject and ProjectRecordColaborator generators)

In the project document, we have the is_finished field. When this field is true, the update operations should be disabled (Enabled only for the super-user, for administrative operations).

Should we use a standardized licensing vocabulary ?

To make the shipment easy, we need to define a common fields in the project metadata.

In addition to the fields already added, I think the following fields should be added:

• Creators;
• Contributors;
• Spatial extent;
• Temporal extent;
• Version.