Separate pre-linkage and post-linkage triggers #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This creates two trigger dags, one that runs clarivate tables/s2, then linkage, and another, triggered from linkage, that runs org er and metadata merge. I'll replace this with a better system when I start work on pipeline improvements in another month or two, but in the meantime this avoids the problem of the linkage task potentially timing out because it takes so long to run. Continued in https://github.com/georgetown-cset/cset_article_schema/pull/123