Open Sourced Cataloguing Packages?
mcse_knowthyenemy asks: "I am cataloguing a HUGE private collection for a magician (No, we cannot waive a wand...) with an item count of at least 100k. The end result will be a searchable website. There are several Windoze packages that fit the bill (item data ad nauseum, image inclusion, reports, website). But these invariably requires numerous Microsoft products plus IIS. So, any input on a solution that is based on Apache, instead?" There are plenty of cataloguing and e-Commerce bases out ther that would work for this, one only has to perform a quick Freshmeat search to find them, however this being a museum, maybe there are better options? Would you use the already available software for this sitution or would you write something custom, instead?
Why doesn't the magician just keep track of everything with magic?
Karma: Good (despite my invention of the Karma: sig)
Poking around a little, it looks like there's a good (but old?) FAQ from Netscape, though there some other sources of information out there.
DO NOT LEAVE IT IS NOT REAL
I have to jump in on this being that this is my current profession. More than likely a custom made approach would work best here (Ofcourse GPL/BSDL the work). Try a *SQL database, with apache for the web (like you said). Use perl and cgi scripts to access and create your catalogue. Take a look at Endeavor . They are what alot of libraries use. It would be hard, not going to pull punches here, but it would garuntee contract work for life. Good luck with this and I know I'd like to keep up with how this pans out.
"If a quarter is two bits, then a dollar's a byte." -R Deric Miller
Write a quick custom app using Linux, Apache, Mysql, PHP
Easy as cake.
i have been looking at this as an option for some programs, but whats irritating is some programs require full database such as PostgreSQL, when i like mysql. I usually dont want to run both. fortunatly i have a bit of programming experience and i can usually modify it. but some programs it seams that a real database would not be needed. To bad there wasnt a way for easy plugin access, ODBC could work, but still thats not a great example. something in a standalone "db", like access 2000 is used (on the windows side)
In my programming C# book, Microsoft has come a long way with using xml database recordsets. its kind of cool and pretty easy to implement. which works perfects in smaller applications.
4. cowsay
An easy way to add speaking and thinking cows to anything.
Yeah, that obviously applies. On top of that, did anyone notice the spelling of Catalog?
catalogue
That wouldn't have been my first attempt (was it Cliff's?).
And some of you wonder why the guy just asked ./ instead of looking for himself.
"I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)