Open ianwallen opened 3 years ago
Related, delegate state of the metadata record to the external BPMN tool:
Note all these systems require geonetwork to store a magic "id" of some sort, used to query the external system for current state.
Re-open enhancement
The external app link helped link to external apps but it does not enhance the approval process for metadata workflow.
This is great, and should be added to the documentation! Out of interest, how easy would it be to add {title} as a parameter? You could then have a tool to search in other catalogs (or google etc) for metadata with the same title
Is your feature request related to a problem? Please describe. In the current workflow process a user has to fill out the full metadata record before being able to submit an approval request. In our environment, users don't have all the knowledge to fill out the full metadata records.
It is currently not possible to apply a consistent process in the application. And this leads to the user doing all these task manually and it is difficult to enforce everyone to follow the same procedure.
Describe the solution you'd like What is being proposed is the ability to add a link to an external BPMN application that could take care of these workflow request.
If it is desired to have the same users exists across the external tool and geonetwork then I would recommend using keycloak/SSO configuration. Otherwise, we could add a "{email}" as another parameter so that the external tool could prompt for authentication. Adding extra parameters would not be difficult.
As for the external tool, in our case we would be using a BPMN workflow application such as activiti/camunda to handle the request ensuring a consistent workflow for all the request identified above.
Describe alternatives you've considered
Additional context I believe being able to link Geonetwork to external BPMN workflow application could help enhance the functionality. Other potential usage include the publishing approval process - current Geonetwork approval process is simple - reviewer approves of rejects the record. But in some cases it can be complex requiring approvals from multiple parties i.e. translation need to approve translation, gis team needs to approve gis data, content reviewer provide general review. Attempting to put this logic into the Geonetwork software would be too complexe but allowing this to be handled by an external BPMN software seems to make more sense.
Looking for some feedback. If approved, I can begin work on applying the new enhancements.