next up previous contents
Next: Table schemas and SQL Up: Database representation of JSOC Previous: Global tables   Contents

Series specific tables

The two tables hmi_fd_v and hmi_fd_v_seq in Figure 3 illustrate what the main record table and the sequence counter table for the series "hmi_fd_v" might look like:

Figure 3: Illustration of the structure of the series specific tables for the series hmi_fd_v. The main record table is named hmi_fd_v and the record number sequence counter table is named hmi_fd_v_seq.
\begin{figure}\par
\centerline{\epsfig{figure=class_tables.eps,width=4in}}\end{figure}

Each row in the table hmi_fd_v represent a data record from the series hmi_fd_v. The first two columns contain record number (ID) and version which together with the series name uniquely identifies the record within the JSOC environment. The values of simple keywords (T_Obs and D_Mean in the example) are stored in the table along with record number (ID) and version of objects pointed to by links. For example, the second row in the table represents data record (hmi_fd_v, 1, 1) which contains a link called L1 pointing the record (hmi_fg, 2341, 1) from the hmi_fg series. For this record the query link named Orbit has been resolved to point to the record (sdo_fds, 7, 1) from the series sd0_fds.

Finally, the "hmi_fd_V" table contains for each record a pointer to the storage unit in which the contents of the data segments of the record is stored. This pointer (here called "DSIndex") is an index into a database table maintained by the SUMS sub-system. DSIndex can be resolved by the SUMS to a path of a directory containing the data files of the data segments.


next up previous contents
Next: Table schemas and SQL Up: Database representation of JSOC Previous: Global tables   Contents
Philip Scherrer 2006-06-17