Changes between Initial Version and Version 1 of statusdatabase

Timestamp:

Mar 26, 2014, 4:18:53 PM (10 years ago)

Author:

knpa

Comment:

--

statusdatabase

@@ +1 @@
+== Structure of ARSF database ==
+
+For furture maintenance.
+
+{{{
+Indented sublevels mean the child has an "id" field matching the "value" field of the parent. 
+If items are on the same level without a separating space, it means they share the same id. 
+The flight_* items appear in separate groups, hence the abbreviation.
+
+------------
+
+piflight_pi_id
+   pi_address
+   pi_email
+   pi_name
+piflight_flight_id
+   flight_area
+   flight_data_location
+   flight_date_received
+   flight_jday
+   flight_letter
+   flight_notes
+   flight_primary_ticket
+   flight_year
+   flight_kmlweblink
+
+progress_change_dataset_id
+   dataset_del_check_time
+   dataset_flight_id
+      flight_*
+   dataset_number_of_lines
+   dataset_priority
+   dataset_priority_offset
+   dataset_processing_progress
+   dataset_sensor_id
+      sensor_name
+      sensor_type
+   dataset_time_to_complete
+progress_change_date
+progress_change_notes
+progress_change_progress
+progress_change_user
+
+projectflight_flight_id
+   flight_*
+projectflight_project_id
+   project_code
+   project_eufar_code
+   project_objective
+   project_priority
+   project_summary
+
+secondary_ticket_flight_id
+   flight_*
+secondary_ticket_number 
+
+-----------
+
+There is a 39th "kml_link" key but this only appears once, so I think it was replaced by flight_kmlweblink but not deleted. 
+
+}}}