My colleague is teaching a Python course. It’s so popular that it’s got a waiting list 3x longer than the registered list. He kindly made a short resource guide to share with others. I had fun making this page to represent it.
It took me a few times to get the header image correct.
Last Friday I was interviewing a colleague about the library’s website when she mentioned a point of confusion for patrons. Our book group titles show up in the same record as non-book group books. That is, when a patron looks at our website, they see that we have 10 copies of the hottest title and may hurry in to snag it. They’ll check the shelves only to discover it isn’t here. The front desk staff then explain what a book group title is within the catalog.
That got me to thinking. Previously I had made a form for book groups to request their books online. Before that, they had to email directly or call in. The trouble though is that the form does not show up on the same page as book group books in the catalog. So a form submitter already has to have the title in mind when they go to a separate page to make their request. I didn’t find that to be the best process, but I couldn’t get the catalog updated to put a form in on the page (or a link to the form) from the catalog records. Back then, the book group books were not merged with all the other physical books of a specific title like they are now.
Now onto my idea: why don’t we pull the book group titles out of the catalog completely? If we do that though, how do we make them available? A Drupal webform. I could make a new content type for this specific case. Then add custom fields like: genre, type (e.g. short story, poetry), links to review sites, the book cover upload field, and a summary alongside the webform. On the backend, the webform would have a hidden field which takes the title of the node. When a group submits a request, our book group people would get an email which has the relevant information they need in an easy format for them to read.
But how does the group get to the individual book record? I’m glad you asked. There would be a grid layout of book covers for all the book group titles. At the top, you could filter by genre or type, or search for a book. There would probably be additional fields to filter/search by, but those were my starting point. I took this idea to book groups that loved it. I told them that it’d be best if we could recruit a few other hands to help with getting the 300 books in the collection to the new format. However, we had to have final approval before whipping this new experience together.
My idea has been tabled for now. With a new website coming out next year, it would not make sense to invest time getting these 300 books into our current site. We may have to just redo the work on the new site if we run into any trouble with migrating the data. In the short term, I am disappointed. However, I understand the reasoning. Right now I’m still in the discovery phase of the new website (interviewing patrons next). This idea can wait. I look forward to sharing the reality of it next year.
From the screenshot above, you probably can’t tell much about changes from the finished product to the previous one I wrote about. Oh, you’d be mistaken. Let me show you a little bit about what happened behind the curtain:
The site took around 25 hours to complete. This is despite the fact that I was working on top of a framework that I established three years ago. The issues are numerous such as there not really being a CMS to work with. Any style change I make on the front page will show up on the logged-in homepage. The logged-in version has additional content. This content climbs on top of the content that was already there. So you have to figure out a way to assign classes to the logged in vs. logged out versions of the same tables (yes, tables).
The backend of the site is not divided into one master stylesheet but into many stylesheets per page. Yes, page level. So if I set the background to be X, Y, and Z on the homepage, I had to visit every other page and set up that new background code. It made the process very long and drawn-out.
My favorite part
My coworker sent me the image from the front of their summer reading brochure. I took it apart in Photoshop and added shadows, removed the spotlights, and created a semi-repeating pattern to use as the background. When I added that to the site, I realized I wasn’t happy with it. So I then pulled apart the curtain into multiple layers (with the courtesy of a transparent background and an eraser). I then ran drop shadows over the new individual rows. I then ‘shopped them back together.
What I didn’t incorporate
My colleague’s original design included spotlights. I wanted to add spotlights which would sway gently or slowly warm up. Something cool with CSS3. However, by the time I got to the end of getting it structurally working, I was done. So done.
The above is a work in progress. This is our third year of using Evanced’s Summer Reading software. What I’ve done so far is clone last year’s site and then made adjustments for this one. You can view last year’s theme below. I was in the process of starting to dismantle its interior when I remembered to take the screenshot. So forgive the out of alignment aspects.
Regarding this year’s theater design, I wanted to have a curtain that could be lifted with a click of a button. Alas, it was not meant to be. I could probably have done it if I had full control over the site. Unfortunately, it’s table-based and all I can do is some CSS manipulation. Below is what I believe is this year’s default theme.
I’m having trouble with our design because it’s breaking in Firefox. I’ve tested it in multiple other browsers (including IE) and it looks on fleek. Firefox has been my nemesis for years in this regards. However, I am using Firefox’s 3D model of the divs to help me pinpoint the different parts of the page are on the site. I’ve completely swapped the original two columns so it can get confusing. Also there isn’t a master stylesheet but approximately 50 tiny ones.
Hopefully by this time tomorrow I’ll be able to share the completely redesigned site!
I was given the task to set up an internal staff blog. I choose WordPress, of course. The constraints:
- easy to use
- easy to update
- easy to navigate
Advanced Comment Form: to remove unnecessary fields like website address
Subscribe to Comments Reloaded: so commenters get notifications when someone replies
USP Pro: Creates front-end post submissions without an account. This was something I choose since people complain when they have to create and remember even more accounts. So I eliminated that. They’ll just have to put their email address in every time. We went with pro since we wanted to be able to upload various file formats. There may have been a free solution, but it wasn’t worth me spending even more time researching a new plugin and then configuring it to work with the setup.
Use categories to organize the site + tags.
Created a video to show people how to use the site.
Use custom menu for “Write Post” link option.
Twenty Fifteen theme
Very minor tweaks to correct the appearance of lists
My additional requirements that I put on myself:
- easy to comment
- get notifications on your posts
- get notifications on new comments to posts you replied to
- email all staff when a new post is submitted
I am in the process of fixing two bugs:
Our all-staff email address is limited to only forwarding emails from our own domain address to stop outside spam. My colleague and I are working on a solution to this. It’ll probably deal with emails being sent to me and an Outlook rule that will auto forward that email to all staff from my inbox.
The person who wrote a post gets two comment notification emails whenever someone replies to what they wrote. Still trying to track that down…!
An annoying WordPress bug is that it’s not sending me native notifications of new post submissions, thus why I had to look into an outside plugin.
The big image was co-created with my colleague’s help. My inspiration was the new iOS site which is big on image with text next to it.
I finished prepping the website for the long holiday weekend. Most of the day though was spent on writing up documentation for the Digital Media Lab on digitizing VHS to DVD. Then I updated the library’s main eBooks web page. It’s plain but I’ll keep working on it!
First day back after Christmas! There was some chaos in the Digital Media Lab which has left me on edge. The supervisor of the area is going to be looking into it. Hopefully in a couple weeks we’ll have things settled and on-track regarding the room. The big thing for the day was working my two hour slot for eReaders are in the House. I had two patrons whom I spent an hour with each. They were non-residents so they cannot check out eBooks from us, but I could teach them about their eReaders. The rewarding part was seeing their confidence grow.
I worked on the forthcoming 21 Things for 21st Century Parents website today. Last year I put the website together very quickly. This year I am making each individual icon/badge in Inkscape. I am going with a circular design which is really hot in web trends at the moment. When I have the site ready to share, I will!
Today being Thursday, everything is dominated by the chunk of time I am manning the Help Desk in the computer lab.
So I came in and worked on finishing preparations for the Winter 2013 classes. We decided to keep the structure the same this “semester.” Depending on the participation we see for this round, we may mix things up for the Spring classes. We are using Wufoo for the class registration thanks to its ability to open and close automatically based upon entries. Then I wrote customized confirmation emails per class. I’m also asking teens one-on-one what sort of tech classes they would be interested in. Tomorrow I get to utilize the Teen Librarian’s mailing list to directly email teens and invite them to sign up for classes. While working on this, I rocked out to Destiny’s Child.
Following that, I finished my part of redesigning the Readers’ Advisory page. The table mimics the layout of the main staff directory listing. I sent some suggestions onto the Head of RA on how to improve items.
In-between items, Heather McCormack, formerly of Library Journal and now with 3M Cloud Library swept into the UX office. I was elbow deep in my work and heavily distracted. However, Heather recognized me and even the place we had met before (Digipalooza in August 2011). I was impressed! She’s got quite the memory.
The good news for today is that my goal to move the Tech Books collection from the Lower Level (basement) to the main non-fiction section is now under away! The Head of Reference is now looping in all of the relevant people to make it happen. I’m very excited for this to happen as this has been my pet project this year. Hopefully my circ numbers will start climbing.
Then I wrote an email advising on LibGuides to another library department today. I probably sounded like I was coming down too hard, but I want them to know what they’re facing. In short: creating LibGuides is challenging.
Help Desk was entertaining as usual. In between patrons I worked on my set aside project: doing a content inventory. I discovered a whole new batch of posts which are ripe for deleting. I’ve received the green light from that department’s head but need to talk to the person who wrote the posts. This is perhaps not the best way to carry out a content inventory, but vicious pruning makes it easier to see what gems the website has buried within its thousands of posts. I also managed to sneak in introducing a patron to the DML. Score!
Finally, I wrapped up the day with a surprise stint on the Welcome Desk (circ). I was called up to help load a 3M eReader. This led to me helping re-fresh one staff member on the process and then showing off the 3M Cloud Library kiosk and eReader to another patron. I had changed out the text on the 3M kiosk last week to be more direct “Don’t have an eReader? See the Welcome Desk” (which is problematic for EOSL folks — oops). It seems people are thus asking!
Today the Collection Development Librarian from the Children’s Library was kind enough to send me the policy she had written up. I then spent 45 minutes modifying it to fit the 100 or so books that make up the Tech Books Collection. I’ve sent the first draft to the Head of Reference and our overall Collection Manager (?) for feedback. While it may be silly for one tiny collection to have its own policy, I wanted to create something solid that will ensure the collection is not left out in the rain again.
Inbox zero continues to elude me. My Outlook inbox doesn’t sync correctly so the only inbox that is properly sorted is on my Windows machine. This computer was in storage for two months after the flood, so now I have 200+ emails that I’m slowly sorting into folders. I figure that if I do ten a day I’ll eventually get there.
I had moved my schedule around to attend SpringyCamp for LibGuides. Then when I looked at the schedule did I realize that only one session even remotely applied to my work. The session from Mount Holyoke was great — they asked students to draw their perfect LibGuides portal. The librarians then looked at all the results and improved their guides from the students’ suggestions.
Next, I had a good chat with the new head of Readers’ Advisory. I found out that the people who come to the Welcome Desk to check out do so for three reasons: really don’t have their library card, prefer face to face interaction (usually older patrons), or have their hands full so they can’t dig out their cards (people with children). She then mentioned that teens don’t have their cards but they’ve memorized their number. So I went upstairs and poked at the 3M Self Checkouts for a bit. When I returned to her, I had turned on the ability to type in your barcode and added a button to switch the screens between English and Spanish.
I also set several balls rolling:
- Two new automatically aggregated panels from web posts
- Looking for a badge to mark that we’re a Five Star Library (according to Library Journal)
- Trying to find a guide on networking to order for the Tech Collection
Finally, I met with my boss to get some help in narrowing down on what projects to work on. I’m going to continue to learn Github, look into a metadata schema for our digitization project (Dublin Core, anyone?), work with 960 grids, and responsive design. I then ended the day by finally fixing some CSS padding issues. Hopefully tomorrow they’ll be rolled out on the website.