Skip to content

Commit e44369d

Browse files
committed
documented the RE-transformation of published notices pipeline
1 parent e428b1b commit e44369d

2 files changed

Lines changed: 19 additions & 5 deletions

File tree

35.1 KB
Loading

docs/antora/modules/ROOT/pages/user_manual/workflow-management-airflow.adoc

Lines changed: 19 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -546,10 +546,7 @@ image:user_manual/media/image49.png[image,width=100%,height=357]
546546
As a user I want to reprocess notices that are in the backlog so that
547547
they are published in Cellar and available to the public in RDF format.
548548

549-
Notices that have failed running a complete and successful
550-
notice_processing_pipeline run will be added to the backlog by using
551-
different statuses that will be added to these notices. The status of a
552-
notice will be automatically determined by the system. The backlog could
549+
Notices that have failed running a complete and successful notice_processing_pipeline run will be added to the backlog by using different statuses that will be added to these notices. The status of a notice will be automatically determined by the system. The backlog could
553550
have multiple notices in different statuses.
554551

555552
The backlog is divided in five categories as follows:
@@ -617,7 +614,7 @@ image:user_manual/media/image71.png[image,width=100%,height=49]
617614

618615
==== UC5.e: Deal with notices that couldn't be published
619616

620-
In the case that the backlog contains notices that couldn’t be published at some point and will want to try to reprocess those notices just run the *reprocess_unpublished_notices_from_backlog* DAG following the instructions below.
617+
In the case that the backlog contains notices that couldn’t be published at some point and will want to try to reprocess those notices just run the *reprocess_unpublished_notices_from_backlog* DAG following the instructions below.
621618

622619
[arabic]
623620
. Enable the reprocess_unpublished_notices_from_backlog DAG
@@ -629,6 +626,23 @@ image:user_manual/media/image38.png[image,width=100%,height=38]
629626

630627
image:user_manual/media/image19.png[image,width=100%,height=57]
631628

629+
=== UC6: How to re-transform notices that have been successfully published and publicly available ?
630+
631+
As a user I want to re-transform notices that have been successfully published and publicly available so that new versions of the RDF notices are published in Cellar and available to the public in RDF format.
632+
633+
This use cases is appropriate only when a new version of the Mapping suite has been loaded into the TED-SWS system. Otherwise, the output of the re-transformation will be the same as before.
634+
635+
636+
[arabic]
637+
. Enable the *reprocess_published_in_cellar_notices* DAG
638+
639+
image:user_manual/media/image109.png[image,width=100%,height=38]
640+
641+
[arabic, start=2]
642+
. Trigger DAG
643+
644+
image:user_manual/media/image19.png[image,width=100%,height=57]
645+
632646
== Scheduled pipelines
633647

634648
Scheduled pipelines are DAGs that are set to run periodically at fixed

0 commit comments

Comments
 (0)