Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add EP trigger id #160

Merged
merged 1 commit into from
Jul 18, 2024
Merged

Add EP trigger id #160

merged 1 commit into from
Jul 18, 2024

Conversation

modot
Copy link
Contributor

@modot modot commented Jul 9, 2024

Description

As discussed in previous PR #155 and #159 ,

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.

we prefer to use trigger id as the unique identifier. This PR add id property to EP Notice schema and example file.

@jracusin jracusin requested a review from Vidushi-GitHub July 15, 2024 15:11
@Vidushi-GitHub Vidushi-GitHub mentioned this pull request Jul 15, 2024
@@ -2,6 +2,7 @@
"$schema": "https://gcn.nasa.gov/schema/main/gcn/notices/einstein_probe/wxt/alert.schema.json",
"instrument": "WXT",
"trigger_time": "2024-03-01T21:46:05.13Z",
"id": ["01708973486"],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @modot, thanks. Would EP Team keep ingesting the ID no. in Circulars as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, absolutely. We are ready to start including the ID for both Notices and Circulars. If I understand correctly, are we good to proceed with the new format now?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, looks good.

@Vidushi-GitHub Vidushi-GitHub merged commit e83c64c into nasa-gcn:main Jul 18, 2024
1 of 2 checks passed
@Vidushi-GitHub
Copy link
Member

close: #159

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants