Re: [OPEN-ILS-GENERAL] Mobile catalog?
Quoting Buzzy Nielsen bu...@hoodriverlibrary.org: Hi everyone, Does anyone out there have a TPAC mobile catalog? We've been tentatively exploring the possibility of having a mobile catalog here in the Sage Library System, but we don't quite know where to get started. Is there already a mobile skin included with 2.2 or 2.3? If not, would anyone care to share templates of their mobile catalog with us? Bill Erickson demoed something very briefly at the last conference. It was a proof of concept mobile interface built on tpac. I have lost the details, perhaps Bill can chime in? Thanks for any help that you can provide! Cheers! Buzzy Nielsen Library Director Hood River County Library District 502 State St Hood River, OR 97031 541-387-7062 http://hoodriverlibrary.org -- Jason Stephenson Assistant Director for Technology Services Merrimack Valley Library Consortium Chief Bug Wrangler, Evergreen ILS
Re: [OPEN-ILS-GENERAL] Mobile catalog?
On Thu, Nov 08, 2012 at 09:06:13AM -0500, Ben Shum wrote: I think you're thinking of the Bill Erickson's Beanstalk simple TPAC that was a sample mobile catalog. http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/berick/beanstalk Also, I guess Bill Ott, GRPL took that code and ran with it some. See http://catalog.grpl.org/eg/tinypac/home which is what I get when browsing them from my phone. Yep. I will admit to deliberately not mentioning beanstalk in my initial response because I think the approach of carving out different sets of HTML for different browsers (whether mobile or desktop based) is difficult to test and maintain, versus defining the content that you want in your HTML once and changing the layout via CSS based on the display capabilities of the consuming browser. And it seems that Google, at least, agrees that responsive design is the best practice: https://developers.google.com/webmasters/smartphone-sites/details
Re: [OPEN-ILS-GENERAL] Mobile catalog?
On 11/08/2012 09:06 AM, Ben Shum wrote: I think you're thinking of the Bill Erickson's Beanstalk simple TPAC that was a sample mobile catalog. http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/berick/beanstalk Also, I guess Bill Ott, GRPL took that code and ran with it some. See http://catalog.grpl.org/eg/tinypac/home which is what I get when browsing them from my phone. You were one step ahead of me Ben. I just pushed those files out for anyone interested. It was an itch I was scratching one day, and is largely unstyled, but very lightweight. The additions I made to the Beanstalk concept were the myopac features. https://github.com/grpl-eg/rel_2_2/commit/c4aa4a5939806bb557a53bde6f712b45d118e996
Re: [OPEN-ILS-GENERAL] Mobile catalog?
Hi all, I don't know the best way to develop and maintain an Evergreen mobile site, but I wouldn't say the native catalog is particularly mobile friendly. The GRPL example is much closer to what I would call a mobile friendly site. I would expect the mobile catalog to be more stripped down than the native tpac skin. I visited some 2.3/master catalogs after reading the initial e-mail, and I still need to do zooming as soon as I reach the catalog to read the screen. What I would envision on a truly mobile site is: 1. On the main catalog page, I am immediately presented with a search box front and center, similar to what happens when I arrive at Google's mobile site. Font sizes should be bigger so I don't need to zoom. I would expect the filters to be below the search box to fit to the screen better, as we see in the GRPL mobile site. However, even on the GRPL site, I need to zoom to get that search box front and center. A prominent link to My Account would also be needed. Many libraries use the bottom space of their main page for graphic images, search tips, or other extraneous material. I wouldn't want to see that piece of the page displaying on a mobile site because it takes up valuable real estate. 2. On the search results page, I want to see a list of titles that, once again, is front and center without the need to do any zooming. I think the bibliographic information should be minimal on a mobile site and the place hold link prominent. I would also like to see the call number for the library I am searching here. We often think of users searching a mobile catalog from home, but, as a library user, I never use the public catalogs in my library anymore. I find it much more convenient to walk around the stacks with my iPhone in hand. I would either entirely scratch the facets on the search results page or find another way to provide access to them. For example, in a typical browser, Amazon provides limiters in the left sidebar of its search results. When I access Amazon on my phone, those limiters are located at the bottom of the screen, and I get a Choose a Department option at the top of my search results that brings me to those limiters. 3. The mobile catalog should also have the ability to link to the full version of the catalog (as I saw in the GRPL example) so that people who want to access added content or features can do so. In those cases, the person is actively choosing to do that pinching and zooming dance. 4. Geolocation would also be a great addition to the catalog, particularly for consortia and multi-branch libraries. It could identify the library that is nearest to the user and possibly set it as the default search location. I don't remember where I saw them, but I recall seeing some screenshots last summer from the GSOC project to build an Evergreen Android app. If I remember correctly, the app did a lot of the things identified above. Personally, I prefer a mobile site over an app because I'm guessing some users won't want to go through the trouble of downloading an app to search the catalog. Also, as an iPhone owner, the Android app wouldn't be useful to me. I'm curious if others have thoughts on what would make the catalog more mobile friendly. Kathy Kathy Lussier Project Coordinator Massachusetts Library Network Cooperative (508) 343-0128 kluss...@masslnc.org Twitter: http://www.twitter.com/kmlussier On 11/8/2012 9:34 AM, Dan Scott wrote: On Thu, Nov 08, 2012 at 09:06:13AM -0500, Ben Shum wrote: I think you're thinking of the Bill Erickson's Beanstalk simple TPAC that was a sample mobile catalog. http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/berick/beanstalk Also, I guess Bill Ott, GRPL took that code and ran with it some. See http://catalog.grpl.org/eg/tinypac/home which is what I get when browsing them from my phone. Yep. I will admit to deliberately not mentioning beanstalk in my initial response because I think the approach of carving out different sets of HTML for different browsers (whether mobile or desktop based) is difficult to test and maintain, versus defining the content that you want in your HTML once and changing the layout via CSS based on the display capabilities of the consuming browser. And it seems that Google, at least, agrees that responsive design is the best practice: https://developers.google.com/webmasters/smartphone-sites/details
Re: [OPEN-ILS-GENERAL] Mobile catalog?
On Thu, Nov 08, 2012 at 10:46:53AM -0500, Kathy Lussier wrote: Hi all, I don't know the best way to develop and maintain an Evergreen mobile site, but I wouldn't say the native catalog is particularly mobile friendly. The GRPL example is much closer to what I would call a mobile friendly site. I would expect the mobile catalog to be more stripped down than the native tpac skin. I visited some 2.3/master catalogs after reading the initial e-mail, and I still need to do zooming as soon as I reach the catalog to read the screen. What I would envision on a truly mobile site is: 1. On the main catalog page, I am immediately presented with a search box front and center, similar to what happens when I arrive at Google's mobile site. Font sizes should be bigger so I don't need to zoom. I would expect the filters to be below the search box to fit to the screen better, as we see in the GRPL mobile site. However, even on the GRPL site, I need to zoom to get that search box front and center. A prominent link to My Account would also be needed. Many libraries use the bottom space of their main page for graphic images, search tips, or other extraneous material. I wouldn't want to see that piece of the page displaying on a mobile site because it takes up valuable real estate. 2. On the search results page, I want to see a list of titles that, once again, is front and center without the need to do any zooming. I think the bibliographic information should be minimal on a mobile site and the place hold link prominent. I would also like to see the call number for the library I am searching here. We often think of users searching a mobile catalog from home, but, as a library user, I never use the public catalogs in my library anymore. I find it much more convenient to walk around the stacks with my iPhone in hand. I would either entirely scratch the facets on the search results page or find another way to provide access to them. For example, in a typical browser, Amazon provides limiters in the left sidebar of its search results. When I access Amazon on my phone, those limiters are located at the bottom of the screen, and I get a Choose a Department option at the top of my search results that brings me to those limiters. 3. The mobile catalog should also have the ability to link to the full version of the catalog (as I saw in the GRPL example) so that people who want to access added content or features can do so. In those cases, the person is actively choosing to do that pinching and zooming dance. 4. Geolocation would also be a great addition to the catalog, particularly for consortia and multi-branch libraries. It could identify the library that is nearest to the user and possibly set it as the default search location. I don't remember where I saw them, but I recall seeing some screenshots last summer from the GSOC project to build an Evergreen Android app. If I remember correctly, the app did a lot of the things identified above. Personally, I prefer a mobile site over an app because I'm guessing some users won't want to go through the trouble of downloading an app to search the catalog. Also, as an iPhone owner, the Android app wouldn't be useful to me. I'm curious if others have thoughts on what would make the catalog more mobile friendly. Thanks for the concrete suggestions. Almost all of this can be achieved via CSS, possibly with some changes to the underlying HTML (e.g. tables to divs or whatever so that Place Hold appears under the bib info instead of way over to the right). I don't see anything that suggests a need for two distinct versions of HTML in your wish list. Geolocation functionality could be supported for desktop browsers too, but be careful in how you implement it. If you go to branch1.example.com in your browser and get redirected to automatically searching branch2 instead of branch1, that's probably going to break user expectations.
[OPEN-ILS-GENERAL] SIP2 Messages supported
Can someone tell me if this page is up-to-date as to what SIP2 messages Evergreen currently supports. I was surprised that RENEW is not supported. This info was found on this page, http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-admin:sip_support, which suggests the following: Message pairs currently supported include: 01 Block Patron 09/10 Checkin 11/12 Checkout 17/18 Item Information 23/24 Patron Status 35/36 End Session 37/38 Fee Paid 63/64 Patron Information 93/94 Login 96/97 Resend last message 98/99 SC/ACS Status. There is also support for SIP clients to retrieve and display a detailed/itemized list of billings to the patron (not sure how that fits in with SIP2) Message pairs NOT currently supported: 15/16 Hold, 19/20 Items Status Update, 25/26 Patron Enable, 29/30 Renew, 65/66 Renew all =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant / The Galecia Group Oversight Board Communications Committee / Evergreen (707) 763-6869 // lori.a...@galecia.com Availability: http://doodle.com/loriayre lori.a...@galecia.comSpecializing in open source ILS solutions, RFID, filtering, workflow optimization, and materials handling =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: [OPEN-ILS-GENERAL] SIP2 Messages supported
Hi, On Thu, Nov 8, 2012 at 1:13 PM, Lori Bowen Ayre lori.a...@galecia.comwrote: Can someone tell me if this page is up-to-date as to what SIP2 messages Evergreen currently supports. I was surprised that RENEW is not supported. Off the top of my head, I know that the Fee Paid message IS now supported, so yeah, that wiki page should be considered out of date at the moment. I'll take a hand at updating it. Regards, Galen -- Galen Charlton Director of Implementation Equinox Software, Inc. / The Open Source Experts email: g...@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web:http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org http://evergreen-ils.org
[OPEN-ILS-GENERAL] Security releases: OpenSRF 2.1.1; Evergreen 2.3.1, 2.2.3, 2.14
The Evergreen development team has announced security releases for the currently maintained versions of OpenSRF and Evergreen. Please see http://evergreen-ils.org/blog/?p=828 for complete details.
Re: [OPEN-ILS-GENERAL] SIP2 Messages supported
Thanks, Jason! On Thu, Nov 8, 2012 at 10:40 AM, Jason Stephenson jstephen...@mvlc.orgwrote: It is done by making a 63 request for patron information and setting the appropriate flag on the request: a Y in position of the summary field.
Re: [OPEN-ILS-GENERAL] Mobile catalog?
Thanks, everyone, for this very productive discussion. I especially like Kathy's recommendations. Providing a more mobile-accessible interface for My Account to allow for easier renewing would also be nice. As Kathy mentioned, larger font sizes would help immensely and probably some slightly different layout. Personally, I'm trying to avoid the need for some sort of app. I know that Boopsie has designed iOS and Android apps for systems running Evergreen, But I think it's a lot more accessible, and less hassle, for our patrons if we don't require them to go out and download a separate app to access something that can be made accessible without one. Thanks for all of your great work on this! Cheers! Buzzy Nielsen Sadly not a web or application developer, but a pleased Evergreen user Library Director Hood River County Library District 502 State St Hood River, OR 97031 541-387-7062 http://hoodriverlibrary.org On 11/08/2012 08:24 AM, Dan Scott wrote: On Thu, Nov 08, 2012 at 10:46:53AM -0500, Kathy Lussier wrote: Thanks for the concrete suggestions. Almost all of this can be achieved via CSS, possibly with some changes to the underlying HTML (e.g. tables to divs or whatever so that Place Hold appears under the bib info instead of way over to the right). I don't see anything that suggests a need for two distinct versions of HTML in your wish list. Geolocation functionality could be supported for desktop browsers too, but be careful in how you implement it. If you go to branch1.example.com in your browser and get redirected to automatically searching branch2 instead of branch1, that's probably going to break user expectations.
Re: [OPEN-ILS-GENERAL] Mobile catalog?
On Thursday, November 8, 2012 at 2:30:59 PM Buzzy Nielsen bu...@hoodriverlibrary.org wrote: I think it's a lot more accessible, and less hassle, for our patrons if we don't require them to go out and download a separate app to access something that can be made accessible without one. It also includes those (like myself) who use other mobile platforms (such as Windows Mobile) that aren't based on iOS or Android Aaron Z Jr. Systems Administrator Pioneer Library System 2557 State Rt. 21 Canandaigua, New York 14424 Phone: (585) 394-8260
Re: [OPEN-ILS-GENERAL] Mobile catalog?
On Thu, Nov 08, 2012 at 04:10:38PM -0500, Aaron Zsembery wrote: On Thursday, November 8, 2012 at 2:30:59 PM Buzzy Nielsen bu...@hoodriverlibrary.org wrote: I think it's a lot more accessible, and less hassle, for our patrons if we don't require them to go out and download a separate app to access something that can be made accessible without one. It also includes those (like myself) who use other mobile platforms (such as Windows Mobile) that aren't based on iOS or Android And as one of the token Canucks in the room, Blackberries / Playbooks :)
[OPEN-ILS-GENERAL] Circulation patron id question
We are headed into using Evergreen and I notice in the required patron fields, there is a place for an ID number with many libraries suggesting putting a Driver's license number or Other. What do you recommend using for juveniles or adults without a Driver's license? Thanks in advance. J. Sara Paulk, Regional Director Wythe-Grayson Regional Library === Email scanned by PC Tools - No viruses or spyware found. (Email Guard: 9.0.0.2308, Virus/Spyware Database: 6.20850) http://www.pctools.com/ ===
[OPEN-ILS-GENERAL] Updating Instructions from 2.2 to 2.3
Dear Sir, When can we get the updating instructions of Evergreen from version 2.2 to 2.3. -- With Best Regards, Jayaraj J. R. Library Information Assistant IISER Thiruvananthapuram
Re: [OPEN-ILS-GENERAL] Updating Instructions from 2.2 to 2.3
On Fri, Nov 09, 2012 at 09:24:43AM +0530, Jayaraj JR wrote: Dear Sir, When can we get the updating instructions of Evergreen from version 2.2 to 2.3. Robert Soulliere wrote up these instructions as part of the documentation some time ago: http://docs.evergreen-ils.org/2.3/_upgrade_the_evergreen_code.html You can subsitute 2.3.1 for 2.3.0 throughout, as Evergreen 2.3.1 was released very recently and the docs haven't had time to catch up yet.
