Changes between Version 115 and Version 116 of Procedures/NewDataArrival


Ignore:
Timestamp:
Sep 29, 2010, 11:50:52 AM (14 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Procedures/NewDataArrival

    v115 v116  
    1919== Move to permanent PML data storage ==
    2020
    21 Check there is space in the repository for the project (`du -hs ~arsf/arsf_data/YYYY/flight_data` and `du -hs location_of_project_to_unpack`). If not then skip this bit and copy to the workspace instead, but put a comment in the ticket so we can rsync it to the repository later.
     21Move to appropriate location in the repository (~arsf/arsf_data/2009/flight_data/...)
     22 * ensure the project directory names conform to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB07_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc
    2223
    23 Move to appropriate location on the filesystem (~arsf/arsf_data/2009/flight_data/...)
    24  * ensure the project directory names conform to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB07_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc
     24** IMPORTANT **
     25
     26If there is no space in the repository then it will need to go into archive-over-flow temporarily (~arsf/arsf_data/YYYY/flight_data/archive-overflow). Make a note in ticket saying that this project is in non-backed up space.
    2527
    2628The next stage can be manual or semi-automatic: