Re: [Koha] Koha - Mobile web version.
OK, maybe like this one? http://www.amzari.com/v3/2011/04/mobile-opac-based-on-koha-open-source-ils/ Felipe Adalid Ortiz Anzaldo Bibliotecario de sistemas Universidad Iberoamericana Tijuana Biblioteca Loyola http://clavius.tij.uia.mx Ave. Centro Universitario 2501 Playas de Tijuana 22200, Tijuana, B.C. 0 664 630-1577 Ext. 623 adalid@tij.uia.mx
Take it and run! :) On Thu, Nov 10, 2011 at 5:19 PM, Adalid Ortiz <adalid@tij.uia.mx> wrote:
OK, maybe like this one? http://www.amzari.com/v3/2011/04/mobile-opac-based-on-koha-open-source-ils/
Felipe Adalid Ortiz Anzaldo Bibliotecario de sistemas Universidad Iberoamericana Tijuana Biblioteca Loyola http://clavius.tij.uia.mx Ave. Centro Universitario 2501 Playas de Tijuana 22200, Tijuana, B.C. 0 664 630-1577 Ext. 623 adalid@tij.uia.mx _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Nucsoft OSS Labs mentioned at KohaCon 2012 that they're commissioned to write a Mobile OPAC for one of their customers. Hopefully one of their team can provide some more details on what this will entail. BibLibre also indicated they were working on a mobile CSS. Two different ByWater partners have also expressed interest in making this happen. I think what needs to happen next is the community needs to get together and come up with a list of features and design styles that should make up a Mobile OPAC, and put together a implementation plan on which to do first. If we have a unified specification out there, all these different parties can work together towards the same goal, rather than having half a dozen different implementations floating around out there. Some questions to ask: - CSS-based, or a new template? - What features first? Search and biblio details seem obvious. What about user logged-in features? - Specific features for mobiles, like integration with GPS, compass, accelerometer and camera? This may require OS-specific apps, but would make the model tool that much more appealing Cheers, -Ian On Thu, Nov 10, 2011 at 8:17 PM, Liz Rea <lrea@nekls.org> wrote:
Take it and run!
:)
On Thu, Nov 10, 2011 at 5:19 PM, Adalid Ortiz <adalid@tij.uia.mx> wrote:
OK, maybe like this one?
http://www.amzari.com/v3/2011/04/mobile-opac-based-on-koha-open-source-ils/
Felipe Adalid Ortiz Anzaldo Bibliotecario de sistemas Universidad Iberoamericana Tijuana Biblioteca Loyola http://clavius.tij.uia.mx Ave. Centro Universitario 2501 Playas de Tijuana 22200, Tijuana, B.C. 0 664 630-1577 Ext. 623 adalid@tij.uia.mx _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
2011/11/14 Ian Walls <ian.walls@bywatersolutions.com>: ...
Some questions to ask:
CSS-based, or a new template?
I have been working on a non-Koha specific mobile web app for libraries based on WordPress and searching through Z39.50/SRU ( http://demo.mobibl.no/ ). I have used jQuery Mobile (JQM) to do the interface, and I'm very happy with it, so maybe it could be a good basis for working on a mobile version of the Koha OPAC too? It would require new/extra templates, though, since JQM has quite rigid expectations for the HTML it works with.
What features first? Search and biblio details seem obvious. What about user logged-in features?
Seems natural to start with the non-logged in parts and then progress to the logged in parts?
Specific features for mobiles, like integration with GPS, compass, accelerometer and camera?
Do we need them? I don't think we do if all we aim to do is reproduce the functionality of the current OPAC for mobile browsers.
This may require OS-specific apps, but would make the model tool that much more appealing
I think we need to focus on building a mobile web-app version of the current OPAC, since this is something that would work out of the box for every library using Koha, and something that would build on the current code. A native app (at least for iPhone) would have to get through the whole approval process etc. Would there be one app per library, or would there be one Koha app to rule them all, where you'd just choose your library? If so, who would "own" the app in the app store? This would be more of a stand alone project as far as I can see, that would communicate with Koha over Z39.50/SRU and ILS-DI, perhaps. I'm not saying we should not do it, I just don't see this as a natural part of the main Koha project/codebase... Just my NOK 0.02... Best regards, Magnus PS Here's the source code for my moBibl project: https://github.com/MagnusEnger/mobibl-wp-plugin https://github.com/MagnusEnger/mobibl-wp-theme https://github.com/glitre/glitre It's far from being wrapped up in one coherent, easy to install package, as you can see...
Le lundi 14 novembre 2011 à 13:12 -0500, Ian Walls a écrit :
Nucsoft OSS Labs mentioned at KohaCon 2012 that they're commissioned to write a Mobile OPAC for one of their customers. Hopefully one of their team can provide some more details on what this will entail.
BibLibre also indicated they were working on a mobile CSS. Two different ByWater partners have also expressed interest in making this happen. We did it. You can test it here :
http://catalogue.devunilim.biblibre.com/ using css only is quite interesting because : - easy to maintain - all the OPAC features But less smoothly integrated in the mobile phone. requires internet connection.
I think what needs to happen next is the community needs to get together and come up with a list of features and design styles that should make up a Mobile OPAC, and put together a implementation plan on which to do first. If we have a unified specification out there, all these different parties can work together towards the same goal, rather than having half a dozen different implementations floating around out there.
Some questions to ask: * CSS-based, or a new template? * What features first? Search and biblio details seem obvious. What about user logged-in features? * Specific features for mobiles, like integration with GPS, compass, accelerometer and camera? This may require OS-specific apps, but would make the model tool that much more appealing
-- Henri-Damien LAURENT BibLibre
BibLibre also indicated they were working on a mobile CSS. You can test it here : http://catalogue.devunilim.biblibre.com/
I tried this on my Android phone and iPad, but only seemed to get a desktop version... David
So has the css been shared for the mobile website someplace? I don't want to recreate any more wheels! I've also looked at modifying existing code to create a mobile Koha, but what I have done requires manual updates to templates etc.. Plus it was done PRE-Template Toolkit... So now I need to clean it up for submission under the 3.6 using TT. http://m.catalog.pisd.edu -- David Schuster Library Technology Coordinator Plano ISD ---- Henri-Damien LAURENT <henridamien.laurent@biblibre.com> wrote:
Le lundi 14 novembre 2011 à 13:12 -0500, Ian Walls a écrit : Nucsoft OSS Labs mentioned at KohaCon 2012 that they're commissioned to write a Mobile OPAC for one of their customers. Hopefully one of their team can provide some more details on what this will entail.
BibLibre also indicated they were working on a mobile CSS. Two different ByWater partners have also expressed interest in making this happen. We did it. You can test it here :
http://catalogue.devunilim.biblibre.com/ using css only is quite interesting because : - easy to maintain - all the OPAC features But less smoothly integrated in the mobile phone. requires internet connection.
I think what needs to happen next is the community needs to get together and come up with a list of features and design styles that should make up a Mobile OPAC, and put together a implementation plan on which to do first. If we have a unified specification out there, all these different parties can work together towards the same goal, rather than having half a dozen different implementations floating around out there.
Some questions to ask: * CSS-based, or a new template? * What features first? Search and biblio details seem obvious. What about user logged-in features? * Specific features for mobiles, like integration with GPS, compass, accelerometer and camera? This may require OS-specific apps, but would make the model tool that much more appealing
-- Henri-Damien LAURENT BibLibre _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
... Mobile OPAC, and put together a implementation plan ...
Some thoughts from a non-Koha-specific perspective. As background, I spent some time working on a mobile Tomcat skin for my Voyager ILS, but ended up scrapping that as we were close to deploying Summon, which has a mobile version. We're currently working on something to fill in the gaps between them - user account info and hold etc requests - with pages that will serve both desktop and mobile.
CSS-based, or a new template?
I would say both. :-) There are some advantages to having separate mobile pages, but the general move seems to be towards responsive web design [1], i.e. adapting the layout for the user. Particularly for something like an OPAC I think that it's advantageous to have a URL that works everywhere, not just on a desktop OR a mobile. It's not necessarily as straightforward as picking CSS templates using media queries. There are a couple of reasons why it's probably a good idea to create a new template for this, rather than bolting additions onto an existing one. One is that it's important to limit what's downloaded on mobiles - for performance and bandwidth charges. It's easy to tell the browser to resize a large image, or to just hide extra stuff that's not displayed (but still downloaded), but it would be much better for the users to take the "mobile first" approach of serving up mobile by default and adding in extra JS/CSS/etc if a larger screen is detected. Also, I have to say that of all of the mobile OPACs I've seen, the ones that were developed through a process of "how can we shrink this desktop page down to fit on a mobile?" rather than "what information do we want on a mobile and how can we best display it?" are uniformly crappy. Admittedly, many of those desktop OPACs are pretty crappy to begin with,4 but even with Koha it would be best to take a look at mobile design from scratch.
What features first? Search and biblio details seem obvious. What about user logged-in features?
I don't have any corroborating evidence at my fingertips, but my understanding is that mobile users tend to be looking up info like library hours and when their books are due more than searching. Which is to say - those things are probably important to be doing at the start, rather than leaving 'til later. It's probably useful to mention that one easy (and apparently relatively cheap) way to go mobile is to sign up with Boopsie [2] or LibraryThing's LibraryAnywhere [3]. They're perhaps less likely to be of interest to Koha libraries(?), but they can be useful for inspiration to copy too. :-) Also, I'll mention that I've been pondering the idea of writing a web app with Sencha Touch [4], in addition to the other mobile stuff. That wouldn't be until some time next year, so I'd be quite interested to see if anyone else did something along those lines. Anway, that was all that fell out of my head - hopefully it wasn't *too* rambling. :-) Cheers David [1] A good read, plus lots of links: http://www.lukew.com/ff/entry.asp?1436 [2] http://www.boopsie.com/libraries.html [3] http://www.bowkerinfo.com/offers/LibraryAnywhere/ [4] http://www.sencha.com/products/touch/
participants (7)
-
Adalid Ortiz -
David Friggens -
dschust＠tx.rr.com -
Henri-Damien LAURENT -
Ian Walls -
Liz Rea -
Magnus Enger