Clogged Drain

A number of months ago, I turned my mind to a developing problem: A slow drain. Not just any slow drain, an incorrigibly slow drain.

The obvious solution was the usual. I released the pop-up drain plug and cleared out all the accumulated hair.

That worked a little, but it was still not the drain of old. I've gotten a lot more tolerant of problems as I've gotten older, so the next effort didn't come for another couple (or more) weeks.

The next solution was to drop the drain trap and give that a go. I cleared out a good bit of accretion, but found to my surprise that the drain was still slow.

As far as I'm concerned, the thoughts I'd devoted to this problem don't constitute i-candy. Half-baked ideas and theories are what I call i-ruminations. (Our instructional technologist called them once ruinations. There may be some truth to that.) These efforts only become i-candy when they've reached the level of revelation.

The question was where did the clog reside? It wasn't in the stopper or the trap. In fact, I removed the drain pipe to the wall and cleared that outflow pipe right to the down pipe. So that meant the blockage had to be in the wall. The next step would have to be a professional plumber with a snake. But I'm as cheap as the next homeowner and didn't want to go that route until I'd exhausted the next easiest options. Short of borrowing a snake from some as-yet-unknown friend, I didn't immediately know what that option was.

In this case, I let the problem persist for a few more weeks as I continued to ruminate. Every time I used the sink, though, I'd devote more mental capital to the problem.

Actually, I did have an idea of the next easiest solution, but had already implemented it without any success. I'd taken a plunger to the drain at least twice, each time with no significant improvement in drainage.

But why hadn't it worked? If the developing blockage was in the wall, perhaps it was farther down the drain. If it was far enough down, the plunger could have failed simply because any change in pressure from the plunging action would have been inadequate so far away from the source. After all, air is a highly compressible substance; gases are like that.

If you blow through a short length of tube, the air coming out the end is pretty close to the pressure of that coming out of your mouth. As the tube increases in length, the pressure drops simply because of the compressive nature of gases. You have to blow much harder for the output pressure to be equal to the output for a shorter tube. The pressure change from a plunger is going to be pretty constant, so the farther away from the plunger the constriction happened to be, the less impact there would be from the plunging.

When the drainage matches the flow from a faucet trickle, desperation sets in. Oddly, the solution still didn't come in the form of a call to the plumber. My willingness to spend money had not increased an iota. So out came the plunger again. I didn't give up so easily this time. I shoofa-shoofaed a score of repetitions.

To my surprise the drainage improved. The flow now matched the flow from a modest faucet stream. It was time to ruminate.

If the septic accretion was further into the wall, why had any more plunging made a difference? (My willingness to try again was a bit less baffling. The cost of plunging is infinitesimal. The cost of a plumber? Shudder.) Repetition can be remarkably effective. The voice of a child asking for a cookie once is irritating. The sound of a child asking for the 100th time is erosive. (We do all know what happens if you give a mouse a cookie don't we?) I think what happened with my drain was that repetition did what just a few plunges failed to do; it gave an opportunity for some of the accretion to become loosened and freed.

I have a theory that plunging the drain for a longer time could make the real difference. I'll probably have to wait for the constriction to increase in order to maximize the pressure and its effectiveness, but if I'm right, I should have a freer drain, my hard-earned cash still in my pocket, and a happier wife.

I'll let you know. There may be some i-candy in it for you.

Twitter and Blogger

I knew a little about the benefit of tweeting from a New York Times article, but I've come to my own conclusions after 3 weeks of tweeting and blogging.

Background
I came to Twitter via the one person that I'm currently following: Joyce Valenza. As an adjunct professor who teaches a course on technology for school library media centers at Arcadia University, I have 2 field trips I take my students on. One to a K-8 school library and one to a 9-12 school library. The latter is where Joyce comes in. She's the school librarian at Springfield Township High School in Montgomery County, PA.

Last year I heard her mention Twitter for the first time. I recognized it for its instant messaging capability then because she tweeted about our imminent arrival and shared the greetings that subsequently arrived from across the Twitterverse.

Now
This year she asked if I was on Twitter yet. (No.) What tipped the balance in the direction of joining is her comment that she herself does not follow just anyone. She follows people who have something to say. This was interesting. People on Twitter aren't just sharing about what cat food they bought today. Some are sharing about more substantive matters. (Not that tweets about cat food don't matter. Any tweet reveals something significant about the tweeter. I simply wasn't ready to join Twitter to read that type of tweet.)

'Well I have something substantive to say. I'm thinking all the time about a whole boatload of weighty matters.' So I joined Twitter and immediately started following Joyce. I also started a blog because I knew I wouldn't be able to convey everything I wanted to say about a particular piece of i-candy I was enjoying in less than 141 characters. Then I linked Twitter and blog together. And I tweet and blog about matters of substance--to me. I try not to go on about nothing. There is are so many ideas going on in my head about many things, I don't much have to.

So I like Twitter because it does force me to encapsulate a solid idea in a few words. I like Blogger because I can delve into one topic at length. It's 2 great tastes that go great together.

I have had trouble finding people to follow. I've searched academic librarians and instruction librarians, but have found that what they have to say doesn't grab me. (I'm cool. I'll find people eventually.)

I myself have 5 followers on Twitter. None of them Joyce. (Again, I'm cool. I'm just not tweeting her kind of stuff. I am after all an academic librarian.) I have 1 follower on my blog i-candy by wangc. I think she's family (library family, that is).

Perhaps my i-candy is for you. Then join the list. Either one of them.

Works Cited
"Twitter." New York Times. 21 April 2009 <http://topics.nytimes.com/top/news/business/companies/twitter/index.html?scp=1-spot&sq=twitter&st=cse>.

An Older, Less-used Hat

This morning I conducted an online orientation session to our library's resources for a group of 4 clinical instructors in our Physical Therapy department.

Background Info
Our physical therapy program results in a doctor of physical therapy degree. Students go through a hands-on training experience in offices where current professionals are actively seeing patients. This is called a clinical internship. Arcadia University has somewhere in the range of 500 clinical instructors in clinics all over the country. CIs who wish to have access to our library's resources online may request it. The session this morning was the first online orientation to help those CIs become familiar with what we have to offer.

I bring to this position an interest in the health sciences, but I'm a general reference librarian as well, and general reference is what I do for the most part.

Technology Issues
I was using Wimba to conduct the session, an application with which I've had a pinch of experience but not recently. Wimba allows participants to use either a computer headset or a telephone to participate in the session aurally and verbally. It took me 15 minutes of negotiating a computer headset, a telephone handset, and a wicked echo before realizing that all I needed was the telephone. Wimba connects the computer with the telephone through the phone handset. And this was happening AFTER the session started.

I also had 2 people of the 4 unable to follow my computer presentation because I failed to register them. (Fix that quickly.) A 3rd didn't know his password, but obtained a temporary one from the PT staff member helping me to organize the orientation. The first participant got on only because I noticed his voicemail message to me and was able to get him the conference call information before the other issues arose. All this juggling happened because I got into my office 5 minutes before the session was to start. Which itself required me getting the kids to a friend's house 45 minutes early so they could get to the bus stop.

Presentation Issues
Have you ever done a presentation without any visual or aural feedback from your audience? It must be what actors go through when they have to play to the camera. Wimba is like that because everyone is just listening to you. You have to maintain your train of thought, be animated, navigate the website, And sound capable with no audience feedback. Happily, that changed as I proceeded through the session and began inviting participation. I'm not afraid to call on people by name. And with a list of attendees in front of me in Wimba, no one is immune regardless of eye contact or lack.

Instructional Issues
I usually poll students to find out what they already know about using article databases. In the chaos of getting the session running, I never thought to do this with the participating clinical instructors. I learned further in that one of the participants Teaches students how to find clinical evidence. The rest had largely never used article databases.

Another of my practices during library research instruction is to make sure participants know how to limit searches to full-text because that's what so many university students want. If you're looking for one article on abortion, you don't have to be too picky. Limit the search to full-text, find an article, and force your paper to accommodate what the article says.

For anyone trying to do a comprehensive topic search, this isn't good enough because only a fraction of the total number of articles you retrieve in a search may have full-text. For students like these, I tell them not to worry initially how they will obtain the article. Find good information first, then use supplemental strategies to obtain the article.

With these CIs, I was in general searcher mode. I showed them how to limit their search results in PubMed. Them not being on campus to get any articles from journals we might have in print, I received a couple murmurs of approval. My experienced searcher interjected that she discourages her student interns from limiting to full-text because the articles might not be comprehensive enough to help make a clinical decision that will benefit patients.

I wholeheartedly concurred with her and offered mea culpa for presenting with the wrong hat on my head. Then I pointed to the supplemental strategies for obtaining articles.

The session ended up serving the purpose, both of educating the CIs about our resources and reminding me that I'm a little out of touch with the needs of health science researchers. No problem. I'm ready now for my next session Thursday night.

Going to a Lot of Trouble to Knockoff

My parents, repatriated American citizens, came to visit from China bearing gifts.

I received a Burberry pullover shirt of which I was immediately suspicious. China is known for being a haven for knockoff products (LaFranier). A look at the quality of the stitching helped to confirm my suspicion, but the clincher was to come only after a look on the Internet and a comparison of the labels. I like how the B for Burberry ended up as an R (for ripoff?).







(haganah)


What was more interesting to me was how the tag was attached to the shirt. Connecting the tag to the label was a plastic ornament injection-molded to nylon cord loops coming out both ends. The ornament was 1 1/4" long and 3/8" wide. The tag was on one loop and the other loop went through the fold of the label.



I could see that the ornament was not simply clamshell-clipped onto the cord. There were no knots of any sort. So how did the garment worker secure the ornament to the label and tag?

A study of the end of the ornament revealed that only one end of the loop of cord was molded into it. The other end looked to be molded into a very small piece of plastic inserted into the larger ornament.

I guessed that miniature piece to be a clip of some sort. It initially seemed like a lot of trouble to secure tag to label; but if it made the final product more convincing, so much the better. Anyway, the effort would have to be on the mold fabrication side. Once the ornament got molded, slipping the clip into the ornament would be a vast time savings over tying a knot.

I cracked the ornament open and found my suspicion confirmed about the nature of the ornament.



There were several elements I brought to this puzzle. One was curiosity. Another was intuition. And another was experience. (Perhaps you'll identify more.)

Wrapped in the curiosity was observation. I noticed something. I wondered about it.

The intuition about the ornament came partly from a former life as an applied materials research scientist.

The experience came from curiosity about other locking devices like nylon clips on backpacks.

Perhaps the real significance of this event is that those various elements make me a more involved academic librarian.

I wonder.

I intuit.

I draw on experience.

Works Cited
LaFranier, Sharon. "Facing Counterfeiting Crackdown, Beijing Vendors Fight Back." New York Times. 1 March 2009. 19 April 2009 <http://www.nytimes.com/2009/03/02/world/asia/02piracy.html>.

haganah. "Burberry Prorsum." Weblog comment. 2 April 2009. StyleForum. 19 April 2009 <http://www.styleforum.net/showthread.php?t=61518>.

Handling Bad Assignments from Professors

(Twitter is failing me because I get no input box in which to tweet.)

One of our librarians distributed a web article she came across recently about bad library assignments professors make their students do (Collier). The article is from a second-year librarian. She comments about the difficulty of imagining approaching a faculty member to discuss the assignment. "What moxie!" She says.

I'm now a fourth-year librarian and in many ways I've forgotten about the challenge of approaching faculty. I think this is mostly because (I believe) I've both cultivated a strong relationship with my faculty and learned how to be diplomatic with phrasing concerns. It helps that despite being a fourth-year librarian, I've been in the work world for 20 years and have an easily approachable personality (I've been told!).

Last year I noticed the pattern of students from the same course searching for specific articles on genetic modification every year. The big problem was that the obvious keywords of gene modification weren't yielding good results. Couple that with the problem of the article having to be less than 3 years old and no one being permitted to use an article that someone else found.

I nipped the problem in the bud by immediately getting on the phone and asking the instructor for an opportunity to do a 15-minute instruction. What worked is that I knew the instructor and knew I could approach the subject tactfully by offering to come into the class. But even if I hadn't known the instructor, I'd still have made the call. Just another opportunity to connect with someone!

As students we see professors as paragons of intellect and wisdom that we must uphold with high regard and can approach only with temerity and humility. They are people, too, with their own personalities, weaknesses, and insecurities! So much can be accomplished by approaching them with due respect, tact, and empathy, but with candor.

Not to say there aren't profs who are full of themselves. At least at Arcadia University, I don't see much of them. There will be situations in which problems are irresolvable. Nobody wins all the time.

Works Cited
Collier, Ellie. "Stepping on Toes: The Delicate Art of Talking to Faculty about Questionable Assignments." In the Library with the Lead Pipe. 18 March 2009. 17 April 2009 <http://inthelibrarywiththeleadpipe.org/2009/stepping-on-toes-the-delicate-art-of-talking-to-faculty-about-questionable-assignments/>.

Troubleshooting technology

At Arcadia University, reference librarians work with instructional technologists in a unit within the Library Department called Instructional Technology and Library Research Services. The details of why this is and why it's a good idea are for another post. The significance is that besides being the Sciences Librarian, I'm also the student supervisor for instructional technology.

With final presentations fast arriving (it's Week 13 of 14), we're actively managing poster printing. These posters are the big ones you see at professional meetings that students have prepared based on their research.

The lab where the padawans work (read padawan as student apprentices--only the Sith have apprentices) is in the library physically. The large format printer is in Information Technology in a neighboring building. This makes life interesting because we have to monitor the progress of printing remotely. Although you can see from the printer window if a print job has failed, you don't necessarily know exactly why. So far the only causes I've known of are empty ink cartridges or a spent paper roll. I haven't known of more causes because this year is the first that I've done this supervision and, thus, been involved with the printing process.

One phenomenon that I did notice as we monitored printing remotely is that there are other users printing other projects that aren't posters. You can see them interspersed with the presentation poster print jobs we send.

Here's the lesson. It is important to get to know the relevant processes before giving full control to a padawan--or anyone else for that matter. After all, knowledge is power.

I'm sitting next to the printer now because there are no padawans on duty. Normally I'd be in the library but the printer report indicated that there was a failure. I could have called an IT student apprentice (they must be Sith over in IT) to check on the printer status, but I figured I'd just look myself.

What I found was a lab full of design students. My poster print job was failing because the design students were trading out paper rolls from poster paper to drawing vellum. I watched a student change the paper back but still had the poster print job I was handling fail twice more. I looked at the printer and noticed it querying for the user to load the paper even though she already had and had then left for the day. I removed the poster paper and reloaded it. Then I realized that she had never changed the printer's paper setting. She had changed the paper to poster paper, but the setting was still for vellum.

If I had been sitting in the library, I would never have realized that the other print jobs I was seeing in the queue could be contributing to failed print jobs. So now I know of 3 possible reasons why a print job can fail that I can notify the padawans to be aware of.

Rubric, what rubric?

One of the challenges of the Tech for School Library Media Centers I teach has been determining what my rubric should be for grading assignments. Originally (last year, that is), it started as a simple 33%-33%-33%. 33% of the grade would be synopsis of the article selected for the assignment, 33% would be reflection on some aspect of the article, and 33% would be for describing application of some element of the technology featured in the article. That seemed pretty straightforward to me. I just needed to help the students understand what I meant by application: It was to be an explanation of how they would use what they had learned from the article. Since few of the students were practicing school librarians, I told them to imagine how they would apply the technology, recognizing that there was at least value in that exercise.

After the first paper last year, I realized that I wanted more in that rubric. I wanted to see something extra that they were doing to enhance the learning in the assignment. If the article was about a web technology, then that extra effort needed to be consultation of another article or perhaps of a website or even a person. Somehow that effort needed to distinguish the work from one fulfilling the basic requirements of the assignment. So the rubric was now 30/30/30/10 for synopsis, reflection, application, and effort. (Effort would eventually become Value Added to avoid the confusion that arose from people who thought they had put a lot of hard work into their assignments--not the same thing.)

This rubric seemed to serve the assignments well the first year. This year, though, I spent a lot of time getting the students to devote 1/3 of their writing efforts to each part. Students were tending to spend more time on synopsis and less on application. So I kept telling them that if approximately 1/3 of the grade was for each part, then they should be devoting 1/3 of the length of the paper to each of those parts.

As each assignment passed this year, I also began noticing other elements that were important that students needed guidance on. I started grading on the quality of the writing, the adherence to MLA's citation style, good grammar, and good punctuation.

Another element that became more prominent was the length of the papers. Although I had set page limits and font style and size, a fair number of students were ignoring those requirements. One kept generating papers 20% shorter than everyone else and a couple were writing ones up to 50% longer.

About halfway into the course one of my students complained about the rubric being too general. I couldn't understand what she meant at the time, so I decided I wouldn't make any changes. I did start comparing notes with other professors.

What became increasingly clear was that quality writing was not as implicit as I thought--neither was following certain assignment requirements. Suddenly, the need for a more specific rubric became clear. I decided not to rewrite the rubric for this year since all the writing was now done. Any changes I could add to the syllabus for next year.

In my class today, however, a student asked for a detailed rubric for the final project. Not a written paper, but a library and technology website, I admitted I didn't have one. This time I was more ready to put something together. As each of 4 groups of students worked together during our class lab time, I collected notes on what I noticed I was liking and not liking. I immediately began making comments and suggestions. Based on my observations and those about the writing assignments, I began formulating hard numbers. I have yet to assign weights. I'll get the actual percentages in place this week and will have the rubric done in time for everyone to use. In this case, better late than never. And next year's class will be none the wiser.