| /* I'm assuming you are using jQuery for simplicity sake, but you can do this with straight JS too */ | |
| /* Include this file right before your closing </body> but after you include jQuery */ | |
| $(document).ready(function() { | |
| // Get the database name. | |
| // This script assumes there is only one, & you don't already have license link | |
| // You'll have to account for other situations | |
| var databaseName = encodeURIComponent($("#DatabaseCL").find("a").text()); |
We use Illiad for ILL, and have heavily modified it. One thing that came up this week was how bad the renewal confirmations are. I wrote a quick script to fix that. Here's what it does:
Why yes, it is useful to have 2 separate alerts there. Thank you.
| #! /bin/bash | |
| GREEN="${BOLD}$(tput setaf 6)" | |
| BOLD="$(tput bold)" | |
| ALL_OFF="$(tput sgr0)" | |
| function schedule() | |
| { | |
| echo -e "\n${GREEN}Schedule a new appointment:${ALL_OFF}" | |
| read -p "${BOLD}Date:${ALL_OFF} " DATE | |
| read -p "${BOLD}Description:${ALL_OFF} " DESCRIPTION |
| set archivedTasks to "" | |
| tell application "TaskPaper" | |
| tell front document | |
| -- don't care which file your log entry came from? | |
| -- comment the next line out | |
| set archivedTasks to "## " & name & return | |
| repeat with _task in search with query "project != Archive and @done" | |
| if entry type of _task is not project type then | |
| -- remove common tags that won't matter after archiving | |
| repeat with _tag in {"na", "next", "priority", "waiting"} |
| user_id | email | major | last_updated | |
| ------------+----------------------------+--------------------------+--------------------- | |
| 1231o8433 | joeblow@library.edu | Economics | 1375980483 | |
| ------------+----------------------------+--------------------------+--------------------- | |
| 873648737 | sueseashells@library.edu | Philosophy | 1375980483 | |
| ------------+----------------------------+--------------------------+--------------------- | |
| 879472974 | billybob@library.edu | Engineering | 1375980483 | |
| ------------+----------------------------+--------------------------+--------------------- | |
This is what the absolute positioning looks like. Yuck.
If a patron tries to request an item and their account is locked, they get this terrific message. Besides being HUGE RED TEXT it is completely unhelpful in letting the patron know who to ask and how to get ahold of someone who can help them. So I fixed it with CSS and markup, since this silly message is hard-coded and can't be changed. You just need to edit the request_result.html file in Web Master and look for the section that looks like this:
<!--{iferror}-->
<!--{errormsg}-->
<!--{else}-->Libraries have jumped on the User Experience bandwagon of late, rethinking our tools and services with a new focus on patron needs. But we still see things differently than our patrons. Where we see discrete services supporting our larger mission, patrons only see a confusing website. Without a holistic view, we spend our time solving the wrong problems.
Fortunately, we have everything we need locked up in data silos. In this presentation, I'll talk about how to get that data out of the dark and make it a powerful tool in reshaping your library's commitment to service.
Do you know your library website needs work but you're not sure where to start? In this workshop, I'll show you a number of ways to improve your library websites quickly and easily. Participants should be willing to volunteer their own library websites, and will walk away with an understanding of how to fix common website access, usage, and performance problems and also how to measure the impact of these changes (all in 90 minutes!).
I'll take volunteered websites and work through a number of common problems that might be plaguing the site, including usability, accessibility, and performance issues. By using the browser's Inspector, I'll show participants how to make changes to a site on-the-fly and quickly measure the impact of that change by using online tools. I'll encourage participants to follow along on their own computers, and give some exercises to learn the basics of the Web Inspector.
In his book, The Hero with a Thousand Faces, Joseph Campbell laid out a narrative pattern he saw across myths, stories, and religious rituals that he called The Hero's Journey. The hero moved out of the ordinary world into the "Special realm," where she encountered all manner of obstacles before coming back to the ordinary world transformed.
As librarians, it's easy for us to forget that many patrons leave the ordinary world for the "special realm" of library research databases when they use our services. For decades, these tools have been disconnected, proprietary tools that require a truly epic amount of effort from our hero/patrons if they are to find their treasure (usually articles, books, or citations). But it doesn't have to be this way. We can make the journey easier for our patrons with the right tools and an eye toward improving the search experience.
More information on the conference at [http://www.ni