Using Koha for photo archive
We have a large photo archive, which we are scanning into image files as time goes by. Is there a way to use Koha to catalog this archive and attach the image files to the record so they can be downloaded by the user? There may be more than one image file per record - for instance if it was scanned as both a jpg and a tif file. Is there a way to handle that situation? Thanks for the look. Doug
Hi, On 12/7/07, Doug Dearden <dearden@sarsf.org> wrote:
We have a large photo archive, which we are scanning into image files as time goes by. Is there a way to use Koha to catalog this archive and attach the image files to the record so they can be downloaded by the user? There may be more than one image file per record - for instance if it was scanned as both a jpg and a tif file. Is there a way to handle that situation?
One approach would be to store your image files on your web server. When you catalog each image, you can create an 856 field that links to each version, e.g., 856 $uhttp://yourwebserver.org/images/image-abc.jpg 856 $uhttp://yourwebserver.org/images/image-abc.tiff Regards, Galen -- Galen Charlton Koha Application Developer LibLime galen.charlton@liblime.com p: 1-888-564-2457 x709
Galen Charlton <galen.charlton@...> writes:
One approach would be to store your image files on your web server. When you catalog each image, you can create an 856 field that links to each version, e.g.,
856 $uhttp://yourwebserver.org/images/image-abc.jpg 856 $uhttp://yourwebserver.org/images/image-abc.tiff
Regards,
Galen
Hi Galen, Thanks for the suggestion, a couple of other people emailed me with the same one. I've been pulled off to another project for now but will try this after the new year and post my results. This looks like the solution. Regards, Doug
Doug Dearden <dearden@...> writes:
Galen Charlton <galen.charlton@...> writes:
One approach would be to store your image files on your web server. When you catalog each image, you can create an 856 field that links to each version, e.g.,
856 $uhttp://yourwebserver.org/images/image-abc.jpg 856 $uhttp://yourwebserver.org/images/image-abc.tiff
Regards,
Galen
Hi Galen,
Thanks for the suggestion, a couple of other people emailed me with the same one. I've been pulled off to another project for now but will try this after the new year and post my results. This looks like the solution.
Regards,
Doug
I am having a problem getting this to work. I have created a new subdirectory named "images" under the /usr/local/koha/opac/htdocs subdirectory. I put an image file in there - "ac18.jpg". If I put http://webserveraddress/images/ac18.jpg into a browser, up pops the image. When I put the same url - http:/webserveraddress/images/ac18.jpg into the 856u field, what I see on the "8" tab of an opac lookup on the item is the http code - an anchor "a" followed by href equals the address above in quotes then the address without quotes. I'm seeing the http code but it is not being rendered as a clickable link on the page. I've tried several variations - ../images/ac18.jpg for example, but to no avail. I have a feeling I'm missing something simple here. Looking at the source code for the page, I see the less than and greater than symbols for the anchor being listed as "<" and ">" instead of < and >. I think that is why the browser is not correctly interpreting the http. Any ideas? Thanks, Doug
Doug Dearden <dearden@...> writes: Never mind. The simple thing I was missing, was just using the Normal view instead of the Complete view. In the Normal view the URL shows up just fine. Thanks, Doug
participants (2)
-
Doug Dearden -
Galen Charlton