MLIS 7505: OPACs on Mobile Devices

 

 

 

 

 

 

 

 

Literature Review: OPACs on Mobile Devices

 

Richard McNeal

 

Valdosta State University

 

6/6/14

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Literature Review: OPACs on Mobile Devices

 

 

                Ever since the debut of the first iPhone in 2007, library users have been increasingly turning to their smartphone to consume information.  The entrance of Android based smartphones has further expanded mobile access, as well as the use of iPads and other tablet devices.  The prevalence of these devices has required that libraries continue to integrate and develop mobile technologies.  Libraries have done this either with vendor solutions designed specifically for mobile use, customizing HTML and CSS code, or utilizing third party apps that which make websites mobile friendly.  Integration of library accessibility in the mobile realm includes not only providing information about library services, but the ability to search the catalog and access electronic resources.  Accessing the online catalog is a core request by many mobile users.  This literature review will address the ability of mobile users to access library OPACs.  I will discuss LibAnywhere and Boopsie – two mobile applications that provide mobile access with catalog search capability – as well as vendor products and the customization of websites for mobile use.  Additionally, I will discuss current applications of this technology, challenges, and thoughts moving forward.

Literature Review & Use in Libraries

Literature regarding mobile library websites and the ability to integrate OPACs is profuse in the last 5-7 years, reflecting the increase of mobile device usage.  As Bridges, Gauscho, and Griggs describe (2010), many vendors came forward during the mobile device boom to provide OPAC solutions such as Innovative’s AirPac and WorldCat’s Mobile Search.  These options provide catalog access for small screens and allows users to browse the catalog, request items, and view their library account (Bridges, et al., 2010, p.314). Though this may be the simplest solution, vendor options can be costly and do not provide adequate customization features.  Some libraries elected to leverage programming knowledge among staff and produce a catalog with customized features.  Some of these customization desires include filtering catalog search results, call number information, and searching by course reserves (Bridges, et al., 2010, p. 315).    

In addition, there are third-party mobile applications that tailor OPACs to a variety of mobile devices and include additional features.  Products such as LibAnywhere and Boopsie provide mobile applications with features that allow libraries to access their library account, search the catalog, and utilize virtual reference services with the ability to tailor images and colors consistent with the library’s brand.  LibAnywhere provides either a native app or the ability to redirect users to the mobile version of the catalog and provide similar account and request options as a regular OPAC (LibAnywhere: Screencast).  Boopsie offers similar capabilities, but is perhaps more robust in its access to electronic resources.  Credo, EBSCO, and Gale are a few content provides integrated into Boopsie.  They also claim to support a wide number of ILSs and can “…integrate with any ILS a library has requested! (Boopsie: Frequently Asked Questions).”        

Increasingly, many libraries are electing to customize their OPACs – via HTML and CSS – for optimal mobile accessibility.  Gillian Nowlan (2013) describes how the University of Regina implemented their mobile website and catalog.  After conducting a survey with other libraries and students at their own institution, they ultimately decided to utilize existing IT staff that had experience with HTML and CSS (Nowlan, 2013, p. 148). Some of the data that drove their decision included the cost of a native app, lack of customization, and the ability to configure code for all mobile devices (Nowlan, 2013, p. 147).  Ken Irwin (2012) argues some of the same points regarding the benefits of mobile OPACs built in house.  Irwin notes that not only does this option save money and provide customization, it also helps web designers create a skill set that is crucial for an increasingly mobile environment (Irwin, 2012, p.45).

                Rebecca Jackson (2013) surveyed 99 ARL libraries to determine the use of mobile websites.  While surveying mobile sites, the author often encountered two scenarios: either the library website URL brought up the mobile version or a prompt appeared to download a native app.  However, most library websites simply provided a mobile version without an app.  In her survey, 84% of libraries had a mobile site.  This number increased greatly from a 2010 study where only 22% had mobile website (Jackson, 2013, p. 175).  Access to the library catalog was a part of about 53% of mobile sites surveyed (Jackson, 2013, p. 177).  Though roughly half may seem like a small percentage, the library catalog was listed in top ten “must haves” of library mobile sites, including library hours, the main library site, and virtual reference services based on user feedback (Jackson, 2013, p. 176).  

Challenges & Issues

 

                Providing OPAC access via mobile devices does pose a few challenges related to authentication and content.  When searching an OPAC on any device, many users come with the impression that they have access to all content.  However, when it comes to accessing electronic journals, databases, and other resources, mobile OPACs do not provide such content access.  Bridges, et al. (2010) note that “…what users typically want from a library is direct access to research materials. Offering a truly mobile catalog interface with links to mobile-friendly catalog records will make the library’s resources actually usable for mobile users (p. 315).” Authentication to access these resources also poses problems.  Mobile apps which include OPAC access do not necessarily provide authentication for electronic resources.  In his article on mobile authentication and access, Mark Williams (2012) notes the following with mobile library apps “…many apps sidestep the issue of having a genuine mobile authentication process to access resources by only allowing search and discovery and not content access, which has to be done via traditional browsers (p. 269).”  The author goes on to describe how traditional browsers are often not much of a better solution.  In some cases, logging in to authenticate involves institutional and vender logins, creating a long and confusing journey.  Williams (2012) states that institutions could develop single sign-on portals to create a seamless authentication experience or a device-twinning as solution “…which effectively links an institutional user account with a specific device for a predetermined length of time (p. 271).”        

Conclusions

                As evident from the literature review, integration of mobile capabilities for library websites and OPACs has been on the upswing.  Libraries can essentially be accessed anywhere by properly utilizing mobile applications or tailoring website coding and layout for smaller screens.  Regarding how mobile accessibility is implemented, the trend seems to be to code library websites and OPACs rather than purchase mobile applications – a cheaper option which allows for mobile accessibility on various platforms (Android, iPhone, etc).  I found this trend to be specifically true in the case of Innovative Interfaces’s AirPac product.  Though it was mentioned extensively in some of the literature from 3-4 years ago, this product is actually no longer developed and maintained by Innovative – evidenced by its absence on their product page.  Libraries increasingly have staff in place equipped to code websites for mobile devices and have no need to pay for native apps or third party products.

                Moving forward, the demand for more comprehensive access to library resources via mobile OPACs will continue to be a challenge.  Mobile device usage will increase and libraries must be committed to finding solutions to authentication access to electronic resources.  Personally, I have found using apps such as Papership – which gives you mobile access to content (articles and PDFs) previously saved in Zotero and Mendeley– as one way to circumvent authentication issues with mobile OPACs.  However, this app only provides access to content previously searched and saved.  It is not a replacement for a fully capable OPAC that could provide full access and authentication.  Until such an OPAC capability becomes a reality, libraries must develop or market immediate solutions – such as Papership – and work with content vendors in streamlining mobile authentication.                      

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

References

 

 

Boopsie: Frequently Asked questions. Retrieved June 4th, 2014 from http://www.boopsie.com/frequently-asked-questions/#library-mobile-strategy

Bridges, L., Rempel, H. G., & Griggs, K. (2010). Making the case for a fully mobile library web site: from floor maps to the catalog. Reference Services Review, 38(2), 309–320. doi:http://dx.doi.org/10.1108/00907321011045061

Irwin, K. (2012). The Homegrown Mobile Catalog: A Quick, Inexpensive Approach to Expanding Access. Technical Services Quarterly, 29(1), 42–57. doi:10.1080/07317131.2012.624453

Jackson, R. (2013). Mobile Academic Libraries: A Snapshot. Reference & User Services Quarterly, 52(3), 174–178.

LibAnywhere: Screencast.  Retrived June 4th, 2014 from http://www.libanywhere.com/

Nowlan, G. (2013). Going mobile: creating a mobile presence for your library. New Library World, 114(3/4), 142–150. doi:http://dx.doi.org/10.1108/03074801311304050

Williams, M. (2012). Mobile Authentication and Access: Any Time, Any Place, Any Device? Insights, 25(3), 268–273.

 

 

MLIS 7505: Is 3D printing all the rage?

So, one of the big topics of discussion this past week was 3D printing. We read one article in particular that talked about implementing 3D printing in a large public university library. This library implemented a relatively low cost printer and then charged for the printing. However, they did not receive a ton of usage, but there was still some benefits for students and researchers who needed this specialized technology.

I know some public libraries have such printers, but I'm not sold that they fit the need of every library or institution.  This is mostly because it seems like a specialized technology - perhaps similar to a CAD machine - that would fit nicely in a community or library with such a demand.  I can see university libraries with a engineering, architecture, or other scientific programs benefiting.  My knowledge is fairly limited on this topic, but I'm not sure all libraries need to be clamoring to provide such technology quite yet.

MLIS 7505 Assignment #3: Interview about CMS in academic libraries

Below is the transcript from my interview with Chris Pollette, Emerging Technologies Librarian at Emory University.  I asked him a few questions about his use of CMS and how its managed within the library.  You will also find my paper that includes a summary of the interview and analysis.  Enjoy!

When did you start using a CMS at Emory?

Until the last year or so, Drupal was used for the library’s website for several years.  We recently switched over to Cascade.     

When did that switch over occur?

The switchover occurred in August 2013 around the same time we targeted for major changes to the library website. 

What were the motivations for adopting Cascade and leaving Drupal behind?

Well, I believe there were a few contributing factors.  The library and IT divisions combined at Emory right before our change over to Cascade.  This transition sort of helped bring about larger discussions about the library’s web presence and how it fit into the university’s use of Cascade.  This meant that there was a desire to create a uniform technology environment across campus.   Library IT, library leadership, and campus web development team began to have discussions about the library website and its management.

What role did the library have in this transition?

We didn’t get to choose the new CMS itself.  But, the change correlated with a large overhaul of the library website.  Librarians, library IT, and the university web development team worked together to facilitate these changes. 

What are the important benefits or advantages of Cascade over Drupal?       

The largest benefit of switching from Drupal to Cascade was the opportunity to make university website management more uniform for the information technology team. Cutting down on the number of platforms that need to be supported makes it easier to focus management and support efforts.

How was the learning curve?

Impact on the learning curve was mitigated somewhat by the university's Web design group, which offered training for library employees. They also created templates for most of the basic content created by library staff, and a guide to show new users how to use the system.

Also, some of our staff was already working consistently with the WDG, so that helped establish lines of communication and understanding that helped make our change to Cascade a positive one. 

The majority of the back-end coding is still handled by the WDG.  I would say, however, that some knowledge of coding is advantageous in editing via Cascade, though not necessary.   The differences in Drupal and Cascade Server in basic page management, however, are somewhat minimal.

  

How is the content managed for the library website?

The content for the library website is managed across different departments with people who have editing rights. 

How many editors does the library have?

I believe the library has about eight editors. 

Richard McNeal

MLIS7505

Dr. Yang

5/31/14

Assignment 3: Interview with an Emerging Technologies Librarian about CMS

Introduction

                The use of content management systems for library websites can provide both opportunities and challenges for library staff.  CMS can provide uniformity, streamline branding across multiple websites within an organization, and create more efficient workflow.  Conversely, some challenges can crop up related to training of librarians and staff.  To gain a real world perspective on this topic, I interviewed Chris Pollette – Emerging Technologies Librarian at Emory University.  Chris focuses on user education, connecting emerging technologies with research and teaching needs, and the development of web content as well as marketing of library services and collections.   In our discussion, Chris discussed moving from Drupal to Cascade, working with the university wide web development team, and training librarians and other staff who were new to Cascade.  This paper will outline the main points communicated by Chris in our discussion.  I will also draw from our main CMS article discussed in our course in providing analysis of the interview.

Interview Findings

                In the beginning of 2013, discussions were held with the campus web development team, library IT, and library leadership about the opportunity to migrate to a new content management system.  This new opportunity was partly influenced by the organizational change whereby libraries and IT services were combined into one division.  This helped facilitate broader considerations about the library’s web presence.  A top-down decision was made for the library to migrate from Drupal to Cascade, given Cascade’s wider use across campus.  At that time, Drupal was the library’s content management system that had been in place for several years.  This decision was primarily motivated by a desire to create a uniform web environment throughout campus, leveraged by the new organizational change.

                Chris expressed that there were a few advantages to migrating to Cascade.  The central advantage was related to reduction of multiple web platforms across campus and divisions, thus allowing staff to focus on management and support efforts.  Training of librarians and staff was a more complex issue.  Chris noted that the university’s web design group played a central role in training library staff on Cascade.  This included creating templates commonly used by library staff and a guide on for new users.  Any coding was mostly handled on the back end by the web development group.  Though Chris mentioned that in-depth knowledge of coding wasn’t absolutely necessary to use Cascade and other content management systems, general familiarity with coding was helpful when editing pages and content.  Regarding differences between Drupal and Cascade, Chris noted that there are differences in page management, but these differences did not provide huge barriers to the migration.  Chris also that selected librarians in various departments throughout the library were given content editing rights.  This was similar to the arrangement with Drupal, but done on a broader scale with Cascade with about eight editors.

                Chris did provide a few insights into the relationship between the library and the broader campus web team.  As previously stated, the move to Cascade was in part motivated by an organizational change, thus coming from a top-down decision.  Additionally, this migration was done in concert with a major change to the layout and design of the library’s website.  These changes were implemented in a web working group that included librarians, library IT, and the campus web development team.  Chris noted that this working group opened lines of communication about the library’s web presence that ultimately made the migration to Cascade easier.              

Analysis

                

                Our assigned reading for content management systems provided broader context and insight for many of the findings in my interview. In her article, Sara Connell conducted a survey with college and university libraries to find whether they adopted CMSs and their experience with such an adoption.  One main connection between my interview and the article is the motivation and reasons for migrating to a new CMS.  Chris noted that the migration to Cascade was not the result of a choice, but rather a top-down decision about the library’s place in the university wide web presence.  Sara Connell’s (2013) findings reflected this trend in that only nine percent of libraries in her survey had a real choice into whether they wanted to transition to a CMS (p. 51).  Chris’ experience certainly fit this trend.

Another additional point of analysis is the role of library staff in the subsequent migration website maintenance.  While the library did not have a say in choosing a CMS, the website changes that coincided with the CMS transition involved librarians, library IT staff, and the campus web team.  In addition, the campus web team did provide the library with templates and guides in using and navigating Cascade.  Interestingly, Connell’s (2013) assertion that libraries must have involvement in the editing rights and maintenance of their websites seems to have been integrated in Chris’ case (p. 54).    

                A final point of discussion focuses on the benefit of allowing multiple users to edit content.  The training and tutorials provided by the campus web team allowed the library to assign content editors in multiple departments.  Connell (2013) notes that one main benefit of CMSs is the “…ability to give multiple people, regardless of their web authoring skills, the opportunity to edit webpages (p. 52).”  This advantage was certainly leveraged in Emory’s case with eight editors.  This number of editors fit with about 13% of libraries in the survey (p. 52).  

Conclusion

                Speaking with Chris about the recent switch from Drupal to Cascade and the subsequent website changes highlighted many of the findings in Connell’s survey. The top-down trend of migrating to a new CMS, the library’s limited role in CMS selection, and the training of library staff were key points from the interview that paralleled trends in academic libraries.  As Chris noted and Connell argued, giving the library a concrete role in managing a CMS and its web content is critical.  Library websites provide critical access to resources and library information, which necessitates strong involvement in its web presence.  Collaborative implementation of CMSs in academic libraries can help improve workflow on the back end and user experience on the front end.

References

Connell, R. S. (2013). Content Management Systems: Trends in Academic Libraries. Information    

             Technology and Libraries, 32(2), 42–55. doi:10.6017/ital.v32i2.4632

MLIS 7505: LIS folks NEED to be on Twitter

I was never really a Twitter guy.  However, after deciding that Facebook was becoming more taxing and annoying than anything else, I turned to Twitter. I originally turned to Twitter a few years back to aggregate news and follow my favorite sports teams. This time I decided to connect with LIS professionals and its been a MUCH better experience.  You can regularly find tweets and discussions related to all things LIS.  Also, there are regular discussion hashtags, such as #libchat, that provide a forum for constructive and helpful insights into the field.  Utilizing Twitter in this manner allows for filtering out a lot of the noise and fluff on Twitter and turning it into a professional resources and forum.

MLIS 7505: YAY!!! Technology isn't so bad!

Hopefully as aspiring librarians we refrain from
reacting this way to technology

Before taking Information Architecture and Applied Tech in Libraries, I was sort of "meh" on technology. I wasn't "meh" in the sense that I didn't have basic technology skills or know how.  It was just that I wasn't sure where technology fit into my interests in academic libraries. I had some nascent interests, particularly in webdesign, but I just wasn't sure how interested I really was.

WELLL, I can now credit these classes with piquing my interest in technology in libraries. This May semester's class - Applied Technologies in Libraries - has really opened my eyes to the dynamic (and dare I say....fun) way technology can be used. Designing a website, creating a library wiki, integrating a virtual reference service, or building a mobile services, are all different ways that technology can be used in libraries. Not to mention that technological literacy and skills is a huge asset in the career field.

So, if you haven't bought into my cheesy-ness of how fun and interesting this stuff actually is, at least take comfort that you're positioning yourself well for gainful employment by taking classes like these.

MLIS 7505: Joomla Exercise

This week's exercise included using an open source content management system - Joomla - to create articles, a menu bar, and experiment with website layout. This exercise coincided with our reading on libraries and their use of CMS in managing their web presence.

I decided to create a site that aggregated top news stories in religion. I modified the "Getting Started" page as the homepage to introduce my site and created two news articles linked in the top menu bar. I also changed some of the colors in the template, changed the article details information and location on each page, and created my own "About the Author" module.

Having already had Information Architecture last semester, I found this exercise to be a fun way to reuse some HTML and CSS tricks learned in the previous course.  I was able to learn these skills to modify the positioning, size, and padding of images in each of my articles.

I have only scratched the surface of Joomla in this exercise. Learning how a CMS functions and operates seems challenging, but its features have the capacity to enhance and improve a library's web presence. Judging from this exercise, management of CMS is certainly a specialized knowledge.  Libraries adopting a CMS must have staff in place to handle such a transition as well as understanding the importance of information architecture and fundamental coding.

On a personal note, I have really been thinking about how to keep my HTML and CSS skills going forward since I do not necessarily see web design as a main feature of my career path.  However, such skills are always a benefit and I've wondered which online tools would allow me to cultivate these skills. I've thought of using something like Joomla as my online portfolio so that I could continue to tinker with HTML and CSS. There are also some cheap web hosting services out there that give you more freedom in coding, but Joomla is definitely a resource I'm going to consider for my portfolio.

My Joomla Page

MLIS 7505: Library Wiki Proposal

ILS Migration Wiki for "Kairos College"

Population served: Undergraduate college of about 3,000 students
Library type: Academic library
Collection strengths: Humanities, education, sciences
Staff: 30 FTE & 5 .5 FTE

The goal of the Kairos College Wiki is to build a knowledge base among library staff for an impending migration to a integrated library system.  The Wiki will provide space for uploading vendor documentation and staff created documents (videos and images as well) to assist in the migration process.  There will be a core page for the migration and each department will have its own page with specialized information and documents related to its specific work.  Ideally, departments will be able to comment and share knowledge and draw connections in preparation for the migration.  The Wiki will also help track the timeline and progress towards the date of the migration.  

Requirements of the Wiki:

• Free
• Ability to comment
• Email notifications
• Categories
• Link to other internal pages
• File attachments
• Embed calendar
• Unlimited storage
• Embed videos & images
• Full text search

Recommendations: GeniusWiki and DokuWiki