Adventures in technology at the library.

Sunday, May 31, 2015

CMS Profile: OU Campus in Action

For this week's assignment, I chose to follow up with the topic of a previous post and investigate the transition between my library's current website development tool, Adobe Dreamweaver with a tiny bit of help from Drupal for the library's internal staff Intranet, to the university-wide mandated OU Campus CMS.  As I discussed in my previous post, our website librarian is not too keen on the fact that he was not (and continues not to be) consulted in matters of decision-making and that he will have to submit every change to a higher power in order to edit the website.  I sat down with him this past week and talked to him about this new process and how he liked working with the new CMS.

My questions and his answers are paraphrased for the sake of cohesion and flow.


Me:  Tell me why you were hesitant about the switch over to OU Campus.

[Website Librarian]:  It's nothing personal against OU Campus itself.  In fact, I was already considering switching to a CMS before this process started because it makes it easier to have multiple people working on the same site at the same time.  That's one of the benefits of a CMS - you can set multiple permissions for different contributors so that I can work on more advanced features of the website using code and other librarians who might not be as familiar with web design can still edit content.  We aren't able to do this with our current system, Dreamweaver, which uses mostly code.  So in that respect, it's great that OU Campus allow multiple permissions levels - the problem is that my own permissions are set so low by the university web master.  Here is the chart of permissions level for OU Campus - our web master is the highest, a level 10, and I'm only a level 5, which is in the Editor category.  This means I can edit content, but I can't really manipulate the design or functionality of the library website, which means I have to submit all change requests through the university.  As the library's website manager, I'm essentially going from having complete control over our site to only being able to edit a few boxes.


Me:  What CMS were you considering before the university told you it had to be OU Campus?

[Website Librarian]:  I was considering an open-source CMS like WordPress because I've worked with it before in the past.  I've also worked a bit with Drupal, but found it to be clunky.   


Me:  Any reason you were interested in an open-source CMS over a paid one like OU Campus?

[Website Librarian]:  Well, mostly I was thinking about cost.  But with open-source CMSs you can usually customize sites to a greater degree.  However, third-party modules and extensions add in a wild card element that doesn't always work the way they're advertised to.  With a paid CMS you have a vendor there for IT support, but in essence the functionality is the same as with an open-source CMS.


Me:  Can you tell me about OU Campus' functionality and workflow?  What is its learning curve?

[Website Librarian]:  If you've ever worked with a CMS before, OU Campus is pretty easy to learn.  And considering I don't have very many permissions, there wasn't much for me to learn at all.  Here's what it looks like when I go to edit a page.

I can't alter where the boxes go because that's above my permissions.  I'm allowed to edit anything with a green box over it.  As you can see, I also didn't have any control in how the menu bar for the website will look.  This menu bar is standard on every single university web page, so the library's menus will have to go on the side now.  I'm allowed to add new content to these menus within the range of a few templates.  These are the options I have below.


I can add pages, site sections, and library department pages.  There's only one top level page - the library's main page - so I would never have to add another page like that.  Here's what the "back end" looks like for me.


Here's where I can store elements of the pages before I publish them.  OU Campus has several staging areas for sites before they're published on the web.  In addition, while I'm working on a site I can "check it out" to myself so that no one else can edit it while I'm still working on it.  When I'm done, I can "check it back in" to allow others to edit it.  It keeps people from stepping on each others' toes.  Another feature is the creation of "assets".  If I create an asset, say the Library Reference Chat Box, I can easily add it to multiple pages at one time.  


Me:  This looks pretty user friendly.  Much easier to use than the product we tried, Joomla.

[Website Librarian]:  It is easy to use, but again, like I said before, with my permissions level I am not able to edit any of the HTML, CSS, etc.  If I want to edit something beyond what I've just shown you, I have to put in an order for the university web master - and they won't always approve it.


Me:  Are there any other features of OU Campus you want to talk about?

[Website Librarian]:  Like many current CMSs, OU Campus uses what's called "responsive design" - this means that you only have to design one website and it will work for any size screen or mobile device.  When I upload a picture, I designate it to be "medium" or "large" instead of a certain pixel width.  This tells the program how to resize it so that it takes up the same percentage of the screen no matter how small the screen is.  This feature still has some flaws so it doesn't work perfectly, but it makes it easier to make a mobile site.  What I don't like about responsive design is that it makes scrolling almost impossible to avoid.  With our old website, you could view the entire homepage in one browser window on a normal sized computer screen.  Now, you have to scroll down to see the part on the bottom.  I don't like that.


Me:  Are there any examples of library websites made with OU Campus you can show me?

[Website Librarian]:  Yes.  The University of Tennessee at Chattanooga made their entire site, including the library, with OU Campus.  Georgia Regents University Libraries as well.  You can see that one of the distinctive features of the OU Campus design is the big picture across the top of the page.


Thursday, May 28, 2015

Head in the Cloud

It's hyperbole, but it's almost entirely true that I keep much of my head -- or at least the important contents -- in cloud storage of some sort.  My embrace of the cloud began after a series of unfortunate coffee spills left my poor laptop gutted and left out to dry in the desperate hope that not everything was erased.  I was able to get the thing on life support long enough to extract a few files, but a lot went the way of the dinosaurs.  I started using a few different types of cloud storage, which I'll discuss here.

Dropbox


Dropbox is one of those services that I hesitated before trying, but now completely rely on.  I was concerned about privacy and permanency of cloud storage for starters.  How did I know this service wasn't just some fad that was going to go out of business in a year or two and delete all of my files with it?  I'd had this problem using photo gallery sites in the past that had gone out of business and deleted my (thankfully, backed-up elsewhere) photos along with it.  I've since come to trust Dropbox for files that won't get my identity stolen, like school papers, creative writing file back-ups, and back-ups of some pictures.  I especially like uploading PDFs of course readings into Dropbox so I can read them on-the-go on my phone.  On my computer at home I have Dropbox's app downloaded so that I can - you guessed it - drag and drop files into it directly without any fuss.

With the free account you get 2GB of storage, and thus far I haven't outgrown it.  I'm not sure I'd ever need the $9.99 1TB storage plan, which is the next upgrade, or the $14.99 business unlimited plan.  But either of those seem relatively affordable for a library who might want to have some cloud storage for their staff.  

Google Drive

Google Drive
Formerly just Google Docs, Google Drive was one of the first cloud storage and collaboration software programs I used.  The best part about Google Drive is that if you have a Gmail account (which many people do), you already have this built in.  No separate passwords to remember!  Inside Google Drive is the original Google Docs, which was a life saver in that post-college pre-job period where I couldn't afford Microsoft Word (which also has a new cloud storage service called One Drive that I haven't tried yet). There is also a basic spreadsheet and slide sharing service.  The things I don't like about Google Drive for my personal use are a bit nit-picky.  I don't like how you can't right-click to copy and paste (instead you have to use keyboard short cuts) and I don't like how all the formatting and fonts available in Microsoft Word get converted when you upload a Word document to Google Drive.  This is pretty petty when you consider that the service is free, so I'll leave it alone.  One thing that does need improving is their mobile app, which got all kinds of confusing when they decided that Google Drive and Google Docs were like, two different things now.  My family uses a Google Doc to keep up a running grocery list that we share with each other, which is our favorite use for it.  I also use Google Drive all the time for collaborating with classmates.

As far as organizational use, our library has been relying on Google Drive pretty heavily during its consolidation with Southern Polytechnic State University.  The downside is that I have to use my personal Gmail account instead of my work email, which seems iffy to me.  I don't like mixing personal life with business, especially when it comes to files.  Libraries that use Gmail as their official work email should have no problem though.  The other problem is that unlike a Dropbox, Google Drive really doesn't work as intended if you only have on institutional account.  To collaborate, comment, and otherwise edit documents together everyone ideally should use their own account.

Carbonite


The final program I have experience with is Carbonite, a service that will back up your secure documents and entire computer for a fee.  We tried doing this with our home computer, which is chock full of years and years worth of high-resolution pictures, home videos, and downloaded music and movies that we store in iTunes.  I have heard that a lot of people have success with Carbonite, but during our first year of service the company was not even able to upload half of the contents of our home computer.  Granted, our computer has external hard drives full of data as well, so we are an extreme case of data hoarders.  If you're interesting in a solution to backing up secure files, I'd look into this as I've heard others have had positive experiences.  The basic personal plan is $59.99 a year though, so if your files aren't that secure you might consider going with a free cloud storage service like Dropbox instead.    




There are limitations for cloud storage, but so far I have appreciated the ease of access to my information as well as the ability to easily share the information with others.  I can access my information on my work computer, home computer, mobile device, and even on a public computer.  Neither software requires downloading anything, although Dropbox does have a downloadable option.  I am in the market for a robust, high storage photo back-up site if anyone has any recommendations?

Tuesday, May 26, 2015

Does Your Link Stink?

Today I'm going to be talking about all the fun ways to jazz up your site links in social media.  Because no one really wants to type in a link the size of a Tolstoy novel.

QR Codes


I don't know why, but QR codes have not really caught on with me.  I admit they make sense for translating something physical into something digital - say if you wanted to create a business card that had a QR code for your website on the back so people could go directly there without the possibility of typing in the address wrong.  I just have never really bothered with them until now.

I made this nifty hot pink QR code for my blog using the nifty BeQRius service.


The service allows you to customize the look, shape, and color of your QR code (hence the hot pink) so that you can make it unique for your brand.  They also allow you to track usage of the QR code so you can get statistics on how effective certain advertisements are.  Most of these services are not free, mind you, but if you were running a business (or starting an aggressive marketing campaign at your library) this service might be worth investing in.

Bitly


Another service that used to do QR codes (but no longer, apparently) is Bitly.  But their main service is link shortening, which is AWESOME for Twitter.  It can take a link like this:

http://www.architecturaldigest.com/architecture/2013-11/most-beautiful-libraries-trinity-college-mushashino-bodleian-sainte-genevieve-article/_jcr_content/par/cn_contentwell/par-main/cn_pagination_container/cn_image.size.libraries-22-st-florian-monastery.jpg

and turn it into this:

http://archdg.st/1J2unwH

Which one helps you with your 140 character limit?

Some links, such as the Architectural Digest link above, even get their own branded Bitly link that resembles their company URL, but the majority get the generic bit.ly link.

Picture Links


But while we're talking about links, did you know you can turn a picture INTO a link on your blog?

Click the picture!
Simply upload or paste the picture into your blog editing form, highlight it, and then click the "Link" button at the top of your editor.  You can add in the URL just as you would for a link behind text.

Yay for linking!

Monday, May 25, 2015

#JoomlaProblems

This is going to be a lengthy post because after a traumatic experience such as this, I find it helps to talk out all of my feelings on the subject.

For this assignment, we were tasked with the creation of a website using the open-source CMS Joomla.  I decided to build an author page for my Mom, a published romance author whose own webpage wasn't looking that great.  (She made her site using a paid version of WordPress, by the way.)  Let me break down the experience below.

We were using the demo version of Joomla that did not require the full download, which I believe may have contributed to some of the initial confusion when the demo videos did not reflect the menu screens I was seeing.  However, I was able to follow along and create some of the basic pages such as the home page, products page (in my case "Books"), and contact page.  The basic process of adding any page to Joomla is their 1.) Create 2.) Add 3.) Show method, which creates lots of opportunity for fun errors.  First, you have to create a Category, such as "home page stuff" or "books page stuff".  Of course, you'll want to name this as closely as possible to your Menu and Article titles so you can confuse yourself later on /sarcasm.  After you create your category, you write "Articles" that contain all of the content you need.  I downloaded the JCE Editor WYSIWYG extension to help out by making my article creation page look like a familiar blog word processor.

JCE Editor WYSIWYG extension in action
The demo also showed us how to style our text into headings that we wouldn't be able to customize in our free demo version, but wouldn't be able to realize that until much later in the process and lots of hair pulling.  However, the basic process of typing text, adding pictures, inserting hyperlinks, etc. was fairly standard for blog software that for some reason did not come standard with Joomla.  My only confusion at this point was I wanted to add a Facebook link, but that required an extension that was not working with my demo version, so I settled for the cheap solution of finding an image of a Facebook button, highlighting the button picture, and making it a hyperlink to her Facebook page.

After you have created the Article and named it - you have to then assign it to a category you've already created - in my case I had created one for About that contained this homepage and the page for the About Evelyn section.  After you put the article in a category, you have to create a Menu to assign it to.  This is the Create (category), Add (article), Show (Menu) process.  It seems pretty redundant to assign an article to both a category AND a menu, but it made sense later for the Books page, where instead of assigning individual articles to a page I basically told it to display all the articles assigned to a particular category.  This method is called the Blog Category template for Menus, and it's probably the feature that was the nicest about this process.

The "Category Blog" makes a great Products/Books page
Thankfully one of the video tutorials specifically explained how to create this Category Blog page, which allows you to show small images and a brief description of an article that then links to a fuller article.  It's perfect for displaying a list of things, such as products or books.  As with my Facebook link frustration, the Amazon Cart required a type of extension I didn't have, so I had to settle for writing out the word Amazon and turning it into a link to her book on Amazon.com.  All in all this page took a TON of work, but it's the page I like the most.  Clicking on the title of her book brings you to a bigger picture of the cover, a longer description of the book, and an excerpt.

You can use this same Menu template to create an Events page, however you have to sort the stupid things manually because Joomla does not have a built-in calendar extension that can intelligently read dates and sort by them.  Instead I used it again to create the Just for Fun photo gallery page for the website.  I could have done the same process I did for the books where each image was just a small thumbnail that linked to a larger version on another page, but because of the sheer amount of images I wanted to upload (12) that process was much too involved.  The result was an image gallery with static images that do not let you click on them.  Sorry.  There were several photo gallery extensions I tried to download that did not work - I'm assuming because I did not have the full version of Joomla.  I really think that Joomla ought to come standard with an image gallery, as many other free CMS programs do (such as WordPress, for example)

"Category Blog" menu template used to make a Poor Man's Photo Gallery
The final page I made was the Contact page, which I used the video tutorial to make.  Unlike the other pages, Contact pages do not use articles, but rather a special component that makes them confusing as sin.  My main problem was that as an author page and not a business page, I didn't want to include a mailing address, so I just put the email address in the Contact form and tried to hide the headings that went above the missing Contact information.  This is actually impossible to do (at least on the demo version) unless you find the CSS code section and do a "Language Override" to tell it not to show the other headings.  I only found out how to do this by Googling the problem and finding this set of instructions.  It worked.  I don't know how, but it worked.  So let's leave it at that.  I also followed the video's suggestions and installed the reCaptcha plug-in that prevents robots from spamming the contact form.  I installed it, but was unable to test it because the Contact Form does not actually work.  I don't know if I did something wrong or if this is another symptom of having the demo version.  I give up.

Contact Form with reCaptcha Plug-In
(
Spoiler alert - it doesn't work)
The final thing I wanted to do was customize the look of the website.  This is probably one of the worst features of Joomla.  Unlike basically every other free CMS that I've used (Google Sites, Blogger, WordPress, etc) you cannot just drag features of the webpage around to where you want them.  If you want to create a column on the right or switch the position of the menu bar with the header, you're going to have to go to this weird version of your website by typing "?tp=1" after the URL to get a confusing screen that looks like this:

Magic secret page that reveals module positions - SO USER FRIENDLY, RIGHT?
After you determine the position numbers, you can then go back in and edit what position certain modules like the image bar, menus, or columns go in.  I was able to find the image bar they were using and replace it with a border I had created.  I duplicated the image bar and put it at the bottom of the website as well.  Then I tried to do something I thought was going to be relatively straightforward - add a header image instead of the site title.  So I created a very basic image header in PowerPoint that was the size I figured was the correct width for the website (1020 pixels, or about 14.72 inches).  Except whenever I tried to upload the header image into this stupidly basic and unhelpful menu, it kept resizing it to 720 pixels wide.

Really? This is the ADVANCED menu?

After yanking out most of my hair, I thought:  screw it - I'll just create another image bar module like I did for the border.  It also only uploads 720 pixels wide, but it did let me stretch the border to the right width before.  So I did this, which made my header distorted a bit because it had degraded the image quality (yay...), but at least it fit across the width of the screen.  However, then it wouldn't let me delete the site title from the top.  After lots of Googling and frustration, I found out that the reason I couldn't edit some of these more advanced functions was because I was using the demo version.  I really, really hope that on the full version you would be able to edit some of these features or maybe even *GASP* add a background image instead of a plain color.  I'm not even going to get started on the fact that to choose a font for my headings I had to look them up myself in Google fonts without even a preview screen in Joomla.  Wow.  (I mean, they know that every other blog site has a font menu, right?)

A header that is not a header - plus the site title that won't go away
So that's it.  I wanted to add in the WordBridge extension that would allow me to integrate her WordPress blog as a RSS feed in one of the menus, but - again - I could not install it because I was using the demo version.  Ha.  Hahaha.  I give up.

The final torture feature that I wanted to try out was the Akeeba Backup extension that Joomla recommended I download, but somehow didn't come standard with...  Because the video walked me through how to install and enable this feature, I did not have any major problems with backing up my site.   The only weird thing was it told me to download my backup in case something went wrong, but my computer doesn't have program that could read the backup, so I just kind of shoved it into a folder I hoped I wouldn't need later.


Akeeba Backup extension in action
So that's it.  This is my finished product.  So would I recommend Joomla to a friend?  Only if I had a sadistic sense of humor.  The entire point of a CMS - unless I'm mistaken - is to be a cheap way to make website development easier for people who don't know how to use HTML.  This CMS failed miserably.  Its three-prong 1.) Create 2.) Add 3.) Show method is overly complicated for novices and leaves lots of room for user error.  However, most insulting is this software isn't any easier for advanced web designers either because it makes finding and editing the CSS code SO difficult!  The one time I tried I realized you couldn't even use your browser's CTRL + F find feature to find the line of code you wanted, because they put it inside of a little box THAT WASN'T SEARCHABLE.  HA...ha...no.  This combined with the fact that even the most basic extensions that a website would want (WYSIWYG editor, photo gallery, calendar, blog) do not come standard with the software.  All of these features require a plug-in or an extension from a third-party, which opens you up to the risks of downloading something that works terribly or does not play nicely with the other plug-ins or extensions you downloaded.

My advice?  If you really don't know what you're doing, use WordPress or pay for a SquareSpace instead.  It may not be as powerful ultimately, but at least you can throw up a half-way decent and functional site without bursting any blood vessels.

Friday, May 22, 2015

A Site for Sore Eyes

This week's readings on Content Management Systems (CMS) for website development is timely, because it just so happens to our library is getting ready for an upgrade of its own.  For a long time, our library's site operated on its own, independent of the university, with many homegrown features to help customize it for library purposes.  We had a database list that we made from scratch, a suggestion box for book purchases, a widget for our Reference Chat.  Lots of things that the other departments on our university campus would never need.  Our website librarian managed it using Adobe Dreamweaver and the open-source Drupal CMS.  

So of course they left us alone to do our own thing, until someone had the genius idea that our university ought to merge with the university down the street (I see you, University System of Georgia, and your disturbing penchant for cannibalizing your own institutions...).  They needed a new university website, of course.  A new site, for a new U.  That's great and all, except now they're getting a little too nosy with the library site.  Demanding we adopt the university standard.  Insisting we change out our outdated owl icons for the official university mascot.

Informing us we have to switch to their new CMS, OU Campus.

At this point, our website librarian burst into flames.

Up until this time, they had not consulted the library at all to ask about our unique needs.  They seemed to have this crazy idea that they could just build us a page and give it us without ever needing to edit, update, or look the slightest bit cross-eyed at it.  Have they ever actually used a library site?  We are constantly going through new database trials, advertising new events or hours, adding new how-to videos or research guides.  We simply cannot build a website that's supposed to last us all year.

And yet I see their point.  Our website doesn't look nearly as polished as the university one.  Compare for instance:

Our Dreamweaver and Drupal website

vs...

Their far fancier, OU Campus website


So... there is definitely some room for improvement, but I'm still a bit nervous for our site.  All in all, I'm excited to be moving to the university's CMS because I know our library site is going to look so much better.  However, I share the concern of our website librarian because I know we are going to have fight with them kicking and screaming for every little change we want to make unless we can negotiate with them to have more freedom and control over our own site.  I just hope that we can open up the channels of communication and solve this in a civilized fashion.  You know.  Before we're forced to do something drastic, like secede and align ourselves with another university that hasn't already been consumed by us yet...

Wednesday, May 20, 2015

You want to put a Wiki...WHERE?

OK, I will admit that when I was first asked to write about the use of wikis in libraries and explain how I would go about choosing one, my reactions were twofold:

1.  Wait, libraries use wikis?

and...

2.  Wait, there are more types of wiki than Wikipedia?

Sigh.

I mean, how did this happen?  I work in a library.  I use the internet.  I have a Twitter for Pete's Sake.  But somehow the idea of using a wiki in a library context never really occurred to me.  So, as I mentioned in my last post, I did what I do in most situations that confound me.

Was definitely not kidding about that Googling thing.
I came across this crazy meta library wiki ABOUT library wikis that explained that libraries typically use wikis for four reasons:

  1. Collaboration between libraries
  2. Collaboration amongst library staff in a library
  3. Collaboration between library staff and patrons
  4. Collaboration between patrons
I wasn't so sure about using wikis to engage patrons or to allow patrons a platform to interact with each other, but the first two uses seemed like amazing ideas to me.  Having a collaborative workspace to share with colleagues at other libraries, or even at your own library, would be a great benefit to using a wiki.  I found a great example in a best library practices wiki designed for libraries to come together and share information and tips.  

We could definitely use a wiki for staff collaboration at the library where I currently work, for example.  It's an academic library at a university of around 33,000 students, two campuses, and four libraries.  It's difficult to get all of us together for a meeting, or even an entire department, even though much of our daily work affects each other greatly.  I work in the Interlibrary Loan Department, and I have to collaborate efforts with my ILL counterpart at the other campus, the library staff member who picks up books from our Repository library, and the weekend/evening staff person I don't always get to see in person but who helps out with Interlibrary Loan at times.  It would be wonderful if we could use a wiki to keep up with new policies or workflows we are trying and to have a venue where we could ask each other questions.  It would also be a great place to share copyright reports, borrowing statistics, or things like the courier's van schedule.  Because wikis have multiple pages, it might be possible for every department to operate part of the wiki for their own needs.

The intimidating thing for me about implementing a wiki is choosing which one to go with.  Like most libraries, our administration does not often stretch the budget for resources, so a lower cost was a priority.  Using wikimatrix, I input my library's requirements and was recommended to try Confluence.  An example of a Confluence wiki is this staff wiki for Oregon State University Libraries.  Check out this video of Confluence's features in action.



I decided to go with a wiki that offered technical support, was easily edited with familiar word processor features, and was hosted by someone else.  Basically, I wanted something that was easy to use and maintain.  Very few of us at the library have website, wiki, server, etc. experience, and the last thing I want to do is burden our stretched Virtual Services department with more software to keep up with.  I also wanted something that we could customize with our own university branding to match the rest of our official library publications.  Features like a calendar widget or built-in instant messaging were great add-ons.  In addition, I liked how Confluence was private and access was restricted to users with passwords, unlike many of the free wikis available elsewhere.  The downside to Confluence was the cost.  It's free for small teams of 5, which may work at the individual department level (particularly if each unit had one shared log-in), however our library has over 40 librarians and library staff, which can cost upwards of $200 a month.  Still, for the convenience of a product that works seamlessly for such a large number of staff and offers technical support, I believe a subscription could be justified.

Monday, May 18, 2015

But first, a little background

So how did I get into library technology, anyway?

I've never been a specifically tech-y person, but I've always believed that my ignorance of technology should never get in the way of what I want to do.  When I was in junior high, I wanted to make British friends (self-diagnosed Anglophile here - no shame!), so I created an AOL account and learned to navigate to British-themed chatrooms.  When I was in high school, I wanted to create a blog to keep up with my friends, so I joined LiveJournal.  When my LJ wasn't as pimped out as my friends', I learned to copy other people's CSS codes to make mine look pretty.  While in library school, I was assigned to create a Google site for my portfolio, so I copied someone else's template and reworked it to be personalized for me (hey, no need to reinvent the wheel, right?).  At work at the library, our circulation system was down, so I investigated how to use Microsoft Access as a work-around using one of the preexisting templates.  I needed new book straps for my interlibrary loan system, so I Googled how to use mail merge in Microsoft Word to edit our old label form.  For our display committee, I fiddled around with Adobe Photoshop and PowerPoint to create posters and fliers.

The basic theme of my approach to technology is 1.) If I don't understand it - Google it, and 2.) Trial and error.  While I was copying other people's CSS code, I didn't understand what I was doing exactly -- so half the time I couldn't figure out how I had made my profile box turn invisible or why the header was now so huge it was obscuring the title.  But I kept experimenting until I figured it out or I found a workaround that obscured how little I knew about coding.  Fake it until you make it, am I right?

I am so surprised by how many people get stumped by small problems and don't try to solve them on their own.  One time a CD-ROM got stuck in my laptop and my husband thought I was going to have to take it to the shop to get it fixed.  I Googled the problem and found out some weird fix where you  restart your computer while maniacally clicking a certain button a million times until the computer eventually vomits out the CD.  It sounded funky, but it worked.  I think that too often people expect to already know the answer to a problem, and if they don't -- they assume they can't solve it.  You don't need to have formal education in technology to try using it in your daily life.

I think that especially in the ever-changing library field, librarians need to be willing to go out on the extra limb and investigate solutions other libraries have tried -- or apply solutions from other fields to the library environment.  Creativity and the willingness to try new things are the keys to managing a learning organization.

Sunday, May 17, 2015

Plug In the Library



Hello and welcome to my blog, Plug In the Library!  This blog will be recording my adventures through the Maymester course MLIS 7505 at Valdosta State University.  You may be wondering how I came up with the name of my blog.  Well, for starters, everything more self-explanatory was already taken.  But!  Mostly I chose it because I wanted to juxtapose two ideas:  things that plug in (i.e., technology) and things that are generally considered not to (such as dusty old libraries).  This is a stereotype that is due a quick, merciful death.  Yes, many libraries, such as special collections or archival libraries, still dedicate themselves to preserving stacks and stacks of dusty old books.  However, most libraries have evolved to become a lot more than that.  And to require a lot more plugs.  Sure, you can visit your local public library to check out the latest hardback on the bestseller list, but you’re just as likely to borrow an e-book version of it, or visit a computer terminal there to do research for a school project, or learn to create a resume through a class there.  Any university student will tell you they spend less time doing research at the library than they do remotely from their laptop in their dorm room.  At 4 a.m.  Four hours before their paper is due.  Besides services like these, libraries are taking the opportunity to engage their communities personally and offer assistance to their patrons wherever they are – through social media, reference help chat, or good old-fashioned email.  So while the library is plugging itself in, it’s also inviting you to plug yourself into it.  So come on!  Sit down, plug in, and follow along as I explore technology in libraries over the next few weeks in this course.