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.
Description
Following the Zendesk ticket #210 (https://nasa-gcn.zendesk.com/agent/tickets/210):
The same event is being notified through both Notices and Circulars. However, they don't contain a common unique ID and have slightly different times and localization (as Circulars are more refined).
It is necessary to include a property such as the event name or trigger ID as a unique ID, which should be the same across both Notices and Circulars.
One potential option is the event name, which is currently reported in EP Circulars, and request to add it to the Notices pipeline.
@modot, please check what's more convenient at your end, either include the trigger ID or event name in the EP Notices.