Friday, June 6, 2014

Final Maymester Project

May has definitely been a whirlwind semester, but I hope everyone's enjoyed it! Here's my final assignment; it's on print-on-demand and whether or not it's a good fit for libraries. Hope you all have a great summer!


Print-on-Demand Books: Changing the Library As We Know It?
Introduction
As digitization progresses and allows users access to a wealth of materials at their fingertips, these users often prefer the works be returned to a tangible form when utilizing them. In this spirit, print-on-demand (POD) was born. While libraries, both academic and public, employ this service, they have also discovered other creative uses for it, and many of POD’s early investors imagine this technology may play a major role in the library’s future. POD in libraries could potentially cause a shift in digital licensing, alter the size and form of library collections (possibly even eliminating the print ones), revolutionize the publishing industry, and help transform the library into a Maker Space and community pillar. However, POD is still a new technology that very few libraries have tested thus far; the bugs (and the cost) are still being worked out. Is the emerging technology of POD a good fit for libraries?
Literature Review
In 2011 when David Rapp wrote “Espresso Print-on-Demand Book Machines Making Inroads at Public Libraries,” less than a handful of public libraries owned an Espresso Book Machine (EBM), a distinctive contraption that prints books on-demand in a matter of minutes. On Demand Books (ODB), the company that produces and sells EBMs, offered libraries a choice of purchasing the machine outright or of opting for a less-costly concession agreement, in which ODB rents the library space, hires its own staff to run the machine, and kicks back a percentage of its profits to the library.
The EBM pulls from a database of over six million public domain and backlist titles, but it also offers the capability to print self-published material. Using EBM, a 200-page book will run the user about $10, but self-publishing a book of the same size is much costlier - around a few hundred dollars. Sacramento Public Library’s Director Rivkah Sass views this self-publishing service as a way of connecting with the community; she noted that POD has great potential for local groups, like “historical societies, genealogical societies, writers groups and schools” (Rapp, 2011). 
Edmund Chamberlain’s “Investigating Faster Techniques for Digitization and Print-on-Demand” delves deeper into evaluating POD for an academic library. Cambridge University Library (CUL) created a workflow concept to streamline the process of digitization to printed book, surveyed library staff and students to assess their interest in utilizing digital copies and POD (finding both groups overwhelmingly receptive of these services but expecting to pay low, reasonable prices for them), and then presented the workflow to the library staff. Having received an enthusiastic reaction from staff and students, CUL evaluated the EBM to use for POD.
The only aspect of the EBM more impressive than its ability to print and bind books rapidly is the expansive collection of digitized works that is part of the package. ODB’s package grants users access to digital copies from Google Books, the Internet Archive, anyone who publishes through Lightning Source Print and allows access to their works, and many specific publishers who allowed such permission, including CUL itself. While CUL’s research found POD’s user cost to be within the range students and staff requested, it showed the quality of prints sometimes left something to be desired. The research also indicated the machine should be relatively easy to run and require little maintenance.
Theoretically, POD could render a library’s large, print collection obsolete, but CUL found its collection had few redundancies with ODB’s digital one. The research also suggested that POD may positively impact current services; it could replace lost, damaged, and worn materials, quickly and inexpensively fulfill ILLs, and even create bound course packets students require for classes. In the end, CUL decided against purchasing an EBM for now. They felt it too costly when already overwhelmed with maintaining current services and their collection and preferred to wait until EBM gained popularity and declined in price.
Unlike CUL, after much research, Rick Anderson decided to invest in an EBM for his library at Utah State University. In “The Good, the Bad, and the Sexy: Our Espresso Book Machine Experience,” he shares both his positive and incredibly frustrating experiences with the machine and its software. He realized that while ODB offers over 3,000,000 titles available for POD, most are old and out-of-print, not exactly in-demand with most of his patrons. He also found said titles difficult to locate due to the unfortunate combination of a keyword-only discover tool and the poor quality of Google Books’ metadata. Despite contacting ODB about this issue, Anderson does not expect it will be repaired anytime soon, owing largely to the newness of the company and overwhelming amount of content concerned. The main issues with the machine’s functionality are that the glue that binds the spine takes approximately 45 minutes to melt and that Anderson’s institution just happens to be in a desert climate, causing unforeseen issues such as the pages not stacking properly. Fortunately, ODB was able to fix this issue, and the few other technical problems that have arisen have been or are in the process of being solved.
As for the machine’s successes, the library’s patrons have been excited about using POD books but warmly welcomed its self-publishing aspect as well. Anderson notes that EBM-printed journals, which are basically blank pages with a high-quality image from the library’s digital collection printed on the cover, are also top sellers. Overall, Anderson states that he is happy with the purchase but hopes that the product improves over time.
Koerber, on the other hand, views POD as a natural fit for the Maker Spaces into which many libraries are evolving, and he believes libraries’ success with using POD to self-publish can be attributed both to this natural match and to the demystification of the publishing process. In the article “Espress Yourself,” Koerber argues the EBM really shines with self-publishing because the user can take their product from a .pdf file to holding “a copy of their book, warm and real in their hands” (2012) within minutes. POD completely eliminates the publishing company from the publishing process. 
Hands-on creation, the sharing of results and process, post-consumer customization, and the ability easily to manufacture just one of something” (Koerber, 2012) are all ideas that align Maker culture with the self-publishing aspect of POD. The cost of purchasing an EBM still runs over $100,000, which seems rather unideal for most public libraries, but costs are expected to decline, as they did for 3D printers. By keeping the publishing process local instead of sending the digital version to online self-publishing companies, the EBM allows the libraries to connect with these local authors and to see the process from beginning to end. One librarian even hypothesized that in the future, an author could begin his writing project on the library’s site and see it all the way to finish with the EBM, possibly giving the library a copy of their book too. While this idea may be far into the future, many libraries today do wish to offer their users Maker Spaces, and POD would undoubtedly be at home there.
Usage & Application of POD in Libraries
Today, only four public libraries and a handful of academic libraries in the U.S. own EBMs (On Demand Books, 2014). This technology is still very new to libraries, and not very affordable, unless the library has a grant or other special circumstance. The libraries that do have an EBM have had the most success with the self-publishing aspect, but they also use it to print digital copies of books from the database for users who request it, as well as to print journals and notebooks either the libraries or other individuals create to sell. The literature mentions using POD to serve administrative library functions, such as to fulfill ILLs, to supplement course materials, and to use as back-ups for lost/damaged materials. However, the little evidence I did find of follow-through for these ideas suggested that POD was of such little consequence in these instances that it was not really worth mentioning with print copies and self-publishing.
Challenges and Issues
The acceptance and future application of POD in libraries will depend on its ability to overcome both major and minor challenges, the smallest of which being consistently good-quality prints. The pitiful state of the ODB collection’s metadata and interface make finding digital titles a hassle for the user, but the main two issues are the same ones sited over and over again in the literature: popularity and cost. 
With so few EBMs (less than 70 worldwide, according to www.ondemandbooks.com), how can publishers expect to offset their cost by allowing free digital access to the book? Therefore, most decline digital access to the in-print materials most library patrons so desire and would make an EBM worth the library’s money. And it’s a lot of money - over $100,000 - and that will just purchase the machine. Most libraries will also need a staff member to run it, and with many being understaffed and underfunded, extra staff is unlikely. If the cost decreased, it would be more popular; if it were more popular, the cost would decrease. As Rick Anderson says, this relationship “raises something of a chicken-and-egg conundrum” (2011).
Conclusion
POD could change the way libraries look and function; it could help progress the digitization movement, while still allowing users their print copies, and could become an integral part of the Maker Spaces libraries and their communities seem to crave. While this technology’s functions appear to be on track with the library’s aspirations, I have to agree that cost and lack of relevant digital materials cripple POD’s potential. Currently, most of the venues that own EBMs are bookstores (On Demand Books, 2014). If more bookstores buy the machines, I can see the cost decreasing enough to be more affordable for libraries. Even then, they will have to decide whether the self-publishing aspect is worth the price tag when the digital collection is not up to par. If costs decline and libraries invest, POD may one day be as permanent and popular a fixture in libraries as copier machines.


Monday, June 2, 2014

The Home Stretch

Maymester is almost over, y'all, and today has been all about the end-of-semester squeeze! I've been attempting to read and reply to the posts for this week's Discussion 12, and I've been working on my research paper, which I'm doing on book printing on demand (POD, as I've affectionately started calling it). So far, I've really enjoyed researching the concept; the challenge for me today has been keeping my head on my work and not getting distracted by things like getting to go to the beach when I finish. How's everyone else's papers, posts, and posters (yep, we have to create one of those too for this paper) coming?

A short video on POD: https://www.youtube.com/watch?v=-Lnk1Q87fr0

Saturday, May 31, 2014

Reaction to CMS Interview




In our MLIS 7505 class this Maymester, we’ve been learning about Content Management Systems (CMS), such as Joomla and Wordpress. For this assignment, I interviewed Mark, the librarian in charge of managing the library’s website for my local library system. He was kind enough to conduct an email interview with me, and I was surprised by some of his answers to my CMS questions.


I was most surprised to learn what little experience he had with CMS prior to running the library’s site. According to Mark, he had never used a CMS before, even when working on his MLIS. I have to wonder if this sort of experience is common among those who now run their library’s website or do their social media. Is learning to use a system like Joomla or Wordpress a skill many tend to learn while on the job? Fortunately, these systems do not normally require the users to write their own code and can be somewhat easily taught to users with decent computer skills. While Mark has never used Joomla, which he says would probably be his second choice, he uses Wordpress to run the library’s website. When I asked him about the learning curve for Wordpress, he noted that it was fairly simple to learn to use. He is fairly comfortable around computers, as many MLIS graduates are, and he did get some pointers from the library’s IT personnel to start him off. He also pointed out that Google was very useful when he was stumped or had questions.


I was also very interested in how much time maintaining CMS takes on a regular basis. For Mark, updating the website is just one part of his job; he is also the branch manager, which means that his job has all the facets to it the other branch managers in the system have, plus the added duty of website maintenance. Therefore, before the interview, I thought the website must not take up too much time - maybe once a week or so. I was very wrong. According to Mark, the website needs almost daily updates. He says that the actual work of changing the content, like taking down posts or uploading new images, takes only seconds or minutes. The part of this process that is most time-consuming is creating various images, such as fliers, posters, and other images, in programs outside of Wordpress (like Publisher) and then having to save them as .jpg files to upload in Wordpress. Fortunately, the uploading of these images into the CMS is usually very quick. After using Joomla for this class, I can see how once the main format of a website is created, going back and making updates and content changes can be fairly simple. Still, I am surprised the site needs updating so often, but I think this constant need for updates shows the system has lots of activity, lots to offer its patrons, and a good online presence.


Mark has been managing our library’s website for several years now, and for my final question, I wanted to know if he has any advice to offer those of us who are just beginning with CMS. “Don’t be afraid to experiment,” he says. I couldn’t agree more. After all, isn’t that what making our own Joomla sites was all about - not only learning to use CMS, but learning how to customize it to fit our needs, both aesthetically and contextually? He even mentioned the plug-ins that are available for Wordpress, similar to the ones Joomla uses. His advice also makes a good point because during these years as MLIS students, this may be our only chance to really experiment with CMS before it becomes part of a resume or job description.

From my interview with Mark, I learned that those using CMS do not necessarily have a lot of experience and that keeping CMS updated, like that used to run a website, takes frequent, yet not usually time-consuming, work. While CMS does not require an IT degree, it does take being comfortable with computers, the patience to learn new systems, and the courage to experiment and try new things. And if you get stumped or have questions, there are probably plenty of other MLIS professionals who use the same CMS, who have probably been in the same boat, and who can offer their advice.

You can find the link to this Google Doc here

Transcript of Email CMS Interview

I recently conducted an email interview with Mark, one of the branch managers of my local library system who happens to run our website through Wordpress. Here's the transcript (I will be posting my reaction to it later today):


How and where did you hear about CMS (Content Management System)?      

The first time I became aware of them was when I took an information technology class for my MLIS. 
    
Do you like using CMS for the library website? What are its advantages/
disadvantages?

I have only used a CMS to update the library website. In my information technology class we had to build a website from scratch, but that was the only time I have ever done that. Using a CMS makes it a lot easier to add and change content. It saves time because you don’t have to manually enter code.

Have you used CMS for any other purpose? If so, what?

No.

What is the name of CMS you are using now?        

Wordpress.

What are the important benefits or advantages of CMS you are using now over another CMS system you’ve used in the past?        

Not applicable.

How was the learning curve?

       It didn’t take me very long to learn the functions of Wordpress. I had Dixie
       show me the basics but most functions are fairly intuitive. I have been using
       computers pretty much all of my life, so I am comfortable doing some
       advanced functions. Also, if you have a question about how to incorporate
       something using Wordpress, doing a quick Google search will usually give you
       a correct answer.

If you were to use another form of CMS to run the library website, what would it be?

I have heard of Joomla, but I have never used it. That would probably be the first CMS I would try if I had to use a different CMS.

How often do you have to update the content and how much time does it usually take?

I update content almost daily, usually to take down posts or images of events that have passed. Updating or removing content usually doesn’t take very long, just a few clicks and hitting the backspace key is all it takes. Creating the content, e.g., creating a flier in Publisher then saving as jpeg, usually takes up the majority of the time. Upload the image to Wordpress and inserting it in the proper location usually takes less than a minute.

For this class, we’ve had to use Joomla to build and manage a site. Do you have any experience with this CMS platform and, if so, what did you think of it?
No.


What advice do you have for CMS beginners?

Don’t be afraid to experiment. Wordpress has lots of great plugins that can enhance your website. Also, Google is your best friend when it comes to troubleshooting.

Wednesday, May 28, 2014

Staying busy

Summer reading has started, and working in a public library has just gotten that much crazier! However, I did manage to find the time to convince a branch manager who is in charge of his library's CMS to interview for Assingment 3. Stayed tuned for more. 

Monday, May 26, 2014

Joomla

Oh, Joomla, thou art frustrating. I watched the tutorial but ended up having to play it again almost step-by-step as I worked on the site. I really wish I had just started building the site while watching the first time around. I'm sure that Joomla is one of those things that gets easier the more you use it; I'm sure the more pages I created with it, the more I would like it. However, I didn't find it to be very intuitive or user-friendly.

I created a relatively simple site for this project for a fake institution, which I've dubbed "Sunnyville Public Library." Of course, a real library would require more than 2 pages to be very helpful to its patrons. On the Home page, you can find very general info, such as the mission statement and hours. The other page I created consists of information for the library's 3 book clubs, which are three articles I ended up featuring as was demonstrated in the webinar.

I found it a little frustrating that the software does not allow me to edit a whole page in one place. If I want to remove tags or change the location of items on a page, I have to utilize several different areas of the site. To get everything exactly the way I want it, I almost would've rather coded it myself, but coding does take more time.

The thing I really liked about Joomla (and that I personally do not know how to do when coding) is that it offers templates with responsive layouts. When building a site, the aesthetic appeal and ease with which the user can view the content is highly important when it comes to usability, and this feature allows the user to see the content relatively well without having to enlarge or scroll left to right on any size screen or device.

To view Sunnyville's library site, click here.

Sunday, May 25, 2014

Long Weekend

Hi, all. Today has been a bit of a catch-up day for me; this holiday weekend has been busy, busy, busy. I enjoyed reading the discussions this week for Module 2, and I've been watching the Joomla tutorial. I wish I had realized before I started it how long it is! Anyways, I hope you all have a happy Memorial Day tomorrow!

Wednesday, May 21, 2014

Finished Wiki!

Today, I finished my wiki! Its purpose is to give both general information about the library, as well as the most current news and event info. Hope you all enjoy:

Tuesday, May 20, 2014

Working on a Wiki: Choosing a Host Site


In my last post, I talked about the characteristics of my library. To begin this post, I'd like to explore the library's wiki needs:

  • is a FREE hosting site
  • does not require coding knowledge (WYSIWTG)
  • is easy to update and to maintain
  • is professional in appearance
  • shows recent changes
When I entered the above requirements into wikimatrix, it returned 23 results: 


After comparing them side by side and flipping through a few wiki examples of the free hosting sites, I chose to use Wikispaces. For now, my library wiki is still a work in progress, but I will keep you updated!

Monday, May 19, 2014

Working on a Wiki: Library Characteristics

So, probably like many of you, I've used Wikipedia about a gazillion times over the years, but when I first viewed the assignment for creating a wiki, I wasn't really sure what that meant. My local library is Houston County Public Library. I work at the Perry branch, and therefore, it is most definitely the library I use most often. I figured the best way to go about it is start with the library's main characteristics:

Library Type:  Public
Population Served: Houston County, Georgia (146,136 people as of 2012)
Budget: $167,850 (for 2014)
Library Locations: Perry, Centerville, and Warner Robins

I know there will be at least a $40,000 budget cut for the upcoming fiscal year. Also, this county always seems to be growing, and I know the population is probably a little larger than this number lets on. I would also venture that Centerville and Warner Robins's libraries have more patrons than Perry due to their proximity to the air force base and simply being larger population-wise.

In my next post, I will discuss my library's requirements for a wiki and utilizing wikimatrix to pick a platform to host it.

Friday, May 16, 2014

Hi! I'm Lauren, and I'm writing this blog as part of a class assignment for grad school. I've really enjoyed the tech classes I've taken so far for MLIS, and I'm excited to learn more about how libraries use technology to interact with their communities. Although, Maymester does seem like it may be crazy hectic, and there's an awful lot to fit in in that short time span.

I work in a small public library, where we use sites such as Facebook, Wordpress, and Twitter to promote our library and its programming. I've seen social media used in some pretty cool ways, like having library-related trivia contests or sharing relevant library news and updates, and I'm excited to learn more about how libraries can use technology to their advantage.

I use Web 2.0 on a regular basis. I'm on Facebook more than I should probably admit, and I also follow several blogs and have accounts on Pinterest, Instagram, and other social sites.

From what I can tell, MLIS 7505 aims to cover many different ways we as future librarians will be actively using the technology available to us to promote and build our libraries. I think that's probably the most exciting thing a library student interested in tech could possibly learn - real-life, practical applications for it.