|
|
| Post Number: 1
|
Guest
Unregistered
|
 |
Posted on: Feb. 01 2002,03:04 |
|
   |
I have a collection of over 300 CDR's that I have to recatalog since a windows crash wiped my old cataloging programs database...so I decided I would try to find a new program and stumbled accross Ruby and may I say I like the program alot...but I have 2 feature requests.
1)I have been using the "Ruby ID's" to coincide with the number I have placed on each disc....unfortunatly during a scan&save Ruby crashed and Disc 36 cataloged by Ruby ID 36 became hosed. I then deleted the entry and rescanned it only to find out that Ruby assigned it an ID of 37 and now I am in a quandry since I should just be able to rename the ID to 36 and Ruby be fine with that...but Ruby won't do it.
2)I give very detailed Disc Descriptions because I also label my disc's accordingly, but Ruby won't search Disc Descriptions. ELITEFORCE (name of disc) ST Voyager Elite Force (disc description) and a search string of "Voyager" should find the disc even if none of the files contain "Voyager" in their names.
These two features would really be a help.
FTLNewsFeed
|
|
|
|
| Post Number: 2
|
AGP 
Group: Super Administrators
Posts: 122
Joined: Feb. 2002
|
 |
Posted on: Feb. 01 2002,03:11 |
|
 |
Im glad you like the program. In answer to your questions:
1) The RubyID is actually an automatic assignment by the database engine. It is automatic to guarantee the integrity of the database. Unfortunately this means that you cannot assign it an ID of your own. Keep in mind that it should be thought of as simply an ID and not the number of the Disc in your collection. I understand what you say but to keep the database sound, it has to be done that way. May I suggest putting your own ID in the Disc Description. In the future I may add an additional field called something like "Disc Number" although this might confuse some people.
2) You are right, Ruby will not give search results on a Disc Description. The program is setup to do searches on files and their properties. If I included the Disc Description then you would get back every file in the Disc when you did a search on a Disc Description. Let me think about that and see how it would pan out. In the mean time why dont you give one of the key files on that Disc a File Description. Then in the options you can choose to do searches and include the File Description in the search.
One more thing, although the program is pretty stable there are some minor things I have to work out so make a backup copy of your database just as a precaution.
Rgds,
Abel
--------------
>>>>>>>>>>>>>>>>>>>>
AGP
Lead Programmer, Owner
Warp Engine Software
>>>>>>>>>>>>>>>>>>>>
|
 |
|
|
|
|
|
