gCubeSystem
/
gcube-cms-suite
14
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Documentation

This commit is contained in:
Fabio Sinibaldi 2022-07-06 11:14:10 +02:00
parent 3d33e50164
commit d1e0e973b6
2 changed files with 24 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -10,9 +10,9 @@ Rationale :
Publication involves lots of common features as well as custom behaviour and formats. The service implements the basic common logic, delegating to installed plugin both cutom and configurable functions ranging from validation, data manifestazion, indexing and lifecycle management.
Lifecycle management is itself an extension allowing for both common and complex ad-hoc workflows.
High modularity of plugins allows for the composition of ad hoc use cases with maximized reusability.
High modularity of plugins allows for the composition of ad hoc use cases with maximized re-usability.
The suite comes with a set of pre-built plugins and GUIs that comunuties can easily extend and / or reuse.
The suite comes with a set of pre-built plugins and GUIs that communities can easily extend and / or reuse.
## Documentation

24
use-cases/src/site/sphinx/suite.rst
View File

@ -16,6 +16,26 @@ gCube CMS Suite is a distributed full stack application for publication manageme
The gCube CMS Suite is a gCube Application designed to manage the publication workflow of complex documents (i.e. comprising of multi-level extensible metadata, attachments.. ) called Projects.
It can manage the entire lifecycle of Projects, from their creation to access including :
GeoPortal key features are :
* Support for publication lifecycle
* By supporting complex Data (Meta + Payloads) archives known as ``:ref:`projects<_project>```;
* By enabling versioning, workflows, access policies;
* By supporting several manifestations (GIS, Databases, ...)
* By managing indexes (Meta catalogues, Index GIS layers)
* Maximise re-usability
* By exploiting space-time GeoPortal Service
* By allowing for configurable behaviour;
* By supporting a generic meta-model;
* By offering configurable GUIs (Management grid, Insert/Edit Form, Data Viewers);
* External Data Integration
* By exploiting OGC standards.
.. toctree::
:maxdepth: 2
- CRUD operations
- Role based access to Projects and lifecycle operations for moderation purposes
- Dataset Materialization (e.g. Image preview, SDI support)
@ -23,9 +43,9 @@ It can manage the entire lifecycle of Projects, from their creation to access in
- Dataset Processing (e.g. DataMiner)
- Customizable Insertion Forms, Navigation and Access GUIs
Every Project is associated to a Use Case Descriptor, which defines :
Every 'project'_ is associated to a Use Case Descriptor, which defines :
- Role based access and operation
- Project validation schema
- 'project'_ validation schema
- Involved plugins configuration (e.g. lifecycle type, materialization, GUIs)