Resource Review #8: Trying Out Clouds

I had difficulty picking a final resource review. What resource would make the perfect capstone to my research? Well. . . none. Here are a few articles I’m clumping together into one resource:

Glotzbach, M. (2009, Dec. 14). Re: Cloud apps, big city: LA goes Google [Web log message]. Retrieved from The Official Google Blog, http://googleblog.blogspot.com.

Library of Congress and DuraCloud launch pilot program using cloud technologies to test perpetual access to digital content. (2009, July 14). Loc.org. Retrieved from http://www.loc.gov/today/pr/2009/09-140.html.

OCLC announces strategy to move library management services to web scale. (2009, April 23). OCLC.org. Retrieved from http://www.oclc.org/us/en/news/releases/200927.htm

These three articles work together to illustrate different ways that libraries can try using cloud computing services. There’s just so much out there on cloud computing, I thought some concrete examples might be nice. Here we go!

The first resource, which I’ll call “LA Goes Google,” discusses the city of LA’s recent switch to cloud computing. Now, instead of relying on local servers to host email or software, city employees are using resources such as Gmail, Google Docs, and Google calendar. The article (which, to be fair, is written by Google!) stresses that the city will see increased security of data and cost savings. Sounds almost too good to be true!

The next resource, “Library of Congress and DuraCloud” mention a few libraries that are using DuraCloud, a “cloud-based service” (hm. . . not to specific, is it?) to provide digital access to certain library resources. Libraries mentioned include the New York Public Library and the Biodiversity Heritage Library (in partnership with other nonprofit organizations). The Library of Congress intends to “test to the use of cloud technologies to enable perpetual access to digital content.” The goal, to provide perpetual access to digital content, will include “content replication and monitoring services that span multiple cloud-storage providers.”

Finally, the OCLC resource announces a new initiative by OCLC to develop a cloud-based library management service. This web services aims at integrating library components such as circulation and acquisitions with other systems such as human resources for a more streamlined, cost-effective management system.

I choose these different resources because they’re great example of what libraries can possibly use cloud computing technology for. I’m hesitant to enthusiastically embrace all these initiatives, but I do think they should be commended for their innovation. Things that surprised me about these resources: switching to Google Apps in LA actually increases security of city data? I’m not sold. While the article mentioned the city’s servers were previously just sitting in a basement, now they’re completely off-site and in the hands of a third party. Obviously it’s in Google’s interest to keep this data safe, but other considerations also arise with using distant servers for data: legal requirements for the transmission of personal information. As I’m sure some city employees must deal with confidential information about certain persons, I just hope someone thought about what kind of data will stored on the cloud and whether it’s proper. Complicated stuff!

“Library of Congress and DuraCloud” also surprised me: when I think of the internet and digital information, I definitely don’t think of perpetual information. However this is the goal of the project: to use cloud services to offer perpetual access to digital information. I’ll be very curious to read about how the LOC & DuraCloud handle issues related to outages, possible format changes, etc. I’m no archivist but I do worry about the preservation and access to digital information.

Finally, the OCLC announcement perhaps concerns me the most. I think it’s an innovative approach–to offer streamlined services in the cloud for library systems–but I cannot imagine relying on a web-based service to provide things like circulation services. Going offline for even a short while once a year (when our system upgrades) creates enough of a headache. I feel as if a web-based service would be even less stable and have more downtime, but maybe I’ll be proved wrong!

And that’s it! Just a few thoughts on libraries (and cities) going in the cloud. I’m excited to keep watching this issue and seeing where this increasing reliance on cloud computing takes us! Thanks for reading.

Resource Review #7: Clash of the Clouds

For my seventh resource review, I looked at an article in The Economist about major players in the cloud computing scene.

Clash of the Clouds (2009, Oct. 15). The Economist. Available at: http://www.economist.com/displaystory.cfm?story_id=14637206. (Last visited December 15, 2009).

When I think about cloud computing, I think about using the internet to access and store information. I think about relying on web browsers to do common computing tasks like word processing or email. I think about organizations (such as libraries), switching to free software and not investing in hardware or servers like they used to. I don’t think about battles between major companies such as Microsoft, Apple, and Google.

Maybe I should. This article, focusing on the upcoming battles between these computing giants, got me thinking about cloud computing services in a new light. 

There are, admittedly, probably thousands of companies offering cloud computing services. The Economist article chooses to focus on Microsoft, Apple, and Google because these three “play in a different league.” All three not only have data centers all over the world, but also intend to offer multiple cloud computing services as suites. These suites, offering service such as email, address books, storage, and business applications have the potential to play a huge role in consumers’ lives. As a result, these is real competition as to what cloud computing provider will come out “on top” and dominate the cloud computing scene. 

The article looks at Microsoft, Apple, and Google from a historical standpoint before assessing their current strength in the market. Each company has different strengths. For instance, Microsoft has long dominated the software scene with its popular operating system and office suite. As for cloud computing, the company has a large network of data centers and is beginning to develop online services. However, its online services are not as developed as others, and Microsoft’s mobile operating system is behind both Google’s and Apples. Regardless, the article considers Microsoft to be a major player due to its huge amount of resources and current market share. Microsoft can, it states, create a ’seamless experience’ through cloud computing services that will attract consumers. 

Apple and Google also have strong backgrounds to dominate this new market. Apple’s reliance on creating popular devices such as the iPhone give it a leg up with providing cloud computing services, since users of Apple’s popular mobile device may want to use Apple services to access their information. Apple currently offers a suite of cloud computing services aptly titled “MobileMe,” but this has yet to truly gain in popularity. Google, on the other hand, has a large number of services that utilize cloud computing technologies, is entering the mobile market with its Android operating system, and has an extensive network of data centers all over the globe. Each company is uniquely positioned to take advantage of consumers’ increasing reliance on cloud computing technology. 

Where the future leads? No one quite knows. Other companies (such as Amazon and Facebook) may also emerge as strong contenders in cloud computing services. While this article does not predict where the market will go, it does raise the question about the next big battle in computer service providers. I had not approached the subject of cloud computing from this perspective, so it was interesting to give it some thought. 

For me, Google is the dominant provider of cloud computing services.  I think consumers will continue to use Google’s suite of services as long as it remains free, easy-to-use, and innovative. If Google manages to successfully enter the mobile market and give Apple a run for its money its chances of remaining a strong presence in the computing world is even more solidified. However, I hope to see more competition and would love for other providers to step into the cloud computing suite field. 

Application of this resource to libraries? I think it’s good to be aware of what providers are out there, and there different strengths and weaknesses. Libraries interested in using cloud computing technology should take the time to assess their different options before taking the plunge, although the article does point out that one plus about using cloud computing technology is that switching from one provider can be a relatively painless task. As a result, maybe the point important point I got from this article was just to be aware of the different services and suites provided using cloud computing. Perhaps one version will better meet my needs than the other, and the only way to find out is to explore all my options. 

Overall, an interesting read!

LibraryThing

#11 of the 23 Things is to explore LibraryThing.

LibraryThing allows you to catalog your library, review books you’ve read, and explore new books to read in the future. Other features of LibraryThing include: book discussions, groups, and information on local book-related happenings in your area. 

LibraryThing is a very busy site. To be honest, the interface is too busy for my taste. But I always enjoy cataloging what I’ve read, so I was happy to export my list of books from Goodreads.com and give it a try (more on Goodreads later).  It imported my information from Goodreads relatively well, and so there I was! About 130 books cataloged in my profile. 

Things I like about LibraryThing:

• Recommendations. On my “home” page, LibraryThing recommends titles to me based upon my cataloged library, as well as recommendations based upon user-submitted information. Users are able to submit recommendations on a specific book’s page. For example, if I wanted to recommend Lolita to readers of War and Peace, I would simply go to the War and Peace page and submit my recommendation. I like this kind of input and plan on using this feature in the future. 
• Early Reviewer Giveaways! I participate in this program on Goodreads.com, which is essentially the same thing: publishers and/or authors agree to give away so many advanced copies of new books. LibraryThing users request to receive a copy, and LibraryThing selects who wins the copies. Winners are asked to post a review to LibraryThing after reading the book. This is a way to publicize the book and get the word out to other LibraryThing users. I’ve already entered to win a few early review giveaways myself.
• Local Book Search. This has great potential! If I find a book on LibraryThing I want to read, I have a number of options on the right-hand side of the page. I can click to see the WorldCat record, Google Books record, or purchase it using an online retailer. OR I can click on “local book search.” Based on my local information, LibraryThing reports what bookstores nearby have this item for sale. I was able to see that my local Borders had a copy of “Peony in Love” within seconds.  This feature isn’t perfect, however: my local bookseller was listed but LibraryThing could not retrieve their holding information. Really, I don’t see why my local bookstore would bother to give LibraryThing a copy of their records, but wouldn’t be cool? 

  Now, about Goodreads. Goodreads and LibraryThing are both websites that allow me to catalog my books, but Goodreads has a more social networking flavor to it. When I sign into Goodreads I can immediately see what all my friends are reading.  I really like this aspect of it–I often find interesting books to read this way, and since joining I’ve discovered my friends and I are more likely to discuss books than before. I also think the Goodreads website is more clean and appealing than LibraryThing’s.

In terms of functionality, LibraryThing seems to have more robust features for actually cataloging your books. Goodreads allows you to import books and create tags (also known as “shelves”) for them, and that’s about it. However, Goodreads has interesting exploration features, user-created reading lists, book giveaways, and online discussions. The real kicker for me is that Goodreads is absolutely free, whereas LibraryThing does have a small cost after you’ve cataloged 200 books. I’ll continue to try out LibraryThing in the future but plan on still using Goodreads, as I’ve used it for years and enjoy doing so. Fun “thing” to try this week!

Resource Reviews #5 & #6: Legal Implications of Cloud Computing

 

Image by seychelles88

For my resource reviews #5 & #6, I’ll be looking at the legal implications of cloud computing. My resources are:

Navetta, D. (2009, Sept. 12). Legal implications of cloud computing – Part one (the basics and framing the issues). LLRX.com. Available at www.llrx.com/features/cloudcomputing.htm.

and

Forsheit, T. (2009, Oct. 17). Legal implications of cloud computing – Part two (privacy and the cloud). LLRX.com. Available at www.llrx.com/features/cloudcomputing2.htm

More after the cut.

Resource Review #4: Cloud Computing and Law Libraries

In addition to library school, I’m also working on my law degree. In fact, I’ll be done with all my law school coursework exactly one month from today! To celebrate, I’m doing today’s resource review on an article about cloud computing in law libraries. 

Murley, D. (2009). Law libraries in the cloud. Law Library Journal 101(2), 249-254. Available at http://www.aallnet.org/products/pub_llj_v101n02/2009-15.pdf.

Murley’s article is a good introduction to cloud computing and raises important questions to consider before using online applications/software or storage options within a law firm setting. I think this article is a great introduction to cloud computing for law firm librarians, as she raises some important legal issues to consider with regards to privacy.

With applications and storage that use cloud computing (often referred to as SaaS, or “software as a service”), lawyers can access data from any web-connected computer. This is great, and very convenient for both lawyers and support staff such as firm librarians, but providing such access over the internet raises concerns as law firms have ethical obligations to their clients. Before a library recommends a particular SaaS application for the firm, Murley’s recommends review a number of factors about the service, including the software’s procedures to protecting data from unauthorized access, and ownership rights of the data once stored on the SaaS provider’s servers.  After listing these factors, she also notes the actual ethical duties of lawyers and client information arising from the Rules of Professional Conduct. While the American Bar Association has not yet issued opinions as to whether storing client files on third-party servers is permitted, a few state ethic proceedings provide some guidance. Two state bars permit such storage, provided the attorney exercises reasonable care. 

I’ve been thinking about legal concerns for cloud computing for a while, and think I will dig into that topic for my later resource reviews.  In the meantime, this resource is a good introduction to cloud computing within a private library setting, especially if your library has privacy obligations to clients.

Cloud Computing Tool: Dropbox

This week I’ll presenting my individual topic to my LIS 644 class. While I won’t be presenting cloud computing, I will be presenting a tool that uses cloud computing. Meet Dropbox.

Dropbox is a tool that syncs data from one computer to another by storing the data “in the cloud.” The process is easy:

• Download Dropbox and create an account
• Download Dropbox to any computer you want to sync files with (You’ll need to sync these computers with your account as well)
• Simply save files to your Dropbox folder. These files are saved on your computer, sent to Dropbox’s own remote servers, and synced with all other authorized computers. That means you can access the same file from any of your authorized computers! This ALSO means you can access your files remotely from any computer just by logging into Dropbox from its own website.

I see Dropbox as a sort of USB drive. What I like about it is that it’s effortless: all I need to do is save my files to one folder and then I can access them anywhere. After signing up with Dropbox I found out one more perk: Dropbox will back up any file you save to its servers.  Usually, when I update a file and save it I’ve “lost” the older edition of the file, unless I saved the new file under a different name.  With Dropbox, I can log in to my account online and view all older files that have since been replaced.  So if I want to access an older version, Dropbox backed it up for me!

See all those files? Each one is a back-up! I love this feature.

Another feature is folder sharing with other Dropbox users.  I can share a specific folder in my Dropbox account with another Dropbox user.  This could be a nice way to share group documents (no more sending Word documents through emails), or perhaps photos with family and friends. I have yet to fully explore this feature, but hopefully after I convince some people to sign up I can try it out.

Dropbox comes with 2 GB of storage free, and also provides paid plans if you’d like more. I think this is a great tool for anyone who works on more than 1 computer, and for any user that wants to access files remotely but isn’t the best with remembering to carry a USB drive with them everywhere.

23 Things #10: Image Generators

#10 of the 23 Things was all about image generators. I had zero experience with image generators so I’m happy I had this chance to explore what’s out there.

After reading the 23 Things post about image generators, I browsed The Generator Blog to get some ideas about image generators to try. As a Mad Men fan, I was immediately drawn to the generator Mad Men Yourself. You can see the generated image to the left: the Mad Men version of me. Glad to see I’m still drinking coffee in the 1960’s.

I’ll be honest: besides the brief experience with the Mad Men generator, I wasn’t sold on image generators. I suppose I don’t have much need to generate images in my work, so I can’t see the application. Generators were a fun thing to try, but in the end I’d rather spend my free time on the internet browsing my favorite blogs or looking up recipes to try.

Always nice to know what’s out there, though. Next up: LibraryThing!

 

 

Cloud Computing: Resource Review #3

Well, I bunched two resource reviews into one post last time, and it felt rushed. For this week, I’ll take my time and just look at one resource:

Buck, S. (2009, September). Libraries in the cloud: Making a case for Google and Amazon. Computers in Libraries, 6-10. Retrieved October 27, 2009 from Library, Information Science & Technology Abstracts (EBSCO).

This article is not a free resource on the internet, but rather is accessible via databases licensed through the University of Wisconsin-Madison. I linked to a citation in my delicious account, which is linked in sidebar to this blog. For those of you not interesting in hopping over to delicious, the citation to my resource is here.

image by Jean et Melo

This was a positive look at cloud computing, but I didn’t find it one-sided. In fact, I found the title of this article to be somewhat misleading: the author was not arguing that all libraries should look into cloud computing services.  Rather, she highlighted good reasons why some users and libraries should consider cloud computing, but also some reasons why cloud computing won’t always work.

First, Buck begins by trying to describe what cloud computing is. I was relieved to see that she also couldn’t find a workable definition. It seems that the term “cloud computing” really does mean different things to different users, and we’ll have to leave it at that. She focuses on cloud computing by looking at services provided in the cloud, in particular Google Apps (or the “Google Suite”) and Amazon Web Services. The Google Suite includes Google Apps, which can take the place of downloaded software such as Microsoft Office, and Google tools such as Google Calendar and Google Mail. Amazon Web Services offer a different service, by providing online storage space for a monthly fee. This storage service is useful for users who want to access their data from anywhere, and need a fast (and reliable) service.

How can libraries use these cloud computing technologies? For me, seeing a library use Google Suite was a bit easier to see than Amazon Web Services, although I do not work on the tech side of library services, so I have no idea what kind of data storage concerns library systems face. Buck discusses how librarians can use Google Docs to easily share documents with coworkers and access documents from home computers, use Google Calendars to set up meetings, and Google mail to communicate. Relying on these services instead of purchasing and downloading similar software for library computers can save a library a lot of money, due to the cost of the software and storage consideration on local computers.

Speaking of storage, Buck notes that Amazon Web Services may work for libraries that wish to “free up” some bandwith by moving larger files to a fast, reliable server such as Amazon Web Services so that patrons using the website will not face a clunky, slow website. This is definitely a plus! Cloud storage services offer a quick and efficient way to store information that, by storing on your own servers, could slow the rest of your website down. However, the author raises a good point about long-term cost: while cloud storage is not horribly expensive, the annual costs to store information in a cloud could wind up being greater that storing on your own servers. Upfront costs to create large local server space may be great, but these costs could decrease with time.

This article does present a good overview of the pros and cons for using certain types of cloud computing services in libraries. While there is an introduction to cloud computing in there, I don’t think it’s the best introduction to the topic. However, if you’re looking for a good introduction on cloud computing in libraries, look no further!

23 Things: RSS Feeds and Readers

 

Things # 8 & #9 are all about RSS feeds and RSS Readers. RSS feeds are something I use every day, so I’m very happy talking about them. They are probably the most useful of the 23 Things for my personal and professional life.

RSS stands for “Real Simple Syndication.” I’m no expert on the technology, but here’s what I know: Websites are available through an “RSS feed.” Some websites even offer multiple feeds for different topics. Using an RSS reader, I’m able to save all the RSS feeds I want to read. Later, I can just go to one website to check all the updates for all of these websites, combined. My RSS reader allows me to organize different feeds into different folders. 

I use Google Reader as my RSS reader. #8 of this week is to open a Bloglines account. I do have a Bloglines account, but I never use it. I find that it does not update all RSS feeds are regularly as my Google Reader does. When searching for information on the differences between the two, I found a number of articles about Bloglines and how users are leaving to different, more reliable services. 

I have also users Newsgator, and RSS Readers that are not web-based but rather installed on my laptop, such as Vienna. I enjoyed Vienna but decided not to continue using it, since I don’t always check my RSS feeds on the same computer. 

I mentioned I use RSS feeds for professional purposes. I find it much easier to keep track of developing news in the library and legal fields with my RSS reader: I find relevant RSS feeds on legal news websites, library blogs, and through blogs Google Reader recommends when I log in. In discovered another useful site for RSS feeds in another SLIS class: LibWorm. LibWorm is a specialized search engine: It searches articles from specialized RSS feeds. I am also able to browse articles based on subject and category, or save a RSS feed to use in my own reader. I like to think of LibWorm as a specialized search engine, with the content all coming from submitted RSS feeds that were pre-approved by users.  Very cool!

And that’s it for my exploration in RSS Feeds and Readers. Next up: Image generators! I don’t think I’ve used these before so this should be interesting!

Technology . . .

#7 of the 23 Things is to post to my blog about anything technology related. Where to begin? There’s so much I could post about, it was hard to choose just one topic. I decided to post about a something I’ve heard a lot about this week, and one that really interests me, since I studied this topic this past summer for a previous SLIS class – e-readers.

More specifically, I want to talk about Barnes and Nobel’s new e-read, the Nook:

I’m an avid reader, and I also enjoy learning new technologies. I’ve been following the e-reader trend since Amazon first introduced it’s Kindle with great interest.  My thoughts?  People seem to have really strong feelings about e-readers: some think print books are the way of the past and these new reading technologies should be adopted; others think e-readers will never replace the printed book, and another group think electronic books are the way of the future, but e-readers will not catch on since other devices–such as netbooks and smartphones–can have multiple functions while an e-reader cannot. 

I personally think e-readers have a future, but they can’t replace everything. I would love to carry books with me electronically, but hate reading on computers. I enjoy the experience of getting swept away in a story and think reading on a laptop greatly diminishes that. This is where an e-reader could be handy. The only reasons why I haven’t purchased an e-reader yet:

• Too expensive. As a graduate student working two jobs, I simply don’t have $200+ to spare on a device I don’t technically need.
• User restrictions. Readers like the Kindle and Sony e-Reader have restrictions on the number of devices that can access a purchased e-book, in addition to publisher restrictions on the number of downloads available. Sharing e-books with friends was forbidden.  Essentially, I would be licensing titles to read on a restricted number of devices, not purchasing books. I would be okay with this to some extent, but the restrictions felt too strict for the amount of money I would be investing. 

Along comes the Nook. The Nook is scheduled for release sometime in November, and I am cautiously excited. The Nook advertises its ability to share e-books with friends, as well as it’s compatibility with certain library e-book lending programs, such as NetLibrary. (Which, by the way, the Sony e-reader also offers). While it’s restrictions seem to be a bit more user-friendly that current e-readers on the market, it’s not perfect. For example, the Nook’s lending capabilities Barnes & Nobel are advertising turn out to be misleading, as users can only lend a book once. 

Despite the misleading advertising regarding lending, I think the Nook is a step in the right direction. By offering more broad rights with regards to e-book purchases, I’m sure other publishers and e-reader providers will follow. I hope the Nook will also warm up to libraries using the Nook and e-books purchased from Barnes and Noble. Libraries that have experimented with lending Kindles or Sony readers have, so far, led to mixed results.

And that’s my thought on technology for the day. Next up: RSS feeds and readers!