Database - Photo Gallery

Hi Kevin the fishman,

You might want to check this page. It has a collection of mostly free PHP scripts. Some are standalone and some work with a mySQL backend. Hope this helps in your search.
http://www.hotscripts.com/PHP/Scripts_and_Programs/Image_Manipulation/Image_Display/

Dan

I looked at most of the scipts and they are not what I want.

But thanks anyway...

Does anyone else have a suggestion?

------------------

You could hirer someone to build you a custom script for starters. If you want something custom that’s the best way to go. I do this type of work fairly often and people are always amazed at how functional a custom application is.

Second you may want to look at http://www.cgi-resources.com/Programs_and_Scripts/Perl/ they have a lot of Perl scripts, including tons of photo album type programs.

Good luck,

------------------
Adam
AIS Internet Solutions
[email protected]
www.aisinternet.com

I have looked through all the images at cgi-resources.com. Most of them are thumbnail galleries. The ones that aren't thumbnail galleries don't suite my needs.

Also, I was hoping to us MySQL so there would be less strain on the server. Or would a CGI work just as well?

------------------

The best way would probably be building a management interface that allows you (or your visitors) to add pictures and text, the images would then be stores in a particular folder and the program would index them by category or what ever. You could implement them directly into mySQL but most hosts have a maximum on the database size (usually anywhere from 2 to 8MB).

------------------
Adam
AIS Internet Solutions
[email protected]
www.aisinternet.com

Adam, there is no limit to the sizes of my databases.

How would I create something like that?

------------------

I’d be happy to point you in the right direction, however there’s no way I can explain it all here. If you want to save the images inside the database you use BLOBs (binary large object). There are a few tutorials around that explain how to do this. You may also want to purchase a PHP/mySQL book. DevShed also has a good mySQL tutorial at http://www.devshed.com/Server_Side/MySQL/Intro/ In many ways it’s a lot easier just to locate the files in your servers WWW space.

------------------
Adam
AIS Internet Solutions
[email protected]
www.aisinternet.com

First off, you need to learn SQL. With 2200+ photos, this is not something you want to do with text files and scripts. You want to use a database (mySQL is a good candidate that most web companies use) and a scripting language to generate your pages dynamically (PHP or Perl work well).

You might want to start a database in Microsoft Access. The database could have two parts (tables). One would correspond to information about the species of fish, and one would correspond to information about the photograph.

The fish table would contain the species, etc. You could also put "category" information on this table, like "man-eating fish", "plant-eating fish", etc.

Having a separate photograph table would allow you to have multiple photos of each fish if you so choose.

You might also want a table to store your categories/sub categories. It would depend if you want to have more information specifically about these categories (as opposed information about the individual fish). It would also help performance (I'll explain this later).

I would advise against storing the images in the database. This makes them unwieldy, and some service providers (mine, for example) prohibit this because they don't have a way of restricting the space you use in the database (the database files are stored in a common directory). If you use a standard directory structure to store the files and store pointers in your database to the file (by pointer, I mean the name of the file + the subdirectory) then it's just as easy as storing them in the database, and it more flexible.

I would suggest your fish table to look something like this:

1) Species ID (a simple number simply identifying your fish type. Don't try and build any intelligence into this key -- it can come back to haunt you later).

2) Species name

3) Common name

4+) Any specific information about this fish, including categories/sub categories, species comments, etc.

Your photograph table would be something like this:

1) Species ID (pointing back to the fish table).

2) URL/Email for credits.

3) Pointer to where the photo is. If you do this properly, you can have identical directory structures on your PC vs your web site. Then simply synchronize the directories whenever you update your site. It will allow you to see the picture on your PC and also on your site.

The advantage of keeping your site on both the web and your PC is that if your ISP decides to pull the plug on you, or the site crashes, you don't lose everything. It's a real concern, not a far-fetched one.

Once you have the web database set up and populated, all you need to do is to write a few scripts that will generate your pages. For example, you could have one script generate a list of category links. Each link would point to a script that generated the list of fish in that category. Each link in that list would bring up the photo(s) of the fish along with any descriptive information about it, and the crediting URL's.

One other thing to consider; you might want to use the database structure to generate static HTML pages for each fish. There are two reasons for this:

1) Database queries can be somewhat resource-intensive. Depending on how much power your site has (if you're on a virtual host shared by other sites, it might be slow to get data from a database), it might be faster to serve up a static HTML page vs. a dynamic page.

2) Search engines don't index dynamic pages. So if someone goes to Yahoo and types in "Sea Bass", if you have a static page devoted to the Sea Bass, it may come up, but if you only have a dynamic page it won't.

You're really going to have to want to learn about new technology though; it seems like you've reached the human limit on maintaining your web site, and in order to get to the next level you need to learn some new stuff.

Ralph

------------------
http://www.hockeydb.com