QUOTE(STEVE MOULDING @ Dec 6 2007, 09:46 PM)

Thanks very much for the offer of help!

At some point I may need it, though it can be slow, tedious work. It takes most of my time trying to keep up with 18thC copper. I have 10's of thousands of images of Silver and 19thC copper waiting to be organized, and auction catalogs waiting for the scanner and/or photoshop cut & paste.
It's really a huge project (which I may never complete) and I've been at it for 5 years now. Unfortunately there's so much still to do so I can't always respond as fully or as quickly as I'd like if somebody asks me to check for a certain die/year of a Rouble (though there's a much better chance if the request is about 18thC copper). It has alreay resulted in some rarity articles for the JRNS however.
Die varieties I haven't even thought about. Still working on getting coins into their appropriate year/denomination folders.
On a different note, it would be somewhat tricky turning this into a public project / database as auction catalogs are copyrighted and part of the business revenues of our dealer friends comes from selling catalogs. I don't want to step on any toes there. Even internet images are likely copyrighted.
So long it's for personal research I would think its OK, but distributing it en masse probably isn't.
Steve
Steve, I read your interesting PDF file presentation about the database. It would be interesting to know more technical details about how you are going about things. For example, there is software out there -- some (a lot of it, actually) is open source and freely available -- which can run batch jobs on a folder of hi-res images, for example, and create thumbnail images or resize the existing ones, all without manual labor in Photoshop or your favorite paint program. That could save lots of time if you need thumbnails, for example on a web site or in some other graphical presentation of the data. Also, if there is a well defined folder structure and naming conventions, there are editors which can create HTML pages by programming macros to do the job (UltraEdit for Windows or Emacs on Linux, for example). Some databases can store images directly in a table; but some of those which can, aren't terribly good at it, so it might be better to leave the actual image files in the file system folders.
As to copyright issues for scans from printed catalogs, there probably aren't that many different venues to consult ... perhaps less than 20? As long as credit is given, there shouldn't be any problem as long as only images are depicted (for example, no prices realized, etc.) Besides, if the database were available as a public service and not for profit, you are providing dealers with free publicity by including their auction images.
However, if the database is publicly available on the internet, there is always the chance that someone will try to use some of the images for fraudulent eBay auctions. There's really not much you can do to prevent that except to discover the bad auction and expose it by reporting to eBay or whatever venue.
I think it is important to think about the scope of the application, whether it is strictly for private use, or available as a commercial or non-commercial public service. That will determine the direction any further development should take.