Skip to content

Last Updated: August 29, 2023

Database Layout

The Blueprints folder contains different API endpoints that interact with different MongoDB Collections behind the scene.

Blueprints and the collections they interact with

Blueprint MongoDB Collection(s) Note
acquisitions acquisitions, sources
admin user, authentication
analysis analysis, events
calibration calibrations name is different (plural)
candidates candidates, events, sources
catalog catalog
debug usernames
events events
hidden catalog
mimic injections, detections
outriggers active_outriggers, vlbi_data
services services, events
sources sources, candidates, events
verification usernames, verification, events, analysis name is singular
voe_subscribers voe_subscribers
voe voe

MongoDB Collections: indexes

Collection Indexes (unique index in bold)
acquisitions id (str)
active_outriggers outriggers_id (str)
analysis candidate_id (int), team, state
authentication user_id (str)
calibrations id (str), beam_number, date, source_name, location* (*GeoIndex)
candidates id (str) candidate_type
catalog version (int)
detections id (int), det_id
events id (int), datetime, event_type
injections id (str), active, injection_program
services id (str)
sources source_name (str), source_type
user name (str), team
usernames id (str)
verification id (int), datetime, delete
vlbi_calibrators name (str)
vlbi_data id (int)
voe id (int)
voe_subscribers email_address (str)