This area will explain and document the database schema, and explain the choices made during the design.

Schema Diagram:



Tables:

Table NameDescription
accountStores Request Handler user account information.
account_roleConnects account table to role table fro the request handler.
archive_logUnused request Handler table for tracking downloads; not populated
authors A listing of the authors of projects.
calibration_status_valuesA listing of the allowed values for the calibration_status field of the execution_blocks table.
calibration_tablesnot yet fully defined; will be used to store metadata about calibration tables.
configurationsThe connecting table between data descriptions and execution blocks.
data_descriptionsA listing of the frequency, bandwidth, and polarizations used in each execution block.
databasechangelog
databasechangeloglock
datadescAn artifact of the import process.  Not used after import is complete.
eventsA record of AAT/PPI events sent. 
execblock_start_stop
execution_blocksThe highest level of science data for an observation.  contains one or more scans.
filegroupsForms an arbitrary-level hierarchical structure between projects and files.
filesThe file-specific data for an NGAS entity.  Belongs to a filegroup.
flatfilesAn artifact of the import process.  Not used after import is complete.
image_productsholds information shared among images which were created & ingested together.
imagesholds metadata about images stored in the archive.
intentsa list of the intent_names that can be used in subscan_intents.  currently empty and unused.
log_sequenceused for generating request handler request IDs
logsA record of log messages generated by the AAT/PPI system.
new_vlba_dataAn artifact of the import process.  Not used after import is complete.
polarizationsA listing of the base polarizations.
projectsproject-level data for images and observations. Contains filegroups and execution_blocks
receiversCurrently unused.
reingestion_queueTracking table for keeping the AAT/PPI system up to date with ALMA observations. 
reingestion_statesComplete list of states for reingestion of ALMA data into the AAT/PPI structure
rh_commandsLookup table containing types of commands issued for user-initiated AAT/PPI requests (i.e., those that come through the new archive UI)
rh_data_entitiesStores data entities (files or collections of files) associated with a Request Handler request.
rh_filesTracks files associated with a given Request Handler request.
rh_operator_requestsRequest Handler table for tracking requests made by operators (rather than end users). Unpopulated in new archive presently.
rh_processesTracks processes associated with a Request Handler request.
rh_request_parametersStores multiple key-value pairs associated with each Request Handler request. Each time the state of a request is updated, parameter values are inserted or update.
rh_requestsTracks user download requests coming from the new archive UI
rh_requests_mediumsUnused Request Handler table, meant presumably to record the delivery medium for a request.
rh_site_delivery_mediumUnused Request Handler table, meant presumably to track details of delivery media.
roleLookup table for request handler roles, referenced by account_role.
scansthe middle level of science data for an observation.  Belongs to an execution_block, and contains one or more subscans.
subscan_data_descriptionsDeprecated
subscan_intents
subscansThe lowest level of science data.  belongs to a scan, and points to a file.
total_file_sizes
workflow_input_filesthe files taken as input by a workflow entry.
workflow_parametersa set of name-value pairs listing the arguments for a workflow entry.
workflowsa listing of each processing job that takes in data from the archive and produces data that is stored in the archive.

       

  • No labels