Changes between Version 8 and Version 9 of Processing/proj_tidy

Timestamp:

Oct 9, 2014, 3:57:05 PM (10 years ago)

Author:

knpa

Comment:

--

Processing/proj_tidy

@@ -26 +26 @@
 Fixing permissions takes time too, and this is done nightly on a cron, so I also moved this to it's own option '-m'.
 
-It decides if directories are missing or not using using folder_structure module that anch originally wrote. This maintains the project structure (somewhere) in a central place, so in theory we only need to update one place when we change structure (e.g. move folders around). Note you'll still have to update proj_tidy's regex file, as files will now be in a different place.
+It decides if directories are missing or not using using folder_structure module that anch originally wrote. This maintains the project structure (somewhere) in a central place, so in theory we only need to update one place when we change structure (e.g. move folders around). Note you'll still have to update proj_tidy's regex file, as files will now be in a different place. For missing directories it will generate a 'mkdir' command, which will appear in "Suggested Commands" at the very bottom (but before the suggested commands that deal with moving, generated below).
 
 It makes a list of all files in the flight, filters out any expected ones using the regex file, and prints the rest as "unrecognised files".
+
+At the very end, it prints suggested commands, which are intended to be checked then copy and pasted. These are the ones that are used when unpacking, which convert the project to the current format. The module that generates the mv commands is one of the most complex and is located under ~arsf/usr/bin/proj_tidy/move_commands.sh. This has to be kept manually updated to match the structure that ops supply to us. It's broken down into one section for each specific directory and is in the form: Check if directory exists -> Check if directory has contents -> Move contents to correct place -> rmdir the directory. It's best start from the lowest level and move upwards (e.g. do leica/ipas/raw/ then leica/ipas/ then leica/) so you're not moving anything you then want to deal with further down the script. It also does some other more complicated things to do with azgcorr style stuff - this was important when converting the projects from the pre-2011 style to the current style and making sure old and new things were kept separated, but is less important now.[[BR]]
+It actually looks more complicated than it is because I set it up so you could either execute the commands or just print them. In the end it was decided it was safer just to print them, so proj_tidy doesn't call this module with the 'ex' argument that is necessary to execute them.