Making Schema consistent with Topic names

[Vidushi-GitHub]

No description provided.

[Vidushi-GitHub]

Following nasa-gcn/gcn.nasa.gov#1539

[lpsinger]

@Vidushi-GitHub, would you please prepare a PR for the web site to update the naming conventions?

Also, should we change the names of the core schema to match?

[Vidushi-GitHub]

@Vidushi-GitHub, would you please prepare a PR for the web site to update the naming conventions?

Also, should we change the names of the core schema to match?

Changing the core-schema isn't necessary, we can keep basic/team ones as CamelCase. Whereas, producers ones as underscore, lowercase? The document only talk about naming convention for producers and can be modified.

[blaufuss]

This is fine with IceCube. We would need to make sure we change our production notices for the LVK followup notices to match the new schema name, but can make a coordinated change once this is ready to go into production.

The move of the Gold/Bronze stuff to test/ was on purpose? Once we get ready to produce these, we need to make a PR to move? Thanks

[Vidushi-GitHub]

The move of the Gold/Bronze stuff to test/ was on purpose? Once we get ready to produce these, we need to make a PR to move? Thanks

Although it's not in production, topic is already created as gcn.notices.icecube.test.gold_bronze_track_alerts and schema should have same structure. If you want please let's us know the modification in topic name for this one, that will be followed for schema name.

[blaufuss]

The move of the Gold/Bronze stuff to test/ was on purpose? Once we get ready to produce these, we need to make a PR to move? Thanks

Although it's not in production, topic is already created as gcn.notices.icecube.test.gold_bronze_track_alerts and schema should have same structure. If you want please let's us know the modification in topic name for this one, that will be followed for schema name.

I understand the renaming to match the topic name, this is fine. I also note the files here are moved to a ./test/ directory as part of this PR. That's an intentional move? It's fine if so, once we finish preparing it for production we can make a PR to move out of test...

[Vidushi-GitHub]

I understand the renaming to match the topic name, this is fine. I also note the files here are moved to a ./test/ directory as part of this PR. That's an intentional move? It's fine if so, once we finish preparing it for production we can make a PR to move out of test...

If you go to issue: nasa-gcn/gcn.nasa.gov#1539, gold/bronze has existing topic name as; gcn.notices.icecube.test.gold_bronze_track_alerts, which implies gcn/notices/icecube/test/ directory structure.
If topic name is fixed, the directory structure wouldn't have extra /test/.

[Vidushi-GitHub]

@Vidushi-GitHub, would you please prepare a PR for the web site to update the naming conventions?

Please see PR#1540 for web site update.