Establishing a Mobile Resources Collection Development Policy

Download Establishing a Mobile Resources Collection Development Policy

Post on 27-Mar-2017

212 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

<ul><li><p>This article was downloaded by: [The Aga Khan University]On: 22 November 2014, At: 03:20Publisher: RoutledgeInforma Ltd Registered in England and Wales Registered Number: 1072954 Registeredoffice: Mortimer House, 37-41 Mortimer Street, London W1T 3JH, UK</p><p>Journal of Electronic Resources inMedical LibrariesPublication details, including instructions for authors andsubscription information:http://www.tandfonline.com/loi/werm20</p><p>Establishing a Mobile ResourcesCollection Development PolicyAntonio P. DeRosa a &amp; Sarah T. Jewell aa Memorial Sloan Kettering Cancer Center Library , New York , NewYork , USAPublished online: 09 Sep 2014.</p><p>To cite this article: Antonio P. DeRosa &amp; Sarah T. Jewell (2014) Establishing a Mobile ResourcesCollection Development Policy, Journal of Electronic Resources in Medical Libraries, 11:3, 144-154,DOI: 10.1080/15424065.2014.939000</p><p>To link to this article: http://dx.doi.org/10.1080/15424065.2014.939000</p><p>PLEASE SCROLL DOWN FOR ARTICLE</p><p>Taylor &amp; Francis makes every effort to ensure the accuracy of all the information (theContent) contained in the publications on our platform. However, Taylor &amp; Francis,our agents, and our licensors make no representations or warranties whatsoever as tothe accuracy, completeness, or suitability for any purpose of the Content. Any opinionsand views expressed in this publication are the opinions and views of the authors,and are not the views of or endorsed by Taylor &amp; Francis. The accuracy of the Contentshould not be relied upon and should be independently verified with primary sourcesof information. Taylor and Francis shall not be liable for any losses, actions, claims,proceedings, demands, costs, expenses, damages, and other liabilities whatsoever orhowsoever caused arising directly or indirectly in connection with, in relation to or arisingout of the use of the Content.</p><p>This article may be used for research, teaching, and private study purposes. Anysubstantial or systematic reproduction, redistribution, reselling, loan, sub-licensing,systematic supply, or distribution in any form to anyone is expressly forbidden. Terms &amp;Conditions of access and use can be found at http://www.tandfonline.com/page/terms-and-conditions</p><p>http://www.tandfonline.com/loi/werm20http://www.tandfonline.com/action/showCitFormats?doi=10.1080/15424065.2014.939000http://dx.doi.org/10.1080/15424065.2014.939000http://www.tandfonline.com/page/terms-and-conditionshttp://www.tandfonline.com/page/terms-and-conditions</p></li><li><p>MOBILE COMPUTING AND THE LIBRARY</p><p>Nancy R. Glassman, Column Editor</p><p>Establishing a Mobile Resources CollectionDevelopment Policy</p><p>ANTONIO P. DEROSA and SARAH T. JEWELLMemorial Sloan Kettering Cancer Center Library, New York, New York, USA</p><p>This column outlines some steps and decisions involved in the processof establishing amobile resources collection development policy. Initialdecisions should be made about what platforms will be supportedand how the workflow will be organized. There are many criteria toconsider when evaluating apps, including subject relevance, qualityof content, reputation of the producer=publisher, cost, access, legalissues, and copyright and fair use issues. We describe many resourcesfor gathering apps for potential collection and address solutionsfor promoting and disseminating the mobile resources. Finally, weaddress the evaluation of the program and future areas for research.</p><p>KEYWORDS Android, Blackberry, collection development, iPad,iPhone, mobile apps, mobile resources</p><p>INTRODUCTION</p><p>Implementing a mobile collection development policy in the library takesmore than simply creating a list of apps and resources for clients to reference.As with the physical and electronic collection, there needs to be a process for</p><p># Antonio P. DeRosa and Sarah T. JewellComments and suggestions should be sent to the Column Editor: Nancy R. Glassman</p><p>(nancy.glassman@einstein.yu.edu).Address correspondence to Antonio P. DeRosa, Memorial Sloan Kettering Cancer Center</p><p>Library, 430 East 67th Street, New York, NY 10065. E-mail: DeRosaA1@mskcc.orgColor versions of one or more of the figures in the article can be found online at</p><p>www.tandfonline.com/werm.</p><p>Journal of Electronic Resources in Medical Libraries, 11(3):144154, 2014</p><p>Published with license by Taylor &amp; Francis</p><p>ISSN: 1542-4065 print=1542-4073 online</p><p>DOI: 10.1080/15424065.2014.939000</p><p>144</p><p>Dow</p><p>nloa</p><p>ded </p><p>by [</p><p>The</p><p> Aga</p><p> Kha</p><p>n U</p><p>nive</p><p>rsity</p><p>] at</p><p> 03:</p><p>20 2</p><p>2 N</p><p>ovem</p><p>ber </p><p>2014</p></li><li><p>acquiring resources to suggest to users. Careful decision-making criteria mustbe established, and promotional and dissemination efforts must be applied.With the emergence of mobile resources come inevitable access issues tonavigate. It is essential for librarians and information professionals to beaware of the many different operating systems and mobile devices on themarket in order to offer truly valuable recommendations on mobile resourcesto their clients. The Memorial Sloan Kettering Cancer Center Library hasinitiated a formal and successful process for collecting and sharing mobileapps and resources with its users.</p><p>Initial Decisions</p><p>Initially, there are some key decisions to make regarding the establishmentof a mobile collection development policy. First, what platforms will be</p><p>FIGURE 1 Screenshot of the Memorial Sloan Kettering Library Mobile Resources LibGuide(http://libguides.mskcc.org/mobile). # [Memorial Sloan Kettering Cancer Center Library].Reproduced by permission of Memorial Sloan Kettering Cancer Center Library. Permissionto reuse must be obtained from the rightsholder.</p><p>Mobile Computing and the Library 145</p><p>Dow</p><p>nloa</p><p>ded </p><p>by [</p><p>The</p><p> Aga</p><p> Kha</p><p>n U</p><p>nive</p><p>rsity</p><p>] at</p><p> 03:</p><p>20 2</p><p>2 N</p><p>ovem</p><p>ber </p><p>2014</p></li><li><p>supported? Librarians can gather information about which platforms theirpatrons are using in several ways, such as conducting a survey or workingwith the information technology (IT) department to ascertain how manyand which devices have been purchased at an institution. Since many peoplemay use their personal devices for work purposes, a survey sometimes cangather more accurate information than just the institutions purchasing his-tory alone. At Memorial Sloan Kettering, we ultimately decided to limit ourfocus to the Android, Blackberry, and iOS platforms. We have, however,been reconsidering continuing to support the Blackberry platform, as timegoes on and its market share drops. Not only is the market share down to3.4% of the smartphone market, but when T-mobile recently offered atrade-in rebate for people to turn in their Blackberry phones for an upgrade,94% of buyers switched to a different platform.1 An emerging platform toconsider is the Windows Phone, which is now running neck-and-neck withBlackberry when it comes to market share.2</p><p>Next, workflow is an important factor to consider. How will members ofthe mobile team propose apps for potential collection and who will make thefinal decision about whether an app will be featured or not? At MemorialSloan Kettering, the mobile team consists of four members of the Referencestaff, including the Head of User Services, although in other libraries it maymake sense to include a Content Management librarian as well. We proposeapps generally via email, investigate and test the apps out on our own, anddiscuss the pros and cons via email. The Head of User Services ultimatelymakes the decision about whether or not an app will be featured on ourLibGuide , the tool we chose toaggregate our list of suggested mobile apps and resources (see Figure 1).</p><p>CRITERIA</p><p>Many sets of principles have been established throughout the history oflibrary science for acquiring and adding new items to a collection. The selec-tion criteria for mobile apps and resources are surprisingly similar in natureto those of physical collections. The mobile app=resource criteria providedhere have been adapted from the Memorial Sloan Kettering Cancer Centercollection development policy.</p><p>Subject Relevance</p><p>The needs of users should be first and foremost of utmost importance whendeciding whether or not to include a mobile resource in a collection. If theapp or mobile website in question would not be pertinent to the communityspractice or research, then there would be no point in adding it as arecommended resource. Librarians should also have an understanding of</p><p>146 Mobile Computing and the Library</p><p>Dow</p><p>nloa</p><p>ded </p><p>by [</p><p>The</p><p> Aga</p><p> Kha</p><p>n U</p><p>nive</p><p>rsity</p><p>] at</p><p> 03:</p><p>20 2</p><p>2 N</p><p>ovem</p><p>ber </p><p>2014</p></li><li><p>the community which they serve: their needs, requests, research, andscholarly universe.3 Having a firm grasp on what users need and expect willhelp to shape the collection and mobile resources recommended for down-load, giving more value to both the librarian and the library as mobile experts.</p><p>We use our embedded librarians via the Clinical Medical Librarianprogram to assess our users unique information needs in order to makeinformed decisions on mobile app=resource recommendations. Otherresources to include are found on selected collection building resources,such as iMedicalApps, MobiHealthNews, and Happtique, or through wordof mouth from clients and other colleagues. Possible additions are discussedwith the Mobile Team via email or in person at bi-monthly ContentDevelopment meetings before a final decision is made.</p><p>Quality of Content</p><p>Aside from the relevance to the user community, mobile apps and resourcesmust also be of sound quality to be included in a librarys collection orsuggested resource list. A 2012 survey study on the development of acollection development policy found the following criteria to be most impor-tant in regard to book selection: 1) authors reputation in the subject field;2) demand for the material; 3) students interest; 4) reputation for the pub-lisher; 5) high standards of quality in content, format, and=or literary merit;and 6) possibility of use for one or more courses.4 Not all of these criteriadirectly translate to mobile resources, but the theories behind them do,especially the high standards of quality in content, format and merit. Thisis a stipulation that should be expected of any quality resource a library islooking to include in their collection, mobile or otherwise.</p><p>Mobile apps are compared to physical and other electronic counterpartswhenever possible. For example, a mobile app for a scholarly journal wouldbe compared with both the content found in the physical journal and theelectronic journal on the web. Features like full text and the librarys linkresolver must be functional and seamless in order to be considered perma-nent and of good quality to be added to our list of mobile resources. Again,these resources are tested across devices (where applicable) and brought tothe Mobile Team for consideration.</p><p>Reputation of Producer=Publisher</p><p>The publisher of a book or journal article is usually a good indicator of thequality of information provided. This is why a publishers reputation weighsheavily in a collection development policy. With mobile resources, thisprinciple is not as cut and dry. Many mobile apps do not have publishers,but producers or developers who created the app. In this regard, it some-times takes a little more digging to find, research, and vet the developer.</p><p>Mobile Computing and the Library 147</p><p>Dow</p><p>nloa</p><p>ded </p><p>by [</p><p>The</p><p> Aga</p><p> Kha</p><p>n U</p><p>nive</p><p>rsity</p><p>] at</p><p> 03:</p><p>20 2</p><p>2 N</p><p>ovem</p><p>ber </p><p>2014</p></li><li><p>App stores, such as iTunes and Google Play can be mosthelpful in uncovering the true developers or producers of a mobile app orresource. Once an app is found in one of these stores, helpful links to thedevelopers website are provided. This is a useful way of uncovering an appsgovernance.</p><p>Cost</p><p>With dwindling library budgets, acquisitions managers and librarians need tocome up with creative ways to keep their collections interesting and currentfor their users, while keeping the overall cost of titles and resources in mind.Many mobile apps and resources are offered for no or minimal fees to users=institutions. Many journal subscriptions and licenses are even beginning tocome with mobile components as part of their packages. More and morepublishers are starting to include mobile counterparts in their bundlesoffered to libraries. These publisher bundles are a cost-effective way forlibraries to offer quality and abundant content to their users.5</p><p>We take the approach of offering both fee and no-fee mobile apps andresources to our user community. These resources are categorized into thesetwo buckets on our Mobile Resources LibGuide to make it easy for our clients to peruse each list. Cost isdefinitely a factor that is taken into account when considering a mobileresource to add to our list. We evaluate the resource against our other collec-tion development criteria and use professional judgment to determine if it isworth the price listed. Conversely, just because an app does not have a fee,does not necessarily mean it meets our cost criteria. Some of these no feeresources do not meet our quality and relevance principles.</p><p>Access</p><p>Functionality and usability are other key components to effective mobilecollection development. Users must be able to successfully and seamlesslyaccess the resources provided by the library. Mobile apps and resources mustbe intuitive and employ user-friendly interfaces that clients can easily use.Aside from ease-of-use, collection development librarians must also keepin mind the advantages of offering content on one platform over another.If a journal app only indexes content dating back to a given year, but theelectronic resource on the web goes back to an earlier time, it may makesense to feature the electronic journal over the mobile app.</p><p>Testing mobile apps before promoting them is an effective way to vetaccessibility and functionality. We have come to learn that reading aboutan app or mobile resource on the web is helpful, but using it on a mobiledevice provides real-world insights. It gives us the ability to (a) evaluate</p><p>148 Mobile Computing and the Library</p><p>Dow</p><p>nloa</p><p>ded </p><p>by [</p><p>The</p><p> Aga</p><p> Kha</p><p>n U</p><p>nive</p><p>rsity</p><p>] at</p><p> 03:</p><p>20 2</p><p>2 N</p><p>ovem</p><p>ber </p><p>2014</p></li><li><p>how well it works, (b) anticipate user concerns, and (c) and make a moreinformed decision on inclusion in our collection. Hands-on use of theresource itself also allows for more robust discussion with the Mobile Teamand ultimately, our clients if a question were to arise.</p><p>Legal Issues</p><p>Licensing materials is the way in which libraries have defined the waymaterials are allowed to be used by staff and clients. Through these nego-tiated contracts and site licenses, libraries are covered in regard to legalissues.3 What about a mobile app developed by an individual at a researchinstitution in Switzerland or a mobile-responsive version of a governmentwebsite? These resources do not need site licenses or contracts to access.Instead, they might provide something similar to Terms and Conditions orTerms of Service. Accepting a mobile resources terms could mean acceptingsome illegal activity. It is important to read the terms provided by mobileresource developers very carefully to ensure that the resource is incompliance with your institutio...</p></li></ul>