Changes between Version 2 and Version 3 of Procedures/NewDataArrival

Timestamp:

Jun 28, 2007, 12:13:05 PM (17 years ago)

Author:

mggr

Comment:

--

Procedures/NewDataArrival

@@ -3 +3 @@
 This procedure should be followed on receipt of new flight data from ARSF.
 
-1. copy to appropriate location on the filesystem (~arsf/arsf_data/2007/flight_data/...)
-  1. ensure the directory name conforms to the standard - PROJECTCODE-YYYY_JJJxx, e.g. ''GB2007_05-2007_116b'', ''boresight-2007_198'', etc
-  1. rename any capitalised subdirectories
-  1. prune empty directories? (''need to think about this, maybe only do after checking it's not a stub for later data'')
-1. raise a trac ticket (type 'flight processing') for the new data
+ 1. copy to appropriate location on the filesystem (~arsf/arsf_data/2007/flight_data/...)
+   * ensure the directory name conforms to the standard - PROJECTCODE-YYYY_JJJxx, e.g. ''GB2007_05-2007_116b'', ''boresight-2007_198'', etc
+   * rename any capitalised subdirectories
+   * prune empty directories? (''need to think about this, maybe only do after checking it's not a stub for later data'')
+ 1. raise a trac ticket (type 'flight processing') for the new data
 
 = Other data types =