You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user I want to reprocess notices that are in the backlog so that
547
547
they are published in Cellar and available to the public in RDF format.
548
548
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
553
550
have multiple notices in different statuses.
554
551
555
552
The backlog is divided in five categories as follows:
==== UC5.e: Deal with notices that couldn't be published
619
616
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.
621
618
622
619
[arabic]
623
620
. Enable the reprocess_unpublished_notices_from_backlog DAG
=== 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
0 commit comments