Changes between Version 116 and Version 117 of Procedures/NEODCDelivery


Ignore:
Timestamp:
Nov 20, 2018 8:50:45 AM (8 months ago)
Author:
dac
Comment:

NEODC -> CEDA

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NEODCDelivery

    v116 v117  
    1 = Archiving projects with NEODC =
     1= Archiving projects with CEDA =
    22
    33=== Creating JSON files ===
     
    3939
    4040=== Archiving ===
    41 This page documents the procedure to follow when sending data to NEODC.
     41This page documents the procedure to follow when sending data to CEDA.
    4242
    4343 1. Choose a project:
     
    7979    1. Delete the broken symlinks and run make_kmloverview.py
    8080    1. Check the links in the processing/kml_oveview folders or use the link on the wiki to open the google earth KML file and check the download links work and that there is data under each of the tabs
    81  1. Upload the data to NEODC using neodc-archive.py. This will upload the data using rsync (see http://www.ceda.ac.uk/help/archiving-with-ceda/sending-data-to-ceda/ for more details on archiving data at NEODC using rsync). If you are not running as airborne and haven't set up a password file you will need to enter your password (listed on the [https://rsg.pml.ac.uk/intranet/trac/wiki/Projects/ARSF-DAN/Passwords Passwords] page).
     81 1. Upload the data to CEDA using ceda-archive.py. This will upload the data using rsync (see http://www.ceda.ac.uk/help/archiving-with-ceda/sending-data-to-ceda/ for more details on archiving data at CEDA using rsync). If you are not running as airborne and haven't set up a password file you will need to enter your password (listed on the [https://rsg.pml.ac.uk/intranet/trac/wiki/Projects/ARSF-DAN/Passwords Passwords] page).
    8282{{{
    8383ceda-archive.py --year 2012 --jday 324 --sortie c --rsync
     
    8787{{{
    8888lftp arsfdan@arrivals.ceda.ac.uk
    89 > mirror -R -L /tmp/neodc_fEYiiE/ET12_14-2012_324_Boset_raw
     89> mirror -R -L /tmp/ceda_fEYiiE/ET12_14-2012_324_Boset_raw
    9090}}}
    91  1. Notify NEODC the data has been uploaded (current contact is: wendy.garland@stfc.ac.uk. cc arsfinternal).
    92  1. Record in the ticket that it has been uploaded to NEODC and include the date.
    93  1. When NEODC confirm they have backed up the data:
    94   1. Note in ticket that it has been backed up by NEODC.
     91 1. Notify CEDA the data has been uploaded (current contact is: wendy.garland@stfc.ac.uk. cc arsfinternal).
     92 1. Record in the ticket that it has been uploaded to CEDA and include the date.
     93 1. When CEDA confirm they have backed up the data:
     94  1. Note in ticket that it has been backed up by CEDA.
    9595  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).
    9696  1. If workspace version present, delete from being_archived.
    9797  1. Add the flight in the appropriate format and in the appropriate position in ~arsf/archived_flights.txt. This is version controlled in ~arsf/live_git_repos/config_files so needs to be committed after being changed (there is no remote copy so no need to push).
    9898  1. If all sensors have been archived (including reprocessing) then close the ticket. Otherwise note why the ticket is being left open.
    99  1. Note, if you don't get a conformation email from NEODC you can check projects which are out of embargo by seeing if the raw and processed data are available from http://browse.ceda.ac.uk/browse/neodc/arsf. Use the same username and password as for the CEDA FTP.
     99 1. Note, if you don't get a conformation email from CEDA you can check projects which are out of embargo by seeing if the raw and processed data are available from http://browse.ceda.ac.uk/browse/neodc/arsf. Use the same username and password as for the CEDA FTP.