-
Notifications
You must be signed in to change notification settings - Fork 0
Algorithmic logic
Jonathan Schaeffer edited this page May 17, 2024
·
4 revisions
First step is to scrap all information, without trying to logically link them together.
Get and store fdsn networks registry from https://www.fdsn.org/ws/networks/1/query
For each of the above networks with doi:
get and store datacite information from https://api.datacite.org/application/vnd.datacite.datacite+json/{doi}
Get and store fdsn datacenters registry from https://www.fdsn.org/ws/datacenters/1/query
For each of the above eida datacenters:
get and store StationXMLs of all networks from https://{datacenter_url}/fdsnws/station/1/query?level=network
Get and store eida routing registry from https://www.orfeus-eu.org/eidaws/routing/1/query?format=json
With all informations, we want to try to make links starting from FDSN registry, but also starting from a Datacenter or from the routing.
Each attempt to make logical bound will result in a new entry in the consistency_checks table. But we do not make checks at this stage.
For each fdsn network stored:
- find if it exists in routing registry (if it exists multiple times then get record for each of them and carry the tests for each of them)
by comparing network name and dates (routing dates shoud be inside the fdsn dates) fdsn_start < routing_end AND fdsn_end > routing_start
- try to link with StationXML networks
network names match AND routing_start <= stationxml_end AND routing_end >= stationxml_start
- check consistency of information.
- make a new record in consistency table
For each StationXML network which was not linked in the above step:
- find if it exists in routing registry the same way (if it exists multiple times then get each of them)
- check consistency of information.
- make a new record in consistency table
For each network in eida routing which was not linked before:
- check consistency of information.
- make a new record in consistency table