Fermi-GBM JSON Notices

[jracusin]

Description

GBM new public JSON notices.

Acceptance criteria

• create topics/acls
• JSON schema
• mission page updates
• add to Quickstart
• announcement

[dakota002]

Schema PR: nasa-gcn/gcn-schema#199

[shb46]

@jracusin: No changes to be made to the Fermi mission page.

[dakota002]

Quickstart update (behind feature flag) #2631

@shb46 are there more topics, or a more specific topic, that you would like listed? This PR will add gcn.notices.fermi.gbm to the list under the JSON option

[shb46]

@dakota002: Our idea was each notice to have its own topic to enable subscription to individual types. Let me know if it is a problem. So the topic would be gcn.notices.fermi.gbm.alert .

[dakota002]

@dakota002: Our idea was each notice to have its own topic to enable subscription to individual types. Let me know if it is a problem. So the topic would be gcn.notices.fermi.gbm.alert .

Not a problem at all! Are there more than gcn.notices.fermi.gbm.alert that you would like added to the list?

[shb46]

@dakota002: GBM produces 5 public notice types and a few internal ones. Besides the alert The public ones are "flight position", "ground position", "final position" and "subthreshold". If you want to be consistent, these can be abbreviated as they appear in the email subscription page.

[dakota002]

@shb46 are those going to all be distributed under the same topic with some flag denoting the difference, or each as individual topics, (ie. gcn.notices.fermi.gbm.flight_position, gcn.notices.fermi.gbm.ground_position, gcn.notices.fermi.gbm.final_position, etc)

[shb46]

@dakota002: Individual topics.

[jracusin]

These should be all the same topic, with an enum that indicates the position is "flight", "ground", "final" etc.

[shb46]

@dakota002: Please see Judy's post above. Sorry about the misunderstanding. I didn't know this is how you want it.