Hi Kyle
On Fri, Sep 18, 2009 at 11:01 AM, Kyle Hall wrote:
> What I have in mind would make selecting images optional. Here is a
> thought scenario: Let's say that you prefer to use amazon images for
> your book covers, but a few books have no cover or the wrong cover
> from amazon. In this inst
Hmm...being able to select a local "cover" would also be useful for
non-print items for loan, such as toys, equipment, etc. :)
Cheers,
Cindy
~~
Cindy Murdock Ames
IT Services Director
Meadville Public Library| CCFLS
http://meadvillelibrary.org |
This is a great idea. I personally don't care that much about the "service"
in which my jacket comes from but the idea of being able to get a picture of
the cover if one isn't available. We have several items that are "unique"
that we would love to have jackets of but are not part of the general
Certainly sounds very sensible to me.
(I need to make sure folks know I have very little experience with
Koha or libraries or library work flow. So, I'm liable to suggest
things that wont work in practice. I just happen to work with Chris
Cormack on a non-Koha project and thought it would be fun t
What I have in mind would make selecting images optional. Here is a
thought scenario: Let's say that you prefer to use amazon images for
your book covers, but a few books have no cover or the wrong cover
from amazon. In this instance, you would be able to upload an image
locally, or force that bib
Selecting and storing images locally for all holdings sounds like a pain.
I can imagine a cooperatively held db (hello, koha foundation) of
records that look like:
isbn/issn/other globally unique id that identifies the holding in a
way that makes searches possible
url to images (front, back, etc)
Excellent ideas all around. I suppose it could be written as a CPAN
module which would then be used in Koha.
Kyle
http://www.kylehall.info
Information Technology
Crawford County Federated Library System ( http://www.ccfls.org )
On Thu, Sep 17, 2009 at 1:05 PM, Galen Charlton wrote:
> Hi,
>
>
Hi,
On Thu, Sep 17, 2009 at 12:04 PM, Kyle Hall wrote:
> This new Covers module would be the sole interface for Koha for all
> cover systems ( Amazon, LibraryThing, Syndetics, etc. ) and would act
> as an interface between Koha and the book cover modules.
Good idea. It occurs to me that this co
Comments inline...
On Thu, 2009-09-17 at 12:29 -0400, Joe Atzberger wrote:
> IIRC, Amazon was pretty strict about caching, limiting you to holding
> images for only 24 hours. That makes building a system around it
> significantly less desirable.
>
You could conceivably add a cache life-time t
IIRC, Amazon was pretty strict about caching, limiting you to holding images
for only 24 hours. That makes building a system around it significantly
less desirable.
The other problem you will have is that if the server is fetching all the
images from Google, a busy site will trip their anti-harve
Hey All,
Writing the LibraryThing book cover module has really got my brain
in full gear. I've been thinking about how nice it would be to add an
internal cover system to Koha. That way, a library could specify the
exact cover they want if they so wish. Here's what I'm imagining.
A new ItemImag
11 matches
Mail list logo
