-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syndetics #13
Comments
Adding a new provider is not a big deal... But isn't Koha Syndetics integration sufficient? |
No, because regardless if I am using Coce or just Amazon or whatever along with Syndetics, is if Syndetics doesn't have a graphic, it will still take priority in the covers and show as blank, and Coce or whatever is in the second slide. Koha isn't very smart about blank graphics. Granted, this might also be worth addressing on bugzilla as well, but it seems better suited for Coce, as it would be great for this to be in a place where it doesn't have to grab the cover as often if it is cached like all the others. I think it would be a nice incorporation into Coce, and an optional way to handle it. |
There is one difficulty. Generally you set up a Coce server to serve multiple Koha instances. That's what we're doing (Tamil). But Syndetics API uses a client token. It means that other libraries that the one that pay Syndetic will gain access to Syndetics book covers. |
Ah, well that is a problem. Unless you can create a Coce Syndetics authentication field, and get Coce to check if the requesting library's token is valid, then use what is cached. |
A Coce server could be seen as a commodity. It's a light service with very low ressources consomption. So for a large library, it would make sense to have a dedicated Coce server. |
Well, if putting Syndetics in a dedicated server instance was an option, we would certainly consider it. |
Are there any plans to incorporate Syndetics into the mix? It would be nice to be able to include Syndetics into the options rather than side-by-side with Coce.
The text was updated successfully, but these errors were encountered: