WinDupe NFO Filename Add Utility
Version 1.0
Katman

PLEASE READ THIS IN ITS ENTIRETY.
(if you are one of those that don't like to read, then let this
 be one of the few things you do read.  However, if you MUST not
 read this, then start where it says --NOTE-- down below)

I suggest that all Release Packer's use this.  The Note section
explains why.

---------------
--Explanation--
---------------

If you use WinDupe then you know that it has an extensive database of
NFO data.  I try to keep this database up-to-date and complete with
all the NFO information from every release, but this gets tedious.

NFO collection is not easy.  A method tried early on was to just take
the largest of the .nfo files, and assume that was the release group's
nfo file.  This didn't work as some courier group, and even some site
nfo's are sometimes larger than the actual release nfo.  Another 
alternative was to go by the release's directory name (ie -SHOCK, 
-RAZOR, etc..), this too does not work because of a few situations.

The final alternative was to keep a database of release group nfo
filenames.  The way this works, is that a search is done on a database
using each of the nfo files in the release as a search mask.  If found,
that nfo's data is inserted into the main database.  If no acceptable
nfo filename is found, then the release is flagged, and later on the
file is manually added to the database.

This becomes a very tedious task for one person.  Every day there is
at least one new release group, or a group who's nfo already exists
uses a different format of the filename.  Because of this it becomes
hard to keep up with the new/changing filenames.

To make this task easier, this utility was created.  It allows anyone
to submit an nfo filename for insertion into the database.  The way
this works, is that the information you send is stored in a queue.
This queue is processed a few times daily, and your entry is reviewed.
If its a legit filename then it will be added to the database.
(I have to do this in the form of a process queue, because allowing
direct adding to the nfo database would not be a good idea ;)

--------
--NOTE--
--------

Because this utility is being released publically, manual adding
of NFO's to the database will no longer occur.  If you are a releaser,
and change your NFO, or are a new group, and you do not submit it via
this utility, there is very little chance it will be added.

----------------
--Instructions--
----------------

This utility allows you to do two things.
  1- you can search for NFO's.  This is very straight-forward.  
     Simply type in the nfo filename, and click search.  There is no 
     pattern searching, this is simply a 'Yes' or 'No' result.  Either 
     it exists, or it doesn't exist.

  2- you can also submit an nfo for adding to the database.  To do 
     this, enter the nfo's filename and directory name with its date of 
     a release which contains this file.  The reason for the name and 
     date are so that the file can be verified as being an actual 
     release group file.  You do NOT need to do this for every release 
     which contains that nfo, just run this once per nfo revision.  If 
     the date is a few days in the future, then it will not be invalid 
     until that date (ie, if you are going to release something with a 
     new revision of the nfo, and want to add it before-hand).  However, 
     the nfo file will not be added until it is verified, and that can't 
     happen until the release exists.


----------
--FLAMES--
----------

I've been adding nfo filenames to the database since WinDupe started 
supporting NFO's so many months ago.  In this time I have become 
frustrated many times and am going to use this section as a way of 
blowing off steam.

My list of 'Why??'-

- Why is the year needed in an nfo name?? 
    (ie mygroup98.nfo)

- Why must the nfo filename for the same group change?? 
    (ie mygroup98.nfo, mygrp98.nfo, mg98.nfo)

- Why must there always be a group that does not want to go by standards??
    (ie mygroup.nfo along with release-title-mygroup.nfo, or similar)

- Why is it that some individual's can't follow 'standard' IND releasing??
    (ie instead of having release.nfo, having  mynick.nfo as the rel nfo)

- Why do some packers not pay attention to what they're doing??
    (ie nfo file path contains path in zip
     -> ./nfo/mygroup/releasename/nfo/mygroup.nfo)

- Why why why why why?!?!



Have fun!
-Kat
