Chicken if ya don’t!!!


That is the mantra from this past weekend for certain. We all had a pretty good time in TN this past weekend. Early in the weekend we met up with a noble gentleman visiting the faire (seems he was the former king of TN) and while Bob and Neisha were goofing around he turned to Bob and uttered the words that shall evermore live in infamy. “Chicken if you don’t” “Chicken if you don’t” “Chicken if you don’t”!!!


Shank Hall Seelie

Tonight I made the trek to Milwaukee once again. No surprise that it was again to see Seelie Court. This time they were the opening act for the Fenians. Seelie put on around a 45 minute set, a little faster than usuall on most tunes but man was it fun. Unfortunatly because it was a Thursday there were very few people there at all. I left after Seelie finished because I’m heading to TN tomorrow. When I left there wasn’t really that many more people there for Fenians than there was for Seelie and I know at least five people were there in support of Seelie Court. All in all thoguh a great time, and well worth the drive from Sugar Grove to MKE, then from MKE to Somonauk. Yup I’m nuts 😀 I wouldn’t have it any other way…

Firefox Fun

Well, I submitted my plugin for the FireFox Search feature to “The Shifted Librarian” and she posted it on her blog. There have been a few comments and some requests for information oon how I did it. I wrote the following quick HowTo for it that probably needs a LOT of correction…

HowTo add search functionality to FireFox.

There really isn’t all that much to it. It is actually easier than it looks. You basically need three files. One is the graphic, one is the Javascript for performing the install, and the other is the plugin file for FireFox. The functionality for searching with FireFox is actually the same as it is for the netscape / Mozilla sidebars however I was unable to get the results formatted quite right for those browsers so for the moment I am leaving it as just a FireFox addin. Your results may vary.

Step One: Decide where on your website the files will reside. I created a separate directory called “Mozilla” to house all of the files to make maintaining them much easier. This path will be needed in later steps so make note of it. (Mine is:

Step Two: Create your image. The image can be a .gif or a .png formatted image. I myself prefer the .png format because that format has had less copyright problems over the years and is much nicer to work with. The image must be no larger than 16 x 16 pixels. This size just happens to be the same size as a favicon.

Step Three: Create the .src file. Using the instructions and example found at: create a file with the name of your choosing, I used catalog.src You probably want to make it unique to your library. If everyone names their plugin catalog.src we will only be able to add one catalog at a time.

Step Four: Modify the example .src file to fit your library. The following items will be unique to your library:
(Note: there is a automatic generator that I did not find out about until after I wrote all of this, located at that should help create the .src file)

  • Examine the <search> tag in the .src file there are a number of elements in it that need to be altered to fit your environment.
  • You should not need to change the version element, so leaving it at 7.1 should be fine.
  • The name and description elements should be self explanatory.
  • In the action=”” element you will need to place the search URL for your catalog. This is the URL your search form submits information to. Take a look in your catalog for the <form> tag, the action element on that page, and the action element in your plugin will most likely be the same. URL Parameters, Items following a ? and separated by & should be included using the <input> tag. I will go into more detail on this later.
  • Change the ‘method=”Get”‘ element to match the method element in your catalogs <form> tag. This controls how information is sent to your library catalog.
  • Change the ‘searchForm’ element to point to the regular page your patron would visit to start a new search in your catalog.
  • After the closing > for the <search> tag you will see a couple of <input> tags listed in the example. These tags are basically the same as any input you would pass along to the catalog via the URL parameter including the text the user wishes to search on. In the case of Web2 we have to specify a few additional items such as “setting_key” and “servers” in order for the search to work correctly. To do this, there needs to be a separate <input> tag for each parameters. If you are at ll familiar with creating forms in HTML this will be easy. The one key item is the tag in which the users search information belongs in. This tag contains the element “user” instead of the ‘value=””‘.
  • The next tag you need to modify is the <interpret> tag. This tag contains the information Mozilla needs in order to interpret your results. In my case I left the example alone, and inserted the various comment tags into the appropriate places in the HTML for Web2. I found this easier than figuring out preexisting unique strings returned by Web2.
  • Finally you will need to make a couple changes to the <browser> tag. This tag contains the exact URL of this file on your web server, as well as the location of your icon file for this tool. This is where you need to insert the path you decided upon back in step one. Edit the update element to point to your .src file, and the updateIcon to point to your .png or .gif image. These elements tell Mozilla where to go to re-download the plugin when the number of days specified by “updateCheckDays” has passed. This allows you to make changes to your plugin and have them automatically update on the patrons browser w/o them having to re-install.

Step Five: Insert the installation Javascript into a test web page. I use the <include> tag to help keep the function code from making my website a mess. The Javascript is located here:
You will need to modify a few lines to point them to the correct URL path for your plugin.

Step Six: Test your plugin, and make changes as desired. When everything works the way you want it, visit step 8.

Step Seven: Insert the installation Javascript into your website. I use the <include> tag to help keep the function code from making my website a mess. The Javascript is located here:

Sales Drones

As some of you know I work in a library. One of the best bennefits of this is that I have the PERFECT response to mazazine / newspaper sales people. Today, one such call came in. The call went something like this:

“Hi my name is Kerri, and I’m with ______ magazine and I’d like to offer you a free…”
Me (interrupting): “I work in a library….”
Kerri: “Huh? you mean you are not a __Technology Assistant__ anymore?” (The inserting of database information into the conversation was quite obvious.)
Me: “No, I am still a technology assistant, for a Library…”
Kerri: “… but so wait …”
Me: “I work in a library. The library receives a subscription. I get it routed to my desk. Therefore I do not need my own.”
Kerri: “uhhh… ummm…” [pause]
Kerri: “Ok, well is there any other technology person in the library that needs a copy?”
Me: “No… It’s a library and we don’t need to have more than one copy…”
Kerri: “Uhh… ok… that’s wierd…”
Me: “Thank you, good by”

I think it is one of my goals to someday be a footnote in a magazine / newspapers sales training handbook…