Create workflow to handle staging and public content publishing #1

See also https://support.d4science.org/issues/19566.
I am working on a dedicated branch

See also https://support.d4science.org/issues/19566. I am working on a dedicated branch

I have updated the repo-hi workflow and related templates as agreed in branch staging-public-wf. I have also re-organised workflow and templates in different directories. Old, unused workflows that can probably be deleted are in the 'old' folder. Workflows and templates inherited from parthenos have been deleted.
In the test folder named wf_migration I have added instructions for the manual migration of existing aggregation workflows, so that we do not need to remove them and re-aggregate and publish from scratch.

Specifically, the aggregation&publish workflow now includes:

collection
transformation
indexing on Solr for the Content Checker
feeding on staging GraphDB
The above run on cascade, one after the other. On GraphDB, the workflow stops, as we need to check the data and write the enrichment SPARQL queries. The following steps must therefore be run manually:
enrich staging GraphDB (+ manual check the enrichment succeeded)
publish on staging Elasticsearch

Finally, if the records look as expected in the portal, we will receive the green light from Julian, which means we can run the last workflow for public publishing.
It includes the following steps that are run automatically:

publish on public GraphDB
enrich public GraphDB
publish on public Elasticsearch

I have updated the repo-hi workflow and related templates as agreed in branch staging-public-wf. I have also re-organised workflow and templates in different directories. Old, unused workflows that can probably be deleted are in the 'old' folder. Workflows and templates inherited from parthenos have been deleted. In the test folder named wf_migration I have added instructions for the manual migration of existing aggregation workflows, so that we do not need to remove them and re-aggregate and publish from scratch. Specifically, the aggregation&publish workflow now includes: * collection * transformation * indexing on Solr for the Content Checker * feeding on staging GraphDB The above run on cascade, one after the other. On GraphDB, the workflow stops, as we need to check the data and write the enrichment SPARQL queries. The following steps must therefore be run manually: * enrich staging GraphDB (+ manual check the enrichment succeeded) * publish on staging Elasticsearch Finally, if the records look as expected in the portal, we will receive the green light from Julian, which means we can run the last workflow for public publishing. It includes the following steps that are run automatically: * publish on public GraphDB * enrich public GraphDB * publish on public Elasticsearch

Labels Milestones

Create workflow to handle staging and public content publishing #1