Book Database

Robizzle01

Limp Gawd
Joined
Sep 30, 2005
Messages
159
Campus book stores are a huge ripoff and i'm thinking about making a book-swap website for my school. I have a lot of the inner workings layed out in my mind but before I even start coding anything, I need to figure out how i'm going to work with all the different books.

My first idea was to simply allow users to add new books to the database and they would fill in all the information about a book for me (author, title, publisher, date published, ISBN #, etc) but I am very scared of ending up with a database that has 10 copies of every book each with different spellings and typos in various fields. I wont have the time to log into the database and merge records of duplicate books so this idea is out.

My second idea would be to find a database somewhere that either allows free accessing or one that I can download and install onto my server then do all the lookups from there. Problems with this solution could be adding new books throughout the life of the website or incomplete databases. Also, my database should only need 500-1000 (I'm not a good estimator) books to cover every required reading for all the classes here whereas if I download and import one from a website somewhere, it would be much much larger -- would this impact my performance any or would it simply be a harddrive space issue? If I remember, mySQL will self organize entries such that the most common items are also the fastest to find and return (if this is true, then after a week of using the database I should have a fairly fast website and maybe even after a few months of use I could go ahead and delete all the books with zero accesses.)

And then a fallback plan that would be horrible would be to maintain and add all entries myself. If I had to go this route i'd likely just setup my website for the most common 25-50 classes and leave it at that.



Sorry for the lengthy description but understanding my problem may help people give me more directed feedback. Does anyone know of a database somewhere that is free to download that contains information such as ISBN numbers, authors and titles? Or any other solutions anyone else could come up with?
 
Your description is actually painfully short; even a simple system like the one you're describing deserves pages of specifications.

There's no "self-organizing" feature exactly as you are describing. I believe what you're thinking of is a cache. When the storage engine reads a page from the database, it stores that page in memory. If it again needs to read the same page, the cache has the page is taken from memory and there doesn't need to be a physical I/O to satisfy the request. This makes the most recently accessed items fast to find, not necessarily the most commonly accessed items.

If you have to enter 1000 titles and it takes 30 seconds to enter each title, you should be able to cover it in an eight-hour work day.

You might find usable resources at http://www.isbndb.com/ or http://www.isbntools.com/. The Amazon site offers an API which I believe can retreive information for a title given an ISBN.
 
Your first idea is probably closest to what you will want to do. Basically, for adding books, just have the user input the ISBN first. Check that against the DB and if it is already there then you won't have to add it. If it's not there, let the user input the appropriate fields. Better yet, use the online ISBN tools that mikeblas posted.

I knew a couple guys who did pretty much the exact same thing at my school a few years ago. It's changed a bit over the years, though, and I'm not even sure if they have a book-swapping feature anymore(that's all it started as). Now it looks like they just list prices from various book retailers. Still pretty useful, though. Anyway, the site is http://www.pricemonk.com/.
 
Just this weekend I installed OpenDB on my server, it catalogs DVD's, CD's, books, etc. into a database, and has the ability to lookup the information by ISBN or name using places like Amazon, IMDB, CDDB, etc, and is actually designed for loaning out and tracking the media. Give it a shot and figure out how it works, that'll be a huge chunk of your work already done :)

With some modifications you could make it to where they can only manually enter information if the automated lookup fails, or returns erronous info or revision. Of course with any DB there will probably be a little cleaning up to do every once in a while, thats a given.
 
mikeblas said:
There's no "self-organizing" feature exactly as you are describing. I believe what you're thinking of is a cache. When the storage engine reads a page from the database, it stores that page in memory. If it again needs to read the same page, the cache has the page is taken from memory and there doesn't need to be a physical I/O to satisfy the request. This makes the most recently accessed items fast to find, not necessarily the most commonly accessed items.
Well I don't know much about how databases are actually implemented behind the scenes but I figured it would have been implemented similar to that of a splay tree.

mikeblas said:
If you have to enter 1000 titles and it takes 30 seconds to enter each title, you should be able to cover it in an eight-hour work day.
Yeah, it wouldn't be so bad if I could just get a list of all the books I need in the database. But that would require emailing every professor on campus and even then I wouldn't get a reply from half of them. Naturally the book stores on campus wouldn't want to help me out as I could potentially cut into thier profits.

As for OpenDB, I'll look into it for sure but I don't think I need anything complicated. I'm thinking that I could whip up some simple php for adding, removing and searching items in the database plus I wouldn't mind doing it myself as a learning experience.

Thanks for the ideas everyone, I'm still sorting everything out and I appreciate any other ideas you all may have.
 
Robizzle01 said:
Well I don't know much about how databases are actually implemented behind the scenes but I figured it would have been implemented similar to that of a splay tree.
If you read that splay tree article, you'll quickly find why databases don't use such a structure for their storage.

For now, it's probably best to focus on your application rather than the details of the implementation of the DBMS system.
 
Talk to third party bookstores and see where they get their info. My personal opinion, if you don't know anything about databases, you're digging yourself a hole. Don't plan on making any sort of profit without a lot of learning or hiring someone who knows what they're doing. There is plenty of competition out there between third party college bookstores and online places like Amazon Marketplace, Half.com, and ebay, so you have to bring something unique to the table to succeed.
 
Learning is what i'm here to do, and i dont plan on profitting from this site (yet.) If it starts to get widely used I might add a donation feature or charge $1 per transaction (or at least cover bandwidth somehow) but the main idea is to help solve the problem of book prices being so huge and no one central place for students at my particular school to find eachother.

We have one website that a lot of people use (http://www.allmsu.com) but it is more of a bullitin board for selling anything and everything to other students at the school -- my idea would be much more finely tuned for books and more automated instead of making each user read through all the posts only to find after contacting all the sellers that they have already been sold.
 
Back
Top