I am afraid we are now mixing apples and oranges!
There are several "applications" and "databases"
terminology is differrent, but we need:
IARU Freq Coordination application and database. The IARU could use something to register and make frequency coordination easier that would contain contact details, Sat name, scheduled or actual launch date, Launch(/Service) provider, Type of Sat, Frequency/link details, Operational Status, Sat cat no, Sat object no, Request Status, Mission details etc etc
An application providing "Dcarr" functionality to the whole community, and database
An application providing a list of active satellites for the users and satellite frequencies, and database
An interface that allows direct interaction between the database(s) and applications
We are discussing this interface here
But we also need to think about these databases and their interaction.
Processing data, kiss files etc etc should be handled by the teams. But if its FUNcube format data, we have a warehouse. If its Delfi-C3 data, there is a warehouse. And so on...
Standardizing this only makes sense within AMSAT, and we have this solution at least for AMSAT-UK/NL
FUNcube technical team member