Organize Library Files & Folders 2.2.1 Download

Description:

Configuration Library Root Directory Dialog 1.1.1
Organize Library Files & Folders 2.2.1

This update version of the script addresses the bug created by the new ComicRack script installer function which was a cause of the previous version hard coding the script directory location.  The script directory location is now relatively coded.  I also included support Python scripts incase Python library paths in preferences aren't already set (this is to assist those users who aren't familiar with setting up/accessing Python libraries).  In addition I included a package configuration file for a cleaner looking setup.

Configuration Library Root Directory Dialog version 1.1.0 Update:
1) In subscript “ConfigLibRootDirectory11” I updated to address new location of script to local current user ComicRack scripts folder. This addresses running script in non Administrator mode.

Organize Library Files & Folders version 2.2.0 Update:
1) In main script “OrganizeLibraryFilesFolders22”  I updated to address new location of script to local current user ComicRack scripts folder. This addresses running script in non Administrator mode.


Looking for a script/tool that will allow you to spend less time organizing and more time doing the very thing that lead you to download ComicRack in the first place...reading!?!?  If your answer is yes, here it is! All you have to do is set the root folder where you want your nice new virtual bookshelf to be located on your hard drive and the script does the rest!  All selected ComicRack library entries will be auto organized quickly and smoothly.

Here is a complete breakdown of exactly how this script works. First there’s the File folder structure and naming. The user must manually set the root directory where they want their eComics to reside on the computer. The script then creates a new subfolder of the Publisher within the root folder, then an Imprint subfolder if it exists, and finally a Series subfolder. The Series subfolder also gets the beginning year it was published concatenated at the end. The syntax looks like this:
[root directoy] \ [Publisher] \ [Imprint ] \ [Series] ([YearBegan] Series) \
So for example if your eComic is The Amazing Spider-Man, Volume 1, Issue 366 or Air, Volume 1, Issue 8 your respective directories would be:
G: \ Comics \ Marvel Comics \ The Amazing Spider-Man (1963 Series) \
G: \ Comics \ DC Comics \ Vertigo \ Air (2009 Series) \

Then there is the file naming structure. The syntax for this is:
[Series] Vol. [Volume] # [Number with leading zeros] (of [Count ] ) ( [Month in text format] , [Year] )
So with the same eComics above as an example your files would be named:
The Amazing Spider-Man Vol. 1 #366 (September, 1992).cbz
Air Vol. 1 #08 (June, 2009).cbz

The code only creates an Imprint folder if the Imprint field contains a value. When naming the file, it adds the Count value after the Number value if the Count field contains a value. The script also checks for invalid characters in field values when making folder and file names. A text format is used for the Month value in the file name. So it would be May, June, July, etc. It also puts the seasons in text format if the Month value is between 13 and 16. So a value of 13 would be Spring and 16 would be Winter.

Also, very important – as of right now, you should run this script on at least each issue of a given Series, so that it names the Series folder properly. You could also run this script on your whole library, which would most definitely name each Series folder properly but this could take time to process depending on how large your eComic library is. A future update will ensure that this extra user step is not necessary.

The script includes the definitions directly into the Python script, so no need for a "XML" related file. I also added a icon file to display script icon in both the library level menu and the books selected level popup menu.

I've included full descriptions of what each piece of code is doing for those that wish to take a crack at learning this cool language to tweak and make their own scripts.

There is also a TEST copy of the script included that sends detailed outputs to the Script Output Window when you open ComicRack (ComicRack.exe -dso -ssc) in debug mode. Basically what I do is just add ( -dso -ssc) at the end of the Target field in Properties for my ComicRack shortcut icon.
Here is cYo's details on what this setup means:
http://comicrack.cyolito.com/index.php?option=com_content&task=view&id=28&Itemid=21

Hopefully saves you time so that you may devote more of it towards enjoying your books and this lovely app. Enjoy and take care!
oraclexview aka SoundWave

Submitted By:

Devin (oraclexview)

Submitted On:

19 Feb 2010

File Size:

43.80 Kb

License:

Absolutely Free... but please, if you enjoy this application and this script, do consider supporting ComicRack by donating. Every little helps!

File Version:

2.2.1

File Author:

Devin Cooper aka SoundWave

File HomePage:

Click to visit site

File Date:

19 Feb 2010

Rating:

Total Votes:1

Comments:

Spencer Hall 2010-05-22 01:18:19 This looks great, but I would have liked it to have been more "vocal" on what it was doing, since it ended up rearranging how I didn't want my files.

James Spaceman 2010-09-03 06:21:55 thanks, love this script (once i got used to it) works really good, thank you

Jeffery Sargent 2011-05-18 21:54:32 Organized and built folder structure. Check. Renamed with issue numbers and volume number. Check. Added "Annual" and "of 56" to ALL my comics within ComicRack, scraped or otherwise. Check. Tried to scrape new clearly named and numbered issues of a comic - they came in visible in Comic Rack WITHOUT their original comic numbers, but instead all issues were given issue 1.5 and "this is a sample" for title. I mean really - the actually name of the digital files were clearly "[series name] #1", "[series name] #2" etc - should have been an easy scrape. But your system changed them all to "Annual[series name] #1.5" EVERY ISSUE. And the original files were still named properly, but scrape wasn't taking any info from that - just the info your script had added. So basically, I'm going to have to uninstall the script, wipe my database, and hand scrape all this stuff all over again - most of it, one issue at a time.

jesse thompson 2011-12-15 19:39:34 This is awesome, I would just like to be able to configure the script to set my own folder structure. Otherwise, thanks a lot!