Changes between Initial Version and Version 1 of statusdatabase


Ignore:
Timestamp:
Mar 26, 2014 4:18:53 PM (5 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • statusdatabase

    v1 v1  
     1== Structure of ARSF database ==
     2
     3For furture maintenance.
     4
     5{{{
     6Indented sublevels mean the child has an "id" field matching the "value" field of the parent.
     7If items are on the same level without a separating space, it means they share the same id.
     8The flight_* items appear in separate groups, hence the abbreviation.
     9
     10------------
     11
     12piflight_pi_id
     13   pi_address
     14   pi_email
     15   pi_name
     16piflight_flight_id
     17   flight_area
     18   flight_data_location
     19   flight_date_received
     20   flight_jday
     21   flight_letter
     22   flight_notes
     23   flight_primary_ticket
     24   flight_year
     25   flight_kmlweblink
     26
     27progress_change_dataset_id
     28   dataset_del_check_time
     29   dataset_flight_id
     30      flight_*
     31   dataset_number_of_lines
     32   dataset_priority
     33   dataset_priority_offset
     34   dataset_processing_progress
     35   dataset_sensor_id
     36      sensor_name
     37      sensor_type
     38   dataset_time_to_complete
     39progress_change_date
     40progress_change_notes
     41progress_change_progress
     42progress_change_user
     43
     44projectflight_flight_id
     45   flight_*
     46projectflight_project_id
     47   project_code
     48   project_eufar_code
     49   project_objective
     50   project_priority
     51   project_summary
     52
     53secondary_ticket_flight_id
     54   flight_*
     55secondary_ticket_number
     56
     57-----------
     58
     59There is a 39th "kml_link" key but this only appears once, so I think it was replaced by flight_kmlweblink but not deleted.
     60
     61}}}