Changes between Version 82 and Version 83 of Procedures/NEODCDelivery

Timestamp:

Nov 20, 2013, 11:03:13 AM (10 years ago)

Author:

knpa

Comment:

--

Procedures/NEODCDelivery

@@ -6 +6 @@
   - A project is ready to be archived when all sensors have been delivered.
   - Check the ticket and make sure there is nothing on there which suggests something still needs to be done with the dataset (ask the processor if need be).
+ 1. Record in ticket that you are beginning to archive this flight.
  1. If there is a workspace version, move it into workspace/being_archived (pre-2011 only)
  1. Prepare the repository version for archiving: 
@@ -32 +33 @@
 find -user `whoami` -exec chmod a+rX {} \;
 }}}
- 1. Notify NEODC they can download the data (current contact is: wendy.garland@stfc.ac.uk) and record the date in the ticket. - CC Knpa
+ 1. Notify NEODC they can download the data (current contact is: wendy.garland@stfc.ac.uk. cc knpa).
+ 1. Record in the ticket that it has been submitted to NEODC and include the date.
  1. When NEODC confirm they have backed up the data:
-  1. Note in ticket that it has been backed up by NEODC and moved to archive disk.
+  1. Note in ticket that it has been backed up by NEODC.
   1. Change status page entry to "archived" for relevant sensors (if pre-2011 HS then only do this if both original and reprocessed HS have been archived).
- 1. Final steps - maybe wait a couple of months:
-   1. If workspace version present, delete from being_archived.
-   1. Close the ticket
+  1. If workspace version present, delete from being_archived.
+  1. Add the flight in the appropriate format and in the appropriate position in ~arsf/archived_flights.txt
+  1. If all sensors have been archived (including reprocessing) then close the ticket. Otherwise note why the ticket is being left open.