IL 2011: Closing Keynote: The Great Gamification Debate
11/20/2011 11:41:00 PM | Author: Christa
Wednesday, October 19, 2011

Liz Lawley, Director, Lab for Social Computing, Rochester Institute of Technology

Gamification is the application of gaming mechanics to non-gaming environments.

Lee Sheldoen – “the multiplayer classroom”. How to use game mechanics in the classroom – instead of grades, exp points. Students are doing better, more engaged, better grades, hand in more assignments. – Ian Bogost – gamification is bullshit. “–ification is simple, repeatable, proven techniques. Is always easy and repeatable, and it’s usually bullshit”.

Earning points in games like Scrabble and Words with Friends, isn’t because you got a 50 point word, but because it was difficult. The feeling of accomplishment is very important.


Microsoft Research gave some money to help them get started, and is continuing to fund it.

Foursquare – gamification that really seems to work. Allows you to reflect back on what you’ve done and think about your accomplishments.

4sq&7yearsago – emails you each day to tell you what you were doing a year ago.

Experience of competence is important. Students should want to do it, not just do it for the reward.

What behaviors did we want to reward and encourage?

What feelings of competence could we engender?

What did we want our students to remember and reflect on?

Bartle’s Player Types – kinds of people who play MUDs. Killers, achievers, explorers, socializers. Too generic a model, overly simplified.

New way of thinking of achievements – apprentice, journeyman, master. Individual and shared (group work). 

Just Press Play.

Game launched last week at RIT.

“Why can’t students get achievements for being awesome?” Game that overlays students day-to-day activities. Beta launched for RIT’s School of Interactive Games and Media. 720 students.

RFID keyfobs for some activities – go places. Some activities give them cards (faculty collectible cards).

Experiences the students will remember. Humor, playfulness, engaging with people around them. Humanizes faculty for students. Connects students to each other.

Will open source at end of summer!

The platform is important, but also need to spend time thinking about the content, designing the experience. What works for students at RIT won’t be the same for students at another univ. Will have to modify for the kind of content your students will respond to. Put the time and energy into it and you can really transform with the power of games.

Sense that they’ve really accomplished something that matters.
Links to this post
IL 2011: Talk About: eBook Preservation
11/20/2011 01:57:00 PM | Author: Christa
Tuesday, October 18, 2011

Goal is to represent our professions rather than our employers.

Talk about: eBook PreservationTalk about: eBook Preservation

Sue, I’m a librarian and I’m concerned about:
  • Usability
  • Authenticity
  • Discoverability
  • Accessibility
What does it mean to preserve ebooks? Just the text? The experience? Links, multimedia

In what format should digital format be preserved? Will it serve us in the future?

Who’s responsible/ who owns them? Library, publisher, aggregator, author? Who has the right to make backup files?

What are the trigger events? Items kept secure until checked out.

Can I move to a different interface? Do I have the right to take my archive files with me and take them to another aggregator? Is the content provider saving items in format that will work in any interface?

Do I have the ability/right to remove a title that needs weeding? Is it completely removed? Or is it stored somewhere else I can access it in case it’s discovered that I do need it again?

Who pays for preservation? Built into price of book? Access fees? Separate access fee? Or just the cost of doing business?

Rolf – publisher

Publisher is involved with beginning, middle and end of content creation.

1-Ownership: perpetual. 2-Publisher owns copyright, library owns product. Challenge is what lies between those 2 statements. Limitations – not everybody will win.

Big issue from publisher perspective is resourcing. Dollars and cents. Who pays for preservation. Publishers have the basic responsibility to participate in all the major digital preservation initiatives. LOCKSS CLOCKSS

Also need to make the investment to protect the version of record. Hard to determine because there are so many dynamic items out there.

Aggregators – a growing and preferred purchasing sector. Every publisher licenses their content to several. Who’s protecting who? Is publisher protecting aggregator who protects libraries? Or something else? What is aggregator’s mission? Contractual issue – preservation doesn’t come up in discussions with aggregators. The legal language is going to be the ultimate protector in how we tighten up issue between publisher and aggregator.

Preservation Before Dissemination

When publisher creates content we need to start thinking about preservation before dissemination. Be strategic. Proactive- plan for change is the most difficult thing for a publisher to do. Still live in book world. Need to be collaborative with aggregators and libraries. Knowing that not everything will be resolved, but publisher needs to wake up and figure out how on a collective level we can create a safer environment for content. Digital preservation is something that every publisher needs to start creating - an operational model that is resourced. Create some standards, have a profound effect  on how we can protect the content that you own.

Ultimately, it’s knowledge that your end user will always need.

Ken - aggregator

What does it mean to preserve ebooks?

Light archive – the aggregated databases that exist today, either thru aggregator or publisher. Collection of ebooks on a platform that can be accessed by users on platform.

Dark archive – creating a repository to ensure that if there’s some event that warrants it that there is still the ability of your users to access the content. Closed, tightly guarded. Only reason someone should need to go in is to inventory, make sure it’s all there in case needed.

Is the text all we need to preserve?

Publisher owns copyright and original file. Publisher’s decision for what becomes the item of record.

Portico – take publisher’s original file, create normalized version of file – all in same format.

CLOCKSS – take capture of last user interface version, prior to a trigger event, and preserve that.

Who is responsible for preserving ebooks?

Publisher owns rights to book initially, grants rights to aggregator to release books. Can also grant rights to organization to preserve. Rights can be assigned to others.

What are ebook trigger events?

Publisher exits business or ebook no longer offered anywhere. Publisher has to approve trigger. Not a trigger – if aggregator exits business, because books are still available elsewhere. If library stops paying for access to platform. Same reason.

Weeding ebooks

Platforms were designd to be additive, unlimited shelf space. What is the right treatment? Choose archive as status, actually just hidden, later access can be reenabled. Manually, or ‘checked’ out? Permanently deleting? Entitled to dark archive version?

Who pays?

We all do. Publisher is owner- should preserve book. Consensus seems to be in at least 2 places. Aggregator putting redundancy in platforms and copy in dark archive. Library – up front fees or ongoing access fees. Preservation efforts.

Preservation initiatives- scalable? Sustainable?


Considered asking digital archivists? Publisher – no, question of scalability. (MY NOTE: not sure  I understand the answer)
Links to this post
IL 2011: eBooks and the Future of Publishing, Lending, Learning
11/20/2011 10:31:00 AM | Author: Christa
Ebooks and the Future of Publishing, Lending, Learning
David Bowers and Stephen Abram
Tuesday, October 18, 2011

eBooks from publishing perspective and where we see things going in the future.

David Bowers, Oxford University Press

Individual is the focus.

Libraries – the original Google. People come to libraries to learn. Issues – budgets.

OUP – is not for profit. Univ has been only shareholder in entire history of OUP. Not kicking back profit to people as shareholders. Looking to generate a bottom line, kick back to univ, so they can share knowledge. Oxford Index.

Content Aggregators

Contract with EBSCO ebrary, Miilibrary, eLibrary. Take Oxford data, package into product.

Ereaders –

Typically, eBooks that have been made and distributed to the vendors are electronic copies of traditional print books.

iPhone and app store changing that. Apps can bring more to books. Maybe reader wants something more – a chapter, an article. Ex: look inside all available books about molecular biology from a single app.

Users rent an app from publisher?

Stephen Abram, Gale Cengage Learning

We want to build stuff that helps people learn. That’s what motivates us (people in publishing). 800 librarians on staff.

Biggest project – thinking of the future. what will the textbook look like over time? What’s going to happen with large print. What will childrens books look like?

Textbooks – needs to be device agnostic. Browser independent. Learning management system independent. ADA compliant. Learning style independent. Testing new versions of textbooks in 150 schools in north America. Mobile independent. Use social tools.

Childrens books – 1st experiences in childrens books. What’s the right form of book? Why are there pages? Scroll thru instead, like a video game. Does it have to have the same ending every time? Does everything have to be in the same place every time you open the book? Move the mouse around. (MY THOUGHTS – what do childrens educators/ experts think about this? Is a change every time good or bad? Or is the consistency what kids need?)

Reference – non fiction. We use nonfiction asynchronously. How do we pull info out of multiple encyclopedias about 1 topic? And have it in whatever format we want, and assemble as my own book on the topic I need on the fly. Frame quality information, that has been quality selected, frame it to serve our users.


Copyright – if you had training in copyright that’s more than 5 years old, it’s no longer valid. Things have changed too much recently. Need to update your knowledge. Laws in US and other countries is changing.
Links to this post
IL 2011: Tips on Redesigning Library Sites
11/20/2011 02:56:00 AM | Author: Christa
Monday, October 17, 2011 

Making Connections: Conversations, Collaboration and Negotiation in a Library Website Redesign Project.
Michael Epstein - University of San Diego, Copley Library

When working on redesign, conversations were most important. Relationships are as important as tools and tech. successful collaboration with stakeholders. must be able to communicate needs of a library website.

In USD context –

Previous univ wide redesign, library not involved, given templates – very locked down version of page, ‘place your content here’, resistance to being boxed in by templates that we hadn’t been included in the conversation about, this led to benign neglect. Didn’t implement them.

Then, CIO named interim director of library, nobody was happy with old templates, not just library. New redesign. Since CIO was director of library, could have conversation with him about library role in redesign. Instead of entire redesign, doing a few depts. at a time. Library website redesign team formed – librarians and IT.

IT and librarians – defensive at first, one size does not fit all, needed to explain why library is different, needs are diff from other departments on campus. Agreed to look at other library websites. Helped IT see how library is different. 


Daily conversations on content and design. Constant communication was key.

Web advisory group within library.

Univ stakeholders unhappy with new template. Not sure who, just some people from higher up. New consultant hired. Meetings with consultant. Library had place at the table. People interested in branding and uniformity vs. unique dept needs.

Lessons learned:

-Look for opportunities to collaborate with non-library personnel.

-Build relationship thru conversations, negotiations, compromise.

-Communicate unique needs of library users with other stakeholders and other people you’re working with. Can’t assume they understand what you’re working with.

-Be willing to give up some control in return for a truly collaborative approach. It’s OK, you don’t have to do the whole thing. As long as you are both able to express your needs and work things out. – a redesign case study
Virginia Franklyn - Pikes Peak Library District

Old website about 8 years old, too small.

Project plan – read Project Management for Dummies. Really helped. Drew up project plan with timeline. On a wiki so all staff had access via intranet.

Choose framework.

Looked at WP and Joomla. But decided Drupal was best for them. Big websites use them, like what they needed. Geared toward staff data entry and patron participation. Received so much help from the community.

Had to learn Drupal. Drupal 6 by David Mercer. Drupal 7 is out now, should use that, but Drupal 6 was available when they started.

Did every example in book to learn it. Yes, very steep learning curve, but it worked to learn it. Drupal community is amazing. Drupal southern Colorado user group, library BOFs, consultants. But mostly trial and error. Broke website a lot when in development. Have a sense of humor about Drupal. Don’t have a strict timeline because things will come out of left field.  Be flexible.

Website survey – needed to know how to set up site. Catalog/my account. Suggest a book. Find classes/programs. Became sections for site.

Website layout


Don’t Make Me Think by Steve Krug. How to make a website intuitive. Get user to what they need as easily and fast as possible.

Usability testing after basic infrastructure was built. Usability Hot Team. Doing 3-4 usability tests is optimal. But do at least 1. “Of course, everyone knows usability tests are very important, and must be done.”

2 years and 1 baby later… = blog of how they did it.

Extreme make-over
Marin County Free Library

Moved from a centralized to open control. Moved from proprietary CMS to open source.

3 big takeaways – patience,  perseverance, passion for the project.

Integrating social media very important. Big 5 – Blogger, Facebook, Flickr, Twitter, YouTube.

Free labor – internship program with univ.

Also decided to simultaneously rebrand site. Realized too late it was a terrible idea.  Concentrated on content development.

Social media committee. Weekly meetings.

Used Google docs as repository. Constant communication.


-When evaluating vendor proposals – get examples with similar budget as yours. So you know what you can really expect to get.

-Get expectations from vendor of when things will be done.

-Wireframes – use different term, like diagrams. Some staff didn’t understand the term and had blocks about it which lasted throughout project.

-Useful tools – content spreadsheet detailing all content, who was responsible, deadline. Google docs.
Links to this post
IL 2011: Drupal vs. WordPress vs. Joomla - CMS SMACKDOWN!!!
11/19/2011 01:09:00 PM | Author: Christa
CMS Smackdown!Monday, October 17, 2011

Blake Carver, LISHost
Kendra K. Levine, Librarian At Large

LISHost – 400 sites. 200 WP, 100 Drupal, 1 Joomla.

What is/Why use CMS? Centralize control, free up people to make content, not techie, non-geeky users can set up own pages.

Empowers other people to create content. Timelier, universal changes easier/quicker. Users end up having a nicer relationship with the website. More user friendly.

Goals of a CMS – what’s important to you? Make life easier? Flexibility? Easier for technophobes? Functionality(calendars, widgets)? Get code out of the way so people can actually do work?

Audience question - Used to get rid of webmasters? “any dummy can do it, so don’t need webmaster”. Wrong, still need someone to maintain it.

“CMS removes impediments of keeping website current.”

CMS Smackdown!
Blake and Kendra
How to choose:

-Complex vs. simple

-How big is website?

-Learning curve- who’s going to be updating website? can they pick it up quickly?

-Who’s going to use it? Designers/users/webmasters?


-Library specific modules/plugins

* Budgets, Personnel, Time

What’s open source?

Get code, modify it, share it back to community.

Free – speech vs. beer vs. kittens

-Stared 2001, kid in dorm created bbs, powers 2-3% of sites on internet now.
-Acquia – company created by inventor.

-2003, company is Automattic
-Support, hosting, services
-14.7% of top websites in world. 22 of every 100 new domains registered.

-“Open source matters” website

All of them-

What makes them great-

Huge developer community, lots of themes, modules, plugins, widgets, scalable, complex yet flexible, regular security updates, tools.

What makes them suck-

Huge developer community – conflicting themes/plugins, PHP versions – servers must be kept up-to-date with current version, modules/plugins/widgets can have issues because of outside changes, security updates.


-Installation- all pretty easy, one click installs for all 3, DRAW.

-Scalability – Drupal – best at managing huge amounts of content.

-Library specific stuff – depending on what you want, probably Drupal.

-Appearance – WP slightly, theme searching interface is very good. Unless you like to code/modify themes, then Drupal.

-User management – Drupal. Seemingly infinite roles/permissions. WP – not bad, started as one person/one blog, but getting better.

-Customization – all equal. Drupal and WP – lots of modules and plugins. Joomla - not as many, but there, can customize with time/patience.

-Ease of use – WP. Nice dashboard. Drupal, has done a lot of usability testing, working on it.

-Configuration and maintenance – WP. One click install, one click update. Batch update all plugins. Drupal – more intensive, have to do some in shell yourself, can configure every little thing and have to configure every little thing. WP – can, but don’t have to to get it to work.

-Upgrade and security – WP – easier for regular user. Drupal - more difficult, FTP, have to touch files on server. WP – seems to be less secure, not bad tho. Drupal a bit better.

Winner = Drupal and WP.

Drupal – big, powerful, good for a lot of pages files, WP - easy to set up, your mom can do it. 

Questions –

Another criteria – what if person who picks and installs the CMS you choose leaves? Is there someone else to support? What about Plone?

Which is easiest to learn when previous person leaves? Depends on complexity of your site, not dependent on platform you choose.

RFP – what limitations shouldthey look out for? How technologically advanced are your staff? Size of lib/staff?

WP – hosted on .com or on own server? Limitations to hosted – can only use their themes, if you want to do lots of customization, have to host your own.

Final thought from Kendra - Not one right answer – it’s what is right for your situation.
Links to this post
IL 2011: iLibrarian: Virtual, iPads & Mobile Devices
11/18/2011 04:39:00 PM | Author: Christa
Monday, October 17, 2011

Willie Miller Indiana University-Purdue University, Indianapolis (IUPUI)

Indiana Univ. Fall 2010, iPad learning community. Gave faculty iPads - go play. Figure out how to use them in teaching. Univ. funded initiative.

Library instruction with iPads.

Mobile research – library’s mobile site.

Journalism – use several different news/media apps. Compare how different apps display/discuss the same topic.

Collaborative concept mapping – Popplet – work together on project. One group used this as presentation instead of doing PowerPoint.

-Measuring outcomes

209 respondents to survey

Just started in Spring 2011

“all tools you need are right there and customizable”
“convenient and fun”
“easier for collaborating”
“time wasted when iPad wasn’t working properly”
“I’m faster writing notes on paper than with an iPad”
“found myself wanting to play with the apps rather than focus on course material”
”can get lost in the iPad and not focus on group work”
“checked my email and Facebook rather than participating because it was easier to hide”

-Best practices

Plan activities in detail and test technology – be able to troubleshoot problems.

Convey expectations – the amount of work expected.

Monitor activities carefully – make sure they’re on track, not checking email/Facebook.

Curate resources – keep everything in one folder – "this is the work for today".

Cultivate mobile information literacy.

Consider device limitations. Ie. Database searching not for iPads. iPads load pdfs slower than PCs.

Library on Demand
University of La Verne

Linda Gordon

Supplemental, not replacing in-person contact with students and instructors. Maximize our outreach during busiest 1st 2 weeks of semesters.

Optimize outreach activities.

Optimize student learning preferences.

Darryl Swarm

Pilot program – one campus, 5 classrooms, get feedback from staff, students.

Phase II – add campuses, one at a time.

Phase III – individualized/specialized instruction.

Kitt Vincent

3 facets of pilot program


Adobe Acrobat – standard that can be used in the future, already licensed to the univ. 200-250 students at one time. Screen sharing.


Faculty at remote sites.


Campus staff as project support.

Lessons learned:

-Skype – logins wiped every night.

-Hardware acquisitions – takes forever to go thru the proper channels to purchase microphones, etc.

-Leadership changes/commitment/monetary promises.

-Naming conventions changed throughout the project.

-Hardware durability – dropped in classrooms.
Links to this post
IL 2011: Transliteracy & 21st Century Skills for Library Users
11/18/2011 03:00:00 PM | Author: Christa
Monday, October 17, 2011

Learning for Life Online at the Boston PL
Jennifer Koerber, Web Services Librarian, Boston Public Library

-Choosing a structure

Blog? What if people join then abandon their blogs? Tons of dead blogs. Wiki? Chaos. Ning – ad based, closed. Moodle – would work well as part of an overall training program. Lot of work to set up.

Take a few tools, put them together to create the platform. WordPress site, Facebook page – that’s where people already are, wouldn’t have to come up with a whole new blog. Twitter – another convenient tool for pushing the lessons out. In person events at branches, off site, other conferences – trainings, social meetups, unconferences.

NTIA grant – laptop lending program and training.

Decided to wait until laptop program started to launch Learning for Life Online.

Each entry - Intro, what is it? How is it useful? Suggestions for trying it out, helpful resources.

No formal registration – drop in program, no way to scale it to a large city if having to register.

Track outcomes – Google analytics, Facebook shares, followers, Twitter stats.

Colorado Public Computer Centers
Jaimie Hollier, Project Coordinator, Colorado Public Computer Centers, Colorado State Library

BTOP – 80+ new and enhanced Public Computer Centers. And trainings – how and why they need to be online. Jan-June – trained over 3000 people.

Lessons learned:

-Digital literacy is a functional building block toward transliteracy.

-Partnerships are paramount to success. Too much to do, too many people to reach, too little funds.

-Step back and take a look at the big picture. Instead of ‘we’re teaching email’, should be ‘ we’re teaching people how to connect to their families’, teach something that means something to the people, otherwise they won’t remember it.

-Follow and inform national policy. People care that libraries have a place, tell people.

Digital Core – FCC. Working with IMLS, Microsoft and E-rate. Getting people out training on digital literacy.

Digital Promise. How do we make learning better thru technology?

Digital – not fulfilling the need it was supposed to be for, NTIA knows that. So they’re working on it, keep an eye on it.
Links to this post
Monday, October 17, 2011
Nancy MacKenzie and Lisa Hardy, Calgary Public Library, Alberta, Canada

Calgary Public Library - 800 employees, 18 branches, serves city of Calgary, a little over 1 million people.

Organizational structure – barrier to change, need to figure out how to create a space in the structure to innovate.

2 initiatives at Calgary PL.

1st Learning Initiative: Librarian Led CPL Supported Training


1-Explore relationship between traditional reference and community info question.

Librarian – lead the exploration, articulate the unique contribution of the library, have courage.

CPL – provide the space and structure to start the conversation.

2-establish organizational direction in working with our communities in different ways.

Librarian – identify opportunities, personal learning requirements, provide leadership and direction.

CPL – create structure that supports innovation, creativity and leadership, and success in and for the community, alignment with strategic directions – how what librarians are doing aligns with organizations directions, measure success – identify strategies and measures.

3-Provide real leadership opportunities for librarians.

Librarian – seeing what needs to be done and doing it.

CPL – Leadership Action Team (LAT), provide opportunities to emerging leaders, mostly librarians but not exclusively. Series of workshops, traditional staff development day. develop valuable public speaking skills, participants say being able to work with CEO is a great benefit.

Emerging leaders training program – develop managerial skills.

Formal project management training – planning, project reporting, timelines, alignment with strategic directions.

Coaching – managers learn about effective listening, following intuition, less about problem solving and direction and more about supporting people in their training.

4-Support librarians in taking responsibility for their own learning- in a system supported way!

Librarians – identify what their learning needs are, come up with strategies to share and further system learning.

CPL - $$, structure and time.

5-Explore the relationship between who we are in the community and who we are as a community.

2nd Learning Initiative – Future Action Think Tank

Engage staff in thinking about future of libraries, sharing ideas, influencing innovation and being a part of change instead of just having change happen to them.

Future Action Team runs the think tank.

Staff engagement very important. How do you plan an event for everyone?

-Pre-conference – blog, ”what is a library future?”

Engage staff and spark curiosity.  Encourage conversations.  Open tumbler blog. -feel free to read and contribute.

Imagine the Future – 1 day event, scheduled for Dec. 7. Needed to do something different from previous traditional leadership training, which was too formulaic and didn’t encourage innovation.

-Futures Fair – departments present on what they do, like IT, etc.

-Field Trips – send staff out to different organizations to talk about Collections, Services, Spaces, Staff & The Workplace, Technology. Asking other organizations who serve the same community the library does, to further understand the community. 80 staff. $5000 budget. Return midafternoon. 1 hour of reflection time.

-Tackle Teams – informal groups, formed based on common interest in a topic. Read, discuss share with peers, provide a channel for them so ideas will be heard throughout organization.

To attend, Staff submit ‘expression of interest’, why they want to come and participate. Not just required attendance like previous training.
Links to this post
IL 2011: 20 Steps to Better Web Services
11/17/2011 02:58:00 PM | Author: Christa
The Librarian in Black.
Monday, October 17, 2011
Sarah Houghton

We are broke
Free=useful, maybe we’re becoming too reliant on free stuff. Maybe we should learn and do things ourselves.

#1 – Where to put your website
Blogger – still flexible platform, small, easy.
Drupal – if you have lots of time to learn it. Super flexible, make it look how you want it to. Open source. Good for larger site needing a big redesign.
Squarespace – Almost free. For around $500, did entire city website, CMS that works, mobile platform hosted. Easy to learn. Even staff who hate technology and websites are learning and blogging.

#2 – Images
Gimp – image editing program. Like Photoshop. Open source, free. Intermediate to advanced people.
Picnik – in browser photo editing. Simple photo editing tool. Flickr uses it.
PictoBrowser – Flickr slideshow. – high quality photography. For finding stock photos that aren’t illegal for you to use.
Creative commons search in Flickr.

#3 – Hot Topics
Addict-o-matic – pulls in items from many sites – Twitter, Bing, Google blog, YouTube, Flickr, etc.

#4 – make ur codez priteeez
beautifyer – java, css

#5 – Surveys and polls
Google forms – excel spreadsheet with results.
Polldaddy – simple polls, see percentages, easy to embed in website.

#6 – Slider
Wow slider – rotating slide show, doesn’t use flash – good. 10 minutes to have one up and running.

#7 - Translate
Google translate – free, it works, language of your choice. Put it near top of page, users will never get to the footer. Audience comment – do not use for medical info, terrible.

#8 – Remote assistance
LogMeIn – remote access to pc or mac. Email with link, gives permission to drive their computer. Free. Make sure they know after the session is over you can’t be in their computer anymore.

#9 - Wireframing
Balsamiq – mockup websites. Premade graphics as placeholders.

#10 – Test your mobile stuff
W3C – mobile OK checker, simple, easy, it works.

#11 – Stats
Google analytics – free, simple, easy. Insert tiny snippet of code into your site. Don’t need any skill.

#12 - Skype
Use for online ref/chat. People are using it anyway.

#13 – Social management
Tweetdeck – monitor multiple twitter accounts. Alerts.
Namechk – check for already used user names, when setting up profiles.

#14 - Webcast
Slideshare zipcast – for webcasts, like WebEx but free, live video feed plus slides and chat. Had up to 200 people on at same time, no load issues. Archives.

#15 – Video
JayCut – browser based video editing tool. Upload video, edit, then download finished product.
YouTube - video editing has gotten better.
Animoto – create video of still photos add animation, music. Free pro account to non-profits.
Xtranormal – give it a script, makes an animated movie.

#16 – Audio
Audacity – audio editing tool.
Podbean – host audio.

#17 – Learning environments
Moodle – good, hard to learn and implement. Good for full feature online class.

#18 – Infographics – build your own.

#19 – LibraryThing
Strong, simple.

#20 – Google
Really good free stuff.
Plus – might be able to integrate into our websites.
Links to this post
Internet Librarian 2011: Better Late Than Never
11/17/2011 02:34:00 PM | Author: Christa
It's been a month since I enjoyed yet another great time at Internet Librarian in Monterey, California. Since then I have been crazy busy both at work and at home, so haven't had any time to share my experiences there. I've finally decided to get this done, before the next one sneaks up on me. First an overview of some things, then I will post my notes from the sessions I attended.

On Sunday morning, October 16, Michael Sauers and I presented our pre-conference on Webcasting and Podcasting. We shared how we run the Nebraska Library Commission's NCompass Live online show with a small, but very lively, group of librarians.

On Tuesday evening, I attended the Great Web 2.0 Face-Off. A hockey themed competition to see who knew the the best collaborative tools out there. Yup, you read that right. And it was Awesome! I think I learned something, but it was hard to tell thru all the laughing. I hope they keep this on the program!

Blue Team!
Lisa, Michael and Blake - The Blue Team!
Red Team!
Ruth, Jeff and Amy - The Red Team!

On Wednesday morning, Michael and I once again did his monthly NCompass Live Tech Talk, LIVE from the conference. A few friends, who brought their friends, and even one of our pre-conference attendees, had a lively discussion about many issues floating around the conference that week.

Live broadcast of NCompass Live

And, there was also a bit of non-conference fun...

Rotisserie Truck!
Rotisserie Chicken Truck at the Farmer's Market!
Royce on the beach
Hanging on the beach.
Sleeping Seal
And seals, of course.
Cannery Row
Shopping and dinner on Cannery Row.

Next up...what I learned at Internet Librarian!
Links to this post