The more the better! But what happened if they are scattered all over the place!

We have our summer reading program going on at the library I work for. The library purchased the software/program from Evanced to handle the online reading logs, and reviews for the program. This is not in my area and I was never involved in the decision making process. Anyway it is up and running as it is, and as far as I know we have a pretty good turn out. Lots of patrons signed up online and posted their reviews.

On the other hand, I have pushed to purchase yet another catalog review/rating engine for our library -- Chilifresh. It can be easily integrated into our online catalog and is already very popular among some public libraries. Anyway, this will be yet another place for our patrons to post reviews.

Now here comes the question. What to do with these reviews posted on our Summer Reading Program after it ends. This was asked by a staff member on our staff blog. Are we simply going to just delete them? Keep them for next summer? Add them to our online catalog? (well this person does not know that this cannot be easily done)

The person asking the question does not know about the Chilifresh project I am working on but this person asked a very good question. It is a key to think about how we offer our services.

More is better, isn't it? More services to our patrons is of course better. But what happens if they are scattered all over the place?? Does that really offer much convenience to our patrons? Log in here to leave a review in our SRP... log in there to leave a review on our catalog...

This is not user friendly at all. More is not better when you are sending patrons all over the place to do things they should be able to do in one place.

I do not have a specific solution to the issue that our staff raised. I don't think that there is a way for Chilifresh to load the reviews we got from Evanced into their database so that they will show up in our catalog. We may have to manually do this if we want to preserve the reviews our patrons wrote for the Summer Reading Program.

If only we could have thought more about these two separate but yet similar services we are offering to our patrons and planned a better way to integrate them rather than offering both but at separate places. Personally I don't like the review section on Evanced. It looks pretty ugly. There is a rating system but it does not display. On the other hand, Chilifresh has a star rating system that displays right up front. The reviews look like they are part of our catalog. We get reviews from not just our patrons but from all participating libraries.

I don't know how my boss will answer our staff. I am just frustrated that we did not do a better planning job as we should have, and I feel like we do not have the vision to offer more integrated an user-friendly services to our patrons.

This is when I really regret that I don't have a CS background...

and/or too lazy (according to hubby) to pick up any significant programming skills!! AW!!!

Library Applications Developer
The Brown University Library seeks a talented software developer to design new and innovative web-based library services, systems, and tools which anticipate the needs of library users.

In addition to developing new applications, the incumbent

• makes creative use of APIs
• continually enhances and extends commercial software applications
• works with library departments to develop tools which increase internal workflow efficiencies
• provides vision and leadership in the investigation and implementation of emerging information technologies

The Library Applications Developer is part of the Library's Integrated Technology Services department.

Qualifications:

• Bachelor's degree in Computer Science, Information Science, or a related field; or the equivalent combination of education and experience.
• Experience in the designand manipulation of relational databases; demonstrated proficiency in developing and maintaining database-driven web applications
• Experience developing and coding interactive web applications using PHP, Python, Ruby, Perl, HTML, XML, CSS , SQL, Javascript, AJAX, and/or other common tools. (AW!)
• Demonstrated experience with Unix or Linux server platforms, related software, and basic system administration utilities
• In depth knowledge of Website design, development, implementation, standards, and accessibility/usability guidelines.
• Experience with Web 2.0 technologies such as RDF and AJAX and with designing and implementing web services (REST). Ability to integrate Web 2.0 services to ensure the seamless delivery (this is the key!) of online library services.
• Excellent communication, interpersonal, and organizational skills
• Creativity and strong analytical and problem-solving skills
  Ability to learn new technical skills quickly; ability to meet deadlines; strong service-orientation. Ability to adapt emerging technologies to new domains.

Preferred Qualifications:

• MLS from an ALA accredited university
• Hands-on experience implementing and managing library enterprise systems

Ok so I am not a programmer and probably will never be. But where could one go to work with someone like that? That would be any system librarian's dream to work with a team of developer(s).

Integrated, easy and transparent user experience!

Folks at the Brown University Library have been doing some interesting stuff. I just happened to come across this while visiting there not too long ago. But they put out a new service called Easy Borrow, which provides "a single user interface for automated requesting of returnable items from multiple shared resource systems."

It's not something of great interest to public libraries unless you are part of a consortium. But it is a wonderful new service for users of academic libraries. Users only need to log in once. The automated system repeats their search in each one of the resource systems (start with Brown's own catalog) until it finds one with a copy available. If none of the other resource sharing systems have an available copy, it then goes into their ILL system ILLiad.

Users do not have to repeat their search in different catalogs/databases. Users do not have to log into different databases because they only have one single user interface they have to deal with. Plus, they don't even have to know where their materials were borrowed from, why should they!! This has made it much easier for staff also because they do not have to repeat users' search because the system is automated so it will attempt each resource before it goes into ILLiad.

Great example of integrating technologies and resources to present a wonderful, easy and transparent user experience!!

Brown is currently sharing the code in Google Code. Eventually they will host the code themselves and continue to share it with others. I wonder if the academic communities have expressed a lot of interest in this!