LIBR 246-04/13 Web 2.0 (Fall 2010)

Printer-friendly version

Description: For the final project, the class will be broken up into six groups to accomplish the following:

1. Create a proposal to implement a specific social software tool (or suite of tools) for a specific purpose in a specific type of library.

2. Create a proof of concept, working model or or detailed prototype of the proposed social software implementation.

3. Sell your ideas to your "colleagues" in a 7-minute presentation in Elluminate.

 

Due Date: December 1, 11:59 pm PST. (the powerpoint for your presentation must be sent to your Elluminate Assistance, Bonnie Rainey, by November 29th at 10 pm PST.)

Each group should run their idea by me for approval before getting started.

 

The proposal and presentation should be designed for an audience that doesn't know much about social software and that you have to convince of the efficacy of your idea.

 

Proposal

The proposal should include:

• The name of the technology you would like to implement.
• A brief description of this technology.
• An explanation of the service you would like to create with the software.
• An explanation of how this service will fill a need at your library, including benefits (also indicate if the service will be helping staff, patrons, or both).
• Evidence that this technology would be useful in libraries. This evidence can take the form of libraries that are successfully using the technology or articles that extol the virtues of using this software in libraries. I would like to see a minimum of four success stories/examples or articles on the subject with appropriate links and brief (1-3 sentence) annotations.
• A list of possible roadblocks to implementing this technology, including institutional culture, staff knowledge and training, getting buy-in, technology issues, support of the technology, monetary concerns if they exist, etc.
• Ways that you believe you or your organization could overcome the issues raised above.
• At least one (or up to three) suggestion(s) of specific software you would use to implement this program in your library. For example "I would suggest using Wordpress for our blog software because it is open source and is one of the most popular software options for blogging."
• A plan for the ongoing maintenance of the software and any policy or training issues you think are important to address.
• How you will assess whether or not the technology is having the desired impact.

Length: There is no prescribed length for this document, but it should be long enough to cover all important points and short enough so that your administrators' eyes wouldn't glaze over.

To submit your proposal: You can use an external website, a page on the wiki, or your blog to post your proposal. Then post the URL of your proposal to the Proposals page on the wiki so that all of the proposals will be easily findable.

Grading criteria:

• Proposal includs all of the following (2.9 points)
  
  • Name of technologies (.2 points)
  • Description (.4 points)
  • Explanation of service you're creating (.4 points)
  • Evidence of utility (.3 points)
  • List of possible roadblocks (.4 points)
  • How to overcome roadblocks (.3 points)
  • Software you'd use (.3 points)
  • Maintenance, policy, training (.3 points)
  • Assessment plans (.3 points)
• Writing is of high quality (.6 points)
• Content is well-organized (.7 points)
• Students make a good case for their technology (.8 points)

 

Proof of Concept/Prototype/Working Model

You will need to create a working model of your proposed social software implementation. For example, if you wanted to create a book review blog for teens, you would need to actually create the blog and add appropriate content. If you can't use the specific tool you proposed in your proposal (let's say you wanted to use Moveable Type for your blog, but didn't actually want to pay for an account to create a model) you can use a substitute for the model (i.e. Blogger, Wordpress.com, etc.).

Since you need a working model, you must choose your implementation carefully. Most groups would not be able to create a working model of RSS feeds of new books or tagging in the catalog. Focus on projects that would not be too difficult to achieve.

To submit your proof of concept: Include the URL in your proposal.

Grading criteria:

• Prototype is realistic (2 points)
• Prototype is detailed (2 points)
• Prototype is as described (1 point)

 

Presentation

Your presentation can include slides, a live demo of your prototype/working model or whatever your group feels it needs to get its point across. It must be 7 minutes-long and it must be presented as if your audience knows little about social software and needs to be convinced that your idea is good. You can assume in the presentation that they know the basic definitions (what a blog is, what a wiki is, etc.), but they have not used them nor thought of how they could be used in libraries. Please contact me if you'd like to practice your presentation in Elluminate before your presentation.

You will give your presentation on December 1st in our final Elluminate session. There will be three minutes for questions after your presentation. Please note: the powerpoint for your presentation must be sent to your Elluminate Assistance, Bonnie Rainey, by November 29th at 10 pm PST.

Grading criteria:

• Students completed presentation in time allotted. (2 points)
• Students were articulate and complete in their description. (2 points)
• Students addressed the correct (imaginary) audience. (1 point)

 

Experience report

Each of you will need to email me a brief summary of the group experience and your perception of each group member's contribution to the finished product. This doesn't have to be formal; just a brief summary. 25% of the total grade for the group project (5 points) will be individual and will be based on the reports I get from you and your group members. Please email me your experience report by December 3rd at the latest.