Saturday, June 13, 2009

MLIS 7505 Final Project

Rhiannon Shoults-Wilson and Sam Link

MLIS 7505

Dr. Fatih Oguz

13 June 2009

       

WorldCat Local: Current and Future Uses in Libraries


Background


WorldCat
Local is an emerging technology which came about as the result of
collaboration between the University of Washington libraries and OCLC,
the non-profit company behind OpenWorldCat and WorldCat.org. In 2005 OCLC reported that 84% of information users begin their search at a
search engine, and only 2%
begin at a library page (De Rosa, 2005, p.1-17). Librarians within the system observed the use of Google,
in particular, as the beginning point of information seeking. While
some lamented the limited capabilities of Google, it was realized that
in o
rder
to remain competitive, there would have to be change on the network
level to make the library system a primary starting point for
information seekers (Ward
, Shadle, & Mofield, 2008, p. 5). Among the strategic directions of the UW Libraries
strategic plan for 2010 is “Enhance user services,” with the associated
initiative to “Build or integrate new tools and services for
information discovery and delivery." After laying out the requirements
for a new search system which would be user-centric, include resources
beyond the physical library, and incorporate the library’s workflows
without causing confusion for the user, the UW Libraries approached
OCLC in the summer of 2006. The resulting platform came to be known as
WorldCat Local
(Ward et al, 2008, p. 5).

             

OCLC
was chosen by UW Libraries because of their previous platforms Open
WorldCat and WorldCat.org. Open WorldCat had demonstrated their ability
to work with large corporate institutions by being integrated into
search engines such as Yahoo! and Google, and had thus required close
work on the requirements lain out by those corporations (Ward et al.,
2008, p. 7). WorldCat.org demonstrated OCLC’s ability to create
original content and a functional and user-centric search sy
stem
(Ward et al., 2008, p. 7).


Features


WorldCat Local can be described as a local
implementation of WorldCat.org, which has been modified to reflect the
individual library’s brand and feel. Like WorldCat.org, WorldCat Local
searches the entire WorldCat database, but has been modified to show
local delivery options unique to the implementing library (Ward et al.,
2008, p. 7). This global search is then linked to the local catalog
either via OCLC holdings symbols being attached to the library’s
records, or
utilizing
a link resolver application. These records are then displayed, and
selecting an individual record brings up the availability of that item,
and options such as holds or interlibrary loans to make it possible for
the user to easily acquire the material (Ward et al., 2008, p. 7). In
an effort to further incorporate electronic resources, WorldCat Local
can import OAI records and convert them to MARC so that they may be
used in the system (Ward et al., 2008, p. 8). In addition to these
user-centric features, WorldCat Local also provides direct access to
multiple article databases, and thus can incorporate article and
journal searches into book searches seamlessly, reducing the need to
learn two separate search systems to locate research materials, and can
then use the library’s link resolver to link to actual article content
(Ward et al., 2008, p. 8).


WorldCat
Local utilizes a Google-style free-text box for searching, creating a
familiar interface for the user and again making a user-friendly
environment. To further add to the functionality, the platform has
inherent multilingual support
and support for non-Roman characters
(Ward et al., 2008, p. 8). The records are organized using tabs, a
familiar feature from web browsers and multiple websites, and
individual records have further tab divisions, as well as incorporating
tools such as Google Books which a user may already have experience
with (Ward et al., 2008, p. 9). The acquisitions options are phrased in
friendly, common-use language – “Get This Item” – allowing the user to
move into the library’s workflows without confusion (Ward et al
., 2008, p. 10).
In a sign of the growing cross-over between libraries and Web 2.0
technology, WorldCat Local allows the user to easily link to the record
on their social-networking page, such as MySpace or del.icio.us, and
allows for the posting of user reviews and other user-generated content
within the WorldCat Local system (Ward et al., 2008, p. 10).


The
Web 2.0 features of WorldCat Local are the ones which the users at UW
Libraries have been most vocal in requesting. WorldCat Local supports
starred user ratings, the export of citations to citation management
software, and the sharing of located materials on social networking
sites (Ward
et
al., 2008, p. 11). There have also been a Google gadget and a Facebook
widget developed to further incorporate WorldCat Local into Web 2.0
functionality (Ward et al., 2008, p. 11).


WorldCat
Local utilizes a ranking hierarchy in the display of located records to
enhance the user experience (Ward et al, 2008, p. 8). Materials local
to the user are displayed first, followed by consortia materials, and
finally materials drawn from the wider WorldCat database. In addition,
individual records provide information on ILL and hold availability,
with the option of also including a “Buy Me” link to either Amazon.com
or Baker & Taylor so that the user may purchase the item directly
if they feel such a need for it (Ward et al., 2008, p. 8-9).


The specifics of the tabbed system are
on the record level. Each record has five tabs which link to further
information concerning the material. The “Libraries” tab shows where
the item is held and available on the ranked scale of local, consortia,
and WorldCat. Further details concerning the item are available under
the “Details” tab, along with acquisitions information for the
material, availability, and link-sharing Web 2.0 capabilities. The
“Subject” and “Editions” tabs provide the obvious content of subject
heading listings for the item and the various editions available.
Finally, the “Reviews” tab combines user-generated reviews of the item
with those pulled from professional sources, allowing the user to gain
an overview of opinions of the work both from peers and professionals
at a glance (Ward et al., 2008, p. 9-10).


Advantages


The greatest advantage to using WorldCat Local is that users do not have to duplicate their search in different tools such as a local catalog, a consortial catalog, WorldCat, article databases, and institutional repositories to find all appropriate information, nor do they have to understand the differences between the different tools.  Users also don't have to understand the complexities of library workflows.  They don't have to consider when they need to initiate a consortial request versus an interlibrary loan request and find the separate forms for that.  The system has the workflows programmed in and is able to make the differentiations for the user and create the proper type of request for the user to receive his or her item (Ward et al., 2008, p. 11-14).  This ease in search and placing materials requests has led to a significant increase in interlibrary loan and consortial requests at the UW Libraries since implementation of WorldCat Local.  The librarians at University of Washington believe this to be because users are finding items they weren't previously and because they find it easier to place requests (Ward et al., 2008, p. 24).


One aspect of this single interface is that article and book content are searchable through the same space - this is one of the most requested features by users (Ward et al., 2008, p. 8).  WorldCat Local launched with the ability to search only the five OCLC databases already indexed in WorldCat - GPO, ArticleFirst, MEDLINE, ERIC, and the British Library (Online Computer Library Center [OCLC], 2008, p. 8).  However, OCLC is constantly working on expanding the amount of searchable databases through WorldCat Local.  It was recently announced that OCLC had reached an agreement with EBSCO that will allow libraries that subscribe to WorldCat Local and to EBSCO databases to search those databases through the WorldCat Local interface (OCLC, 2009a).  This will vastly expand the amount of articles available, making the service more valuable.


The inclusion of Web 2.0 features such as user reviews and the ability to make and share lists is another major advantage to the WorldCat Local service.  These are the types of features that web-savvy users expect in websites, but incorporating them into OPACs and other search tools can be very expensive (Ward et al., 2008, p. 11).  A packaged service like WorldCat Local makes providing these services more affordable.  The WorldCat Local service is particularly affordable since OCLC's recent announcement that libraries that subscribe to FirstSearch WorldCat will automatically be eligible for a free "quick start" version of WorldCat Local.  This version of the service is fully functioning, with the locally branded interface and simple search of the full service (OCLC, 2009b).  The major feature missing from the "quick start" version of the service is the library's implementation assistant - the OCLC employee assigned to assist the library with making a thorough, smooth transition to the WorldCat Local service.


WorldCat Local is a service that is very customizable for its users.  The multiple languages available for the interface are one aspect of this.  Another is the user's ability to limit his or her search to just a local library, the library and its consortia or even to a particular library branch, rather than including the entirety of WorldCat's holdings in a search (OCLC, 2008, p. 6).  This is an important feature for ensuring that users aren't overwhelmed by search results.


OCLC has been releasing monthly updates to the WorldCat Local service based on user feedback (Ward et al., 2008, p. 39).  It is a well-maintained service, and OCLC has demonstrated a commitment to expanding and developing the service.


Disadvantages


Most libraries that implement WorldCat Local have to undertake records cleanup to make their holdings matched to those of OCLC.  This is because WorldCat Local searches the WorldCat database, so if records in a library's catalog have not been properly linked to WorldCat via an OCLC holdings symbol or other service, search results will be incorrect (Ward et al., 2008, p. 7).  Depending on a library's cataloging practices, this can be a minor to major undertaking.  It is often most complex when dealing with e-serials (Ward et al., 2008, 36).  If a library is using the full WorldCat Local service, they will be assigned an implementation manager who can help to make this process as seamless as possible (Ward et al., 2008, p. 27).  The free "quick start" service that comes with FirstSearch WorldCat does not involve an implementation manager - this is something that a library must consider when deciding if one of the WorldCat Local services is right for them.


OCLC has limited the amount of display customization that library's can do, in an effort to maintain the basic WorldCat design in all implementations (Ward et al., 2008, 31).  As WorldCat Local is, at its heart, a commercial software product rather than an open source project, the amount of customization available and the direction of development will ultimately be controlled by OCLC.  Many libraries are used to this aspect of commercial software implementation, but those wanting a fully customizable product should look elsewhere.


Social features are one of the greatest advantages to using WorldCat Local.  However, for users to use most of these features they must create a separate WorldCat.org account.  There is no way for a user to use these features with his or her library account information, which could potentially be confusing or annoying.  OCLC is pursuing integrating OpenID into WorldCat (OCLC, 2008, p. 4), which would allow another option for logging in, but would not fully deal with this issue.


A usability issue with WorldCat Local is the fact that call numbers and availability are not visible from the main search results screen, they are only accessible from the individual item record.  This could potentially create more time-consuming searches, particularly as there is no way to restrict searches to currently available items only (OCLC, 2008, p. 8).


Another implementation issue that a library must consider with WorldCat Local is the relationship between its local catalog and a consortial catalog, if applicable.  If both exist, the library must designate which one will be searched in specific instances.  The UW Libraries, for example, chose to have the system always query its consortial catalog, and that has led to some issues that needed to be resolved.  Inconsistencies between the two catalogs led to certain items being hidden from search results, for instance.  They also had some problems with overloading the consortial catalog's server (Wade et al., 2008, 30-31).


While recent agreements between OCLC and database providers such as EBSCO as discussed above have greatly expanded the amount of articles that will be searchable through WorldCat Local, it is still the case that most libraries will have databases that are not included in the service.  This could lead to confusion in users who may not be aware of other search services.  WorldCat Local is not likely to ever fulfill the same functions as a well-constructed federated search tool, though it does have many features that federated search does not.


Current Implementations


WorldCat Local is currently in use in many libraries, including the University of Washington Libraries (http://www.lib.washington.edu/), Lincoln Trail Library System (http://www.ltls.org/linc.html), Ohio State University (http://library.osu.edu), Macalester College (http://www.macalester.edu/library/), and the California Digital Library (http://melvyl.worldcat.org).


Future Applications


OCLC recently announced they are expanding WorldCat Local to include automation features more traditionally seen in an integrated library system such as circulation, delivery, and acquisition.  This cloud computing service will provide automation features at a network level.  This service could potentially reshape the automation field, as these are services generally provided by commercial ILS vendors at a very high price (Breeding, 2009a).  OCLC has added the ability to include a barcode number with an item's
WorldCat holdings information, paving the way for a web-based circulation
system (Breeding, 2009b). 
The ability to obtain these automation services from
OCLC could be very appealing to libraries that already subscribe to
many OCLC services, for increased interoperability.


The automation services from OCLC could also lead to increased adoption of the WorldCat Local service itself.  WorldCat Local has to be customized to work with integrated library systems individually.  It currently works with Innovative Interfaces Millennium, Innovative Interfaces INN-Reach, SirsiDynix Horizon, Ex Libris Voyager and Ex Libris Aleph, and OCLC is working on compatibility with others (OCLC, 2008, p. 3).  This makes many libraries currently unable to adopt WorldCat Local even if they would like to.  OCLC's automation services will be designed to work with WorldCat Local, giving another incentive to try them out.


Conclusions


WorldCat Local has the potential to be a powerful tool for libraries, combining searches for books and articles both locally held and worldwide into one interface, and integrating Web 2.0 features and connections to social sites.  Currently, in order to determine if WorldCat Local is a good option for adoption, a library must consider if it is compatible with its ILS, how well-maintained their catalog records are in terms of their integration with WorldCat, and if they are comfortable with a commercial service with limited customization, among other things.  As OCLC develops WorldCat Local further and introduces their web-based automation services, the adoption criteria will develop along with it.  WorldCat Local is an emerging technology library professionals should follow with interest.




References

Breeding, M. (2009, April 23).  In Challenge to ILS Industry, OCLC Extends WorldCat Local To Launch New Library System.  Library Journal.  Retrieved June 8, 2009, from http://www.libraryjournal.com/article/CA6653619.html.

Breeding, M. (2009, April 28).  Breaking Down the Components of OCLC’s New Library System.  Library Journal.  Retrieved June 8, 2009, from http://www.libraryjournal.com/article/CA6654793.html.

De Rosa, C.  (2005).  Perceptions of libraries and information resources.  Retrieved June 11, 2009, from http://www.oclc.org/reports/2005perceptions.htm.

Online Computer Library Center.  (2008, November).  FAQ: WorldCat Local.  Retrieved June 8, 2009, from http://www.oclc.org/services/brochures/212632usf_worldcat_local_faq.pdf.

Online Computer Library Center.  (2009, April 7).  OCLC and EBSCO partnership offers library patrons online access to full text of authoritative electronic journals.  Retrieved June 9, 2009, from http://www.oclc.org/news/releases/200922.htm.

Online Computer Library Center.  (2009, April 23).  OCLC announces "quick start" version of the OCLC WorldCat Local service.  Retrieved June 9, 2009, from http://www.oclc.org/news/announcements/announcement355.htm.

Ward, J., Shadle, S., & Mofield, P. (2008, August). WorldCat local at the University of Washington libraries. Library Technology Reports, 44(6), 4-41. Retrieved June 11, 2009, from Library, Information Science & Technology Abstracts with Full Text database.



Friday, June 12, 2009

Assignment Three

I conducted an interview via email with Dean Frey, director of the Red Deer Public Library in Red Deer, Alberta. The transcript is below.

Dean Frey: Intro: We're using Drupal 5.7 for a variety of websites:
www.rdpl.org - our main library website

www.electionforum.ca - a site devoted to the 2007 Municipal Elections - this will be re-started for the 2010 elections.
www.artsparks.org - a site about arts programming for persons with developmental disabilities.
www.digitalreddeer.ca - a digital repository
www.villalobos.ca - a site about Heitor Villa-Lobos (a personal project of mine)
staff.rdpl.org - a staff intranet
board.rdpl.org - a Library Board extranet

Me: How and where did you hear about content management systems?
DF: My IT Librarian (now Assistant Director) Cory Stier was well-versed in all of our CMS options.

Me: What were the motivations to use a content management system for the library's site?
DF: We wanted to distribute the content creation to a variety of people throughout the library, and to separate the content from the look+feel of the websites. We also wanted a robust back-end database to manage stories, information about events, image libraries, links, and specialized data. As we developed our websites using Drupal, we got more involved in blog posts and comments, and also needed user control for password-protected intranet and extranet sites.

Me: What criteria led to the adoption of Drupal, in particular?
DF: We wanted a robust system from the Open Source world: something that had a significant user-base to develop and test new functionality. We liked that functionality could be easily added by adding newe modules.

Me: What benefits does Drupal offer over the previous site or other content management systems you've used?
DF: Everything from 2. and 3. above, plus the opportunity to see some fairly mature library Drupal websites in operation. We liked Drupal's openness, and the upgrade path to new functionality. Drupal is very, very solid.
Me: Are there disadvantages to using Drupal?
DF: Some modules (Events, for example) are complex to setup, though once they're in place, they're very easy to keep running.

Me: How was the learning curve?
DF: On the setup side, my impression is that it was pretty quick for our IT staff. I was involved in putting together bits of the staff and board sites, and most of villalobos.ca. As more of an end-user than an IT person, I would say the setup of the site was of moderate difficulty. I think most staff and Board member end-users have found content development very easy and intuitive. Having secure sites to learn in made things less stressful.

Me: Are departments or non-IT staff updating their own content? If so, what kind of training was used for those staff?
DF: Yes. There has been some training - mostly one-on-one, I think. We've encouraged posting and commenting by all in the staff site, and that's worked out very well. Practising in the staff site (especially in the "Just Testing" and "Personal" sections) has given people the skills and experience to be able to update public sites.

Me: My class has been posting all of our assignments to a public blog. May I post your name and the library's name on my class blog?
DF: Yes, please do. We'll be on the lookout for Drupal-ready librarians in the future, so it's good for us to get our name out there. Red Deer is a great place to live, by the way, though it's a tiny bit colder here than it is in Georgia.

Tuesday, June 9, 2009

MLIS 7505 Assignment Four

Rhiannon Shoults-Wilson
MLIS 7505
Dr. Fatih Oguz
9 June 2009

Assignment Four

I went to our DSpace implementation and clicked on My DSpace, which allowed me to create an account, which was very simple. After I was given administrative privileges, I created my community. The technical side of this was very simple, though I wish there was more input on the site regarding the content. For instance, when creating or editing the community, there is the option to add "sidebar text," but no description of what type of information should go there, or how it should be different from the "short description" or the "introductory text."

I next created a collection within my community, which I decided would house a couple of works I'm considering for my MLIS portfolio.


I visited the metadata registry and added a new field, dc.title.shoults-wilson. I then emailed Larry and had him add the field to the input form and make it indexable. After that had been done, I uploaded a couple of files - a paper from my cataloging class and a pathfinder I created for my reference class. I input information into the fields, including the "Shoults-Wilson title" field. I used this field to indicate what class and project the document belonged to, e.g. "MLIS 7100 Pathfinder." The input was very intuitive, though it relied on the user having an understanding of the metadata elements. If I were to implement this system for end users to upload their own documents, I would want the ability to link to style guides and information about what is required for each metadata field.


After I had uploaded my documents, I received emails telling me my submissions had been accepted. The emails also included a Handle System permanent identifier, which did not work (I would assume this is because we don't have the service set up for our test installation). Sending this permanent URI to the document owner is a very useful tool.


I went to the advanced search, and searched Title for MLIS. This brought up both of my documents, because I had included this term in the "Shoults-Wilson title" field, though it wasn't in the displayed title.


From my experiences here, I feel like DSpace is a potentially powerful tool for libraries and their digital collections, though it would require a lot of time to grasp all of the available features, and I think a lot of customization would be required to make a useable repository for community users to upload and modify (as opposed to librarians). I know that is what DSpace was designed for, and it's interesting to see how libraries are implementing that. One such is IDEALS, the repository for faculty, staff, and graduate student research at University of Illinois at Urbana-Champaign. They have customized their installation, created lots of help documentation, and have a final review process by librarians, and this allows community members to upload their own documents using DSpace, saving a lot of staff time. This illustrates what a great tool this can be!


URLs Created:
My Community: http://mlis.library.gatech.edu/handle/123456789/32
My Collection: http://mlis.library.gatech.edu/handle/123456789/33
My Cataloging Paper: http://mlis.library.gatech.edu/handle/123456789/99
My Pathfinder: http://mlis.library.gatech.edu/handle/123456789/100

Sunday, May 31, 2009

MLIS 7505 Assignment Two

Rhiannon Shoults-Wilson
MLIS 7505
Dr. Fatih Oguz
31 May 2009

Assignment Two

After Suzannah, our team leader, adjusted the site's settings to accept new registrations, I was able to create an account on our site. I then updated my profile, so that my name displayed as "Rhiannon" rather than my user name when I made posts and comments.

After my status was changed to "admin," I looked over the site and the changes my team members had already made. I went to Settings and updated the blog's tagline, which still read "Just another WordPress weblog" to say "Applied Technologies in Library Practice." I created my bio page, and set it to appear under the "About" page, with those of my teammates. Inserting text and a picture was very simple. I changed the text of the "About" page, which was still set to the WordPress default, to describe our site.

Rita had already changed the site to the ArcLight theme. I looked at the other installed themes, and decided that one was the best, but I wanted to make a few modifications. The theme by default had background images used for the navigational buttons and the headers for the widgets in the sidebar, but had the options to change to an image-free version. I made this change, because I liked the look better and it improves load times (particularly for those on slow connections). I mostly liked the colors, but I wanted to get rid of the pink the theme used for the widget headers and the link hover text. I did this using the CSS modifications box on the theme settings page. I've never really studied CSS, so I don't know the proper syntax, but I'm able to make small changes like this by finding the appropriate spots in the style sheet, copying them and then changing to the color code I want. Learning proper CSS is definitely on my to-do list!

I next went to the widgets page and looked at what we were using. I removed the Events Calendar widget, as we weren't currently using it, and the Search widget, as the theme had a Search box in the header. I also removed the Recent Posts widget, and instead added the Archive widget, which allows viewers to browse archives of our posts by month. I decided I wanted a box that showed the recent posts from our class blogs in the sidebar. To do this, I went to Yahoo! Pipes (which we heard about in the lecture on mashups) and created a pipe that combined the RSS feeds from our four blog feeds. I then took the RSS feed from the pipe, and added the RSS widget to our sidebar, so it shows the ten most recent posts from our blogs. Initially the feed was showing our posts in a weird order, in the order in which it had imported our posts from our blogs. So I added a filter to the pipe to tell it to sort by the post's timestamp. It took a while for the RSS feed to resort itself, but it looks right now.

I then searched the plug-in directory, sorting through the most popular plug-ins. I found the Add to Any plug-in, which adds a button to all posts and pages, allowing the viewer to add the post or page to an email, their browser's bookmarks, or one of over 100 sites, such as Digg and Delicious. I really like and use these buttons on other sites, so thought it would be good here. I emailed Dr. Oguz and once it was installed I activated it. It works well for the services I've tried (Delicious, Gmail, and Facebook).

I made posts to our site's blog to document what I had done for my teammates. When I did so, I added categories from the ones Rita had created. I also added a few topical tags, such as "RSS" and "CSS."

I had used WordPress before this assignment, so everything was pretty familiar to me already. The most trouble I had was with working out the kinks with Yahoo! Pipes and the RSS widget. I'm glad I did this - Pipes seems to be very powerful potentially and I'm glad I'm now familiar with it. WordPress is a really great tool - it looks great out of the box, is easy to use, and is really potentially customizable with the plug-ins (and even more customizable if you're familiar with scripting).

URLs Created:

Our Site: http://www.valdosta.edu/~foguz/mlis7505/team5/
My Bio: http://www.valdosta.edu/~foguz/mlis7505/team5/?page_id=96
Our Site's About Page: http://www.valdosta.edu/~foguz/mlis7505/team5/?page_id=2
The Pipe for our Combined Blogs: http://pipes.yahoo.com/pipes/pipe.info?_id=eJa8BKBL3hG4JHPa_g6H4A

Sunday, May 24, 2009

MLIS 7505 Assignment One

Rhiannon Shoults-Wilson
MLIS 7505
Dr. Oguz
24 May 2009

Assignment 1

Part One:


I created my class blog at http://rhi-lib.blogspot.com. I customized my settings, including having comments emailed to me and excluding my blog from search engines. I also customized my layout by changing some colors, rearranging and removing items from the sidebar, and adding script that lists recent Delicious links in the sidebar. I posted a link to the blog's RSS feed to the discussion board.

Part Two:

I decided to create my standalone RSS feed to list entries from the Athens Regional Library System's "Featured Genres" column. I did this through RapidFeeds as directed. It is located at http://feeds.rapidfeeds.com/23631/. I posted this link to the discussion board.

Part Three:

I already use Google Reader and subscribe to several library blogs, as well as the MLIS Program's feed. I added a few new blogs from the suggested list, including Information Wants to Be Free (Meredith Farkas's blog), and Cliff Landis's blog. I also added the feeds from my classmates' blogs that they have posted to the discussion board. I created a new folder for these, labeled "mlis 7505."

Part Four:

I decided that my imaginary library is a mid-sized public library (service population approximately 200,000 people) that wants to create a wiki to contain general subject guides. An example of the type of wiki they are envisioning is the St. Joseph County Public Library's subject guides wiki.

I visited WikiMatrix, and began their comparison wizard. I decided that, even though this would be a staff-edited wiki and not subject to public vandalism, a page history feature would still be useful for editing, and was thus necessary. I decided that, as staff would be trained on updating the wiki if they were not already familiar with it, a WYSIWYG interface was not necessary. I decided commercial support wasn't strictly necessary. As the wiki will be run by a small community of users in one location, I decided localization wasn't necessary. I decided the flexibility and security of running the wiki software on the library's hardware was preferable to a wiki hosted by an outside service. I decided to go with a database system, for its search capabilities. I decided Open Source software was important, both philosophically and to reduce costs. I did not restrict based on programming languages.

The wizard left me with 44 choices, so I scrolled through the comparison table for these. I removed the software that was still in early development - I use such software in my personal life, but I do not want to try to implement a professional project with it. I removed software that did not run on Windows, as that is what our library computers use. I removed software that did not include a preview function, which I thought was important. I restricted to software that had the most common editing features, such as revision logs, and minor changes. I removed software that did not have support forums.

After doing all this and browsing through pages, I ended up choosing TikiWiki. It has all of the features we might want for the wiki and, since it has CMS components, would enable the library to easily include non-wiki elements, such as RSS feeds and forums, if they chose to in the future.

Part Five:

I logged into my Google Docs account, created a new document and typed this up. I then shared it to my blog.

Friday, May 22, 2009

My Background

I am fairly familiar with the Web 2.0 technologies we have been discussing in Module 1. I have created and maintained blogs before, using Blogger, WordPress, and LiveJournal. I use Google Reader daily (I currently have 116 subscriptions, apparently!). I use Google Docs to work on documents, as I do my work on multiple computers. I have edited articles on Wikipedia. I use Facebook, Twitter, and Delicious on a daily basis, as well.

The most interesting course materials to me have been about specific ways that libraries are using these technologies. I read quite a few library blogs and try to keep up with these things, but the class readings have been interesting to me in this regard, as well. Meredith Farkas's presentation, in particular, contained examples of some really interesting implementations, such as the librarian who asks for collection development suggestions through a Facebook page, and the library that has set up a Q&A blog, in which they post all of the feedback they receive, and respond. I am most excited about the opportunities these technologies have to change the ways libraries communicate with their users (for the better, hopefully), and it is great to see this at work.