In general SatNOGS DB and SatNOGS Network are two different projects. They have different code repositories, they can run on its own and they serve different purposes.
SatNOGS DB serves the purpose of cataloging satellites/transmitters info and store data coming from any source in a specific format. One of these sources could be a network of ground stations.
SatNOGS DB project that LSF runs in db.satnogs.org gets data from from Telemetry Forwarder users/stations, gr-satellites users/stations, SatNOGS Network users/stations and from any other source that uploads data in SIDS format. So, that means that if SatNOGS network stops sending data, DB will still be functional and still will receive data, as it did 1 year ago when Network wasn’t able to send data to DB.
SatNOGS Network serves the purpose of ground station network management for observing satellites.
SatNOGS Network project that it is hosted from LSF in network.satnogs.org uses as source for satellites/transmitters data the SatNOGS DB, however it could use another source for these data if there was one.
So, there are relations between the two projects in the way LSF runs both of them, however keeping DB logging everything that’s out there, doesn’t mean that Network should follow to observe everything which is a discussion we have to do.
The discussion here is how we can change the DB in such a way that will expose the necessary info (about co-ordinations/regulations etc) for anyone interested (including Network).