Friday, October 31, 2008

My Grad School Life

I feel like I'm neglecting this blog--SNL videos and class assignments aside--but there hasn't been much to say: I've been sick for about a month (bronchitis and a never-ending cold), which has left me completely drained and not really feeling up to the time, energy, and brainpower requirements of my classes. I kind of just want to take a weekend to sleep and eat soup and drink hot tea, you know? But being behind on most of my projects (by my own estimation, not in any official capacity) leaves me no time for that kind of nonsense.

But, you know, such is the life of a grad student. It was the same in engineering grad school, only I didn't enjoy the reading. (I really do enjoy what I get a chance to read. I wish my professors had been a little more realistic in assigning books for the semester--seriously, there were students complaining about 100 pages a week per class, in some online forum, and I kind of wanted to smack them--but if I get around to finishing the books I've merely skimmed [or less], I will be a better librarian for the effort. They are really fantastic.)

One interesting point: I learned that specializations other than Archives actually do matter at Pitt. I couldn't register for the Academic Libraries class without being in the Academic Libraries track, which vexed me, the self-declared generalist, mightily. But it looks like it will not be a big deal to jump into the specialization--the paperwork was easy, anyway! Financially, I might have lucked into something: the only Academic Libraries "course" I had planned not to take was the field placement (3 credits, 150 hours working with a local library under the supervision of someone who has their MLIS--and, as far as I can tell, I can't get the 3 credits for my internship, because it is a separate program that pays a portion of my tuition per semester), which I could sign up for in the spring and finish in the summer. Since summer is pay-per-credit, having five classes in the spring and three in the summer would save me a few thousand dollars--SCORE!

As an added bonus, I found someone at CMU who may be willing to take on an intern. (I found him by asking "Do you need an intern?" out of nowhere, when he told me what he's working on. It was opportunistic, if not downright rude, but it may have worked out OK.) The project I'd be working on would be kind of ideal, in that it would fill in a gap in my goals and interests that my [awesome] Engineering & Science Library internship doesn't quite fill. It's some digital stuff; I'll explain more if this whole thing pans out--which looks promising, but maybe I shouldn't count my chickens prematurely.

So, there's good, and there's bad, and, as always, there's up-in-the-air. I'm excited about the stuff I get to do and worried about the group projects that need to get done and grumpy about the class on Halloween night (I'm not even joking, 5:30-8:30pm, the first Halloween in years I've lived where trick-or-treaters might show up, I'm going to be in a classroom) and tired from not being able to breathe for a month.

Also, I have a midterm on Monday. I'm stressing about it, mostly because that's just how I am. I hate midterms. Knowing what I do now about the structure of library school, I will immediately drop any other midterm-containing elective as soon as the syllabus finds its way to my hot little hands. (Unless it's the Intellectual Property class; not even a midterm could keep me from taking that!)

Labels: , , , , , ,

Thursday, October 23, 2008

[2670] Muddiest Point

I have no muddiest point.

Is anybody dying to meet up and discuss digital library-y goodness, the day before our midterm?

Labels:

Sunday, October 19, 2008

I like it. (That's the real one, not Tina Fey.)

Labels:

Thursday, October 16, 2008

Coral waxes philosophical on Week 8 Readings for 2670 (and Muddiest Point)

I loved the following quote (from our Week 8 Readings):

Google has taught us, quite powerfully, that the user just wants a search box. Arguments as to whether or not this is "best" for the user are moot—it doesn't matter if it's best if nobody uses it. Moreover, as both Google and Amazon have demonstrated, users have a funny way of determining for themselves what is best for them. --Todd Miller

Right on! I mean, I love highbrow, ivory tower discussion as much as the next girl, but what it really needs to come down to is, "How can we engage the user? What will they use?" And, not to get too far off topic, but this is an issue that's really been on my mind a lot lately. You see, before I started seriously considering librarianship as a profession--and admitting this out here in the open is a little weird for me--I didn't go to the public library. At all. (There's this whole thing about how the library in my hometown was my favorite place in the world until I turned 12 or 13, and then suddenly I realized the librarians were looking at me with ... some negative emotion I didn't bother defining, at the time. Having worked in a public library, myself, and having thought about it a bit, I realize it was probably dread. Teenagers are scary, because they're hard to relate to. We remember being teenagers, but we also remember what we thought of adults. You know what I mean?) I dearly loved the library at my university, but I retained my fear of librarians. How sad! I had absorbed that common misperception of librarians as cranky, bespectacled old ladies with book carts and stern expressions, and it didn't occur to me to ask them questions--even the obviously not old, not bespectacled, sometimes not even female librarians at UVA. Then I went to graduate school, where the Engineering & Science Library (where I work now!) was good as a silent study space, between classes, on days when I could deal with the oppressiveness of it all--something the students who wanted silence exuded, not something inherent to the library itself. (That part of it is still a problem for me. I hate walking past the study carrels. Though as time goes on, I become more sure of myself, and I imagine to myself that they realize I have work to do, to keep the library running.) I didn't know the librarians were super friendly and wanted to answer my questions! I wouldn't have dreamed of bothering them! I did all my searches online, in a combination of Google Scholar and IEEE Explore (which, admittedly, did pretty much encompass my research).

This is all a very long-winded lead-up to the question: how do we deal with potential patrons like I was? I was too shy to ask for help. Frankly, I was too shy to venture into the library, except to study. I was intimidated by the catalog and by the shelves upon shelves of books. ... I guess therein lies a lot of the benefit of digital libraries; if shy patrons can find us online, at least they'll have access to some of our resources. But I'd like to address the bigger question, as it relates to brick-and-mortar libraries, at some point in the future. I'll keep thinking on it. Your comments are welcome!

Now to the much more relevant idea of federated search. I am interested in this. I was considering applying to PhD programs and trying to get funding to build a search utility that would go through a library's catalog and all of its databases, because <rant>the current way we do things is so backward and involved and frustrating. Why, after 8 weeks of doing reference for at least a few hours a week, am I still feeling less than confident in my ability to find absolutely everything in our system? That's absurd. There's no excuse for it. Sure, if you know the name of the journal you want to search, I can help you. And I have a passing familiarity with a growing subset of our journal offerings--and the databases that house them--so that I can find certain types of articles pretty well. But why should I have to know what every journal/database contains, in order to help a patron find the answer to a question I understand? [I get why I have to understand their questions.] Why can't I just type something in a search box?</rant> (I realize I'm proposing something that might end up putting some of us out of jobs, if ever implemented well. I think this is a noble goal, really. We're smart people; we'll find something to do. What's important is that information can be retrieved--ideally by everyone--right?)

It seems to me this is what federated search is out to solve (slowly, and with great limitations). I'm a little embarrassed that I thought nobody else had tried to solve this problem, admittedly, but I guess such is the dilemma of a grad student. Better that I'm thinking of solutions, even if they're already implemented (in some form or another) than that I ... don't? Eh.

There are still, clearly, significant hurdles to be overcome in all of this.

The D-Lib article was published in 2004; I wonder what academic libraries have done, since then, to respond to this problem--for those who don't feel like clicking, the problem is a lack of acknowledgment, on the part of academic libraries, of the tremendous amount of academic resources on the Web. My guess: not much. (I love academia, but I acknowledge its imperfections, slowness being a major one.)

Muddiest Point: Does the Greenstone installation on the lab computers do anything besides show us the demo library? Can we build libraries and burn them to CD at the lab? (This is of great importance, since Greenstone isn't installing properly on Dreamhost, and I have a Mac. Also, an unwillingness to install Apache on my Mac.)

Labels: , , , ,

Friday, October 10, 2008

[2670] Week ... 7, actually

Muddiest Point: My muddiest point from last week didn't get answered. Since it directly impacts the homework that's due on Monday, I'd be really grateful if somebody could help me out: I'm not sure I understand what an attribute is in XML. We saw a schema and how to set an attribute up in it, but not how it would look in the XML that fit the schema. (Apologies for imprecise terminology.)

Reading Response: I hadn't thought all that hard about how beefy a web crawler would have to be, given the volume of information the Big Three search engines index. Those are some mighty big numbers. And, you know, now that I'm thinking about it, of course they could shut down an entire domain if they did not have politeness algorithms in place. That they could shut down an entire country, I am still wrapping my head around. (To be fair, I still picture them as little spiders that "grab" links and report back information to big servers.)

I didn't see any mention of ill-mannered search engines, who ignore robots.txt files; I'm curious how search engines other than Google, Yahoo!, and Microsoft work. Probably similarly, but with lower ethical standards (due to less public attention ... or the need to get more of it?).

It seems as though there's quite a lot of research going on in the digital information retrieval area, particularly in multimedia. I wish I were a better programmer; it sounds really interesting.

Really, I just wish everyone would just use metadata and be honest about it.

In support of Honest Metadata, I present to you Eleanor Rubidium Chinchillington (who just goes by "Ella"):

Labels:

Further Musings

I feel like I was unnecessarily harsh in my post yesterday. Looking at it, there's nothing I consider untrue or really feel a need to change, but the whole thing kind of leaves a bad taste in my mouth.

I think what bothers me is that I came off sounding as though I'm unhappy, and, on the whole, I'm really not. Yes, I think there are some serious problems with Pitt's program--problems that may lead to a drop in our rank, honestly--but, you know, I'm still there, and I plan to finish my degree. I'm looking forward to next semester's classes, which I've mostly chosen, even though the official schedule isn't up yet. (An unofficial schedule is available to anyone who bothers Googling for it.) The student groups--something I haven't discussed, thus far, but ought to--are great; SLAPSG is a little late getting off the ground, but there's a lot of interest on the part of the student body, and I know the [super active and awesome] local chapter will help us out. SCALA is fabulous: we're planning on putting together a Book Kart Drill Team (it's spelled with a "K," yes) for ALA Annual 2009--I'm heading that up, because I'm involved in ALA already and because I'm Treasurer--a Technology Petting Zoo for students who want to learn about and play with various kinds of technology, and a t-shirt sale. And there's a new student group, centered around community outreach, called SISCO (which bothers me every time I hear it, because I think about network hardware, but there you go). These are excellent and all make me very happy.

As for my internship at CMU's Engineering and Science Library, I am really enjoying it and learning a lot. Every time I get really confident about my reference skills, someone comes along with a hard chemistry or math question (why is it never electrical engineering? or even computer science?), which reminds me what a beginner I really am. But that's really not a bad thing; it just means I am constantly learning. I'm signed up to help give a talk on RSS and Google Reader, in the near future, which I find pretty exciting (and terrifying), and I will be helping at least one of my coworkers redesign her portion of the library web site. I am super excited about these projects. Slightly less exciting--but certainly useful to the library and still a learning opportunity--is a set of ongoing projects, going through a large collection of materials science books donated by a retiring professor and a smaller, but much older, collection of books that belonged to Roberts' (of Roberts Hall) mentor. A large portion of my time goes, of course, to "other projects as assigned"; earlier this week, I went through some tech reports, to determine whether or not each one was redundant or new to the collection, and last week I picked up some journals from a professor. That kind of thing. I'm hoping for some collection development (spendin' money!) and more instruction experience, before too long.

So, you know, things are actually pretty good.

On a more personal note, I've finally gotten together the bravery and momentum to go out and volunteer for a cause that I think is important (in all that free time I don't have). That makes me feel pretty good about myself, even if it means I go to bed earlier than I otherwise might on some Friday nights.

And, as I predicted, my schedule is changing: I'll be working Saturday afternoons, starting in a few weeks, because the other Information Assistant, who used to do the Saturday shift, got a job. (Yay for enjobination!) I'll have to drop an hour, somewhere in the week (personally, I'm hoping to start at 11am instead of 10am on either Tuesday or Friday morning ;)), to stay on the right side of CMU's rules, but it will be a good experience; back-up is a phone call away, instead of a short walk away, on weekends. Self reliance and all that!

Also, I have a purple iPod Nano. I love it. It holds all of my music, a bunch of podcasts, and a couple of TV shows. I've already used it to listen to supplemental class material that I otherwise wouldn't. (Because I have very little self control when faced with a computer monitor, I have a very limited amount of time I can spend paying attention/not reading random stuff on the Internet, if I'm at my computer--limited by how many photos I have to sort, actually--and the Panopto-only lectures are going to soak that up; no time for the supplemental material on top of it! But with an iPod, I can listen while I wait for the bus, while I walk out to get tasty Indian food for lunch, etc.) It will make the 5 hour trip to Detroit and back, in early November, into usable time, which will decrease my guilt at going (instead of doing homework). This is a win.

Labels: , , , , , , , ,

Thursday, October 9, 2008

Long Delayed Musings

I've been meaning to post a "State of the Schooling" kind of thing for quite a while, as the six week mark of the semester neared and then swooped past--it's funny how "six weeks" still has meaning to me, nearly ten years removed from high school as I am. Having a report card might not be such a bad thing; there are several post-graduation job openings with deadlines in the next few weeks. What, precisely, should I show them, in lieu of a degree, or even a transcript? (A cover letter and curriculum vitae, I suppose. Speaking of, if anyone would like to do a CV review for me or give me some academic library-specific tips for cover letters, I would be most grateful. I still don't feel like I know what goes in either.)

It isn't that I don't have work to do tonight, by the way; I had reserved today to work on a grant proposal for my Management class, but I was tackled to the ground by a cold. I'd like that to be more metaphorical than it is, but I think I've spent 18 of the last 24 hours asleep on an air mattress, where I collapsed last night and again this afternoon. My head is achy and stuffy, and I'm just kind of vaguely miserable and totally wiped out. Fortunately, though I don't have the wherewithal to work, I have it to blog. And blog I will!

There are some really fantastic things going on, schooling-wise, and some really not fantastic ones. Let's start with the good before we move on to complaining, shall we?

I love my Organizing Information class. It's one of the five "core" courses people in the general, academic, or digital track are required to take before graduating, and the professor who teaches it is just so great. She obviously cares very much about the subject, but she doesn't take it so seriously as to take the fun out of it. Actually, it isn't even just that she cares about the subject: she cares that we understand it. After every assignment she asks us if we learned from it and thought it was worthwhile, and she seems to really listen to our feedback. I think I will take the Cataloguing class next semester because her class has been so good; honestly, I'm really thinking about going into metadata librarianship (of the "data wrangling" variety, as Mike Bolam put it in his guest lecture, not the really hardcore cataloguing). ... Which sounds so flakey, as I re-read it. But it isn't just that I like the professor; I really find the subject interesting. I liked English classes because I liked grammar. The structure--diagramming sentences--really pleased me. I think engineering and computer programming--and sorting through data with Matlab (which, inexplicably, I miss very much)--appealed to me for the same kind of reason. There's just something very comforting about hierarchies and trees and structure. (Not that I apply any organizational acumen to my own life, but I imagine that's part of what appeals to me about studying the subject.)

My Digital Libraries class is also pretty good; I'm frustrated with trying to use the poorly-documented digital library software (I admit, Dreamhost's CGI support page is above my level), and I'm kind of nervous about the midterm, but there's a lot of good content in the class. Some of the topics are a review, but even that isn't a bad thing. I wish I had time to sit down with Lesk's book (Understanding Digital Libraries), to just read it cover-to-cover. Honestly, I'd settle for the time to really do the assigned readings in depth, rather than skimming through them in a hurry. (I'll get to that in a minute; honestly, the time requirement for this class is very reasonable, and I'm selling it shorter, in the time I give to it, than I would like.) But our professor encourages us to ask questions, lets us use blogs (instead of horrible, horrid, nasty Blackboard) to communicate with one another (as you know), and is just generally very understanding and accommodating. It's a good class.

My Management class ... isn't bad. I mean, I've never liked fuzzy business speak. It brings my hackles up and evokes a feeling of distrust in me (yes, even after a couple of years of consulting in the DC area... especially after that, actually). The assignments are kind of poorly defined, which I found frustrating until I started seeing the grades (both mine and the averages); I think perhaps the expectations for the assignments are also poorly defined, so the grading is fairly lenient. On the up side, two of the three group projects we're doing for the class are really relevant and useful to us in a real-world way; we will be writing a "management portfolio"--with a needs assessment, mission statement, vision statement, staffing plan, budget, and business plan--and a grant proposal (which the professor keeps referring to as though it is part of the other assignment, but very few of us joined up with partners who are in our management portfolio groups; also, most of the class seems to have gone out and found real-world grants to write up, whereas our management portfolios are all fictional). The irrelevant project is a slide show put together with a group of 5-6 people, to share with our "virtual groups" of 15 people chosen randomly from the in-person and online students. We're supposed to discuss these slides in the group discussion boards, but nobody cares; most of my group logged in, made a token comment, and never checked back again, the week my slideshow went up. (My feelings weren't hurt.)

The big downside of the Management class, other than the vague hand wavyness of it (that's a management class for you) and the fact that most of it is repetition from my two-day Project Management class at BAH, is the fact that the management portfolio and grant proposal are to be done in groups of five and two, respectively, on very different topics (which, again, the professor doesn't seem to realize?), and turned in on the same day. The five-person group is deliberately chosen so that on-campus and online students are grouped together--one physical meeting will happen, less than a month before the project is due, for no more than an hour, and everything else is to be done online. I know the professor thinks this is a beneficial look into real-world working conditions, but I've done real-world distance collaboration, and there's usually a little more in-person, or at least teleconferenced, interaction. So that's frustrating. But group work in school is always frustrating; I've gone through worse.

Aaaand... I saved the class I like the least for last. (Say that five times fast.) It's required of every single person who enters the program, regardless of their "specialization." This semester, as an "experiment," they have something like 250 people in the class, half of them online. There are roughly ten professors running it, and as nearly as I can tell, each one was allowed to pick a book or two that they'd like us to read. They didn't, you know, whittle it down after that discussion, either, or choose a set of topics to really focus on: we are expected to read 15 books, on various subjects, clumped together in a sometimes arbitrary fashion. We are asked to write 400 word essays about these sometimes arbitrary clumps of books, citing outside reviews, roughly every other week, and to post them in our randomly-chosen "group"'s discussion board. This week, we wrote about two books; next week (actually next week, not two weeks hence), we write about four. Roughly zero percent of the class [I've asked something like thirty people] reads every book, or even half the books, before "winging it," as I say, and it kind of shows in reading their essays... (Sorry, my group! I am sure you're very smart people, and I'm sure my essays also leave something to be desired.) Anyway, on the off weeks, we're given big lists of articles and asked giant questions ("How has the WWW influenced the way in which ideas, information, and knowledge are exchanged? .. blah blah, Semantic Web"), which we are to answer in 250 word essays. Every Thursday, we turn in the "big" essay, and every Monday, we are expected to write a response agreeing with one of our colleagues' points and disagreeing with another. And then there are various other discussions we're supposed to participate in, on Blackboard, as well. I think they also expect us to go to lecture, though I'm not sure how many people still do that. (Which is a shame. I actually really like the one professor's lectures, but because of the class size, they had to move it to the far side of Oakland, near nothing else that interests me and up a smoker-filled hill from the closest bus stop. I'm not kidding; half the nurses at UPMC seem to smoke, and they all do it between the bus stop and class. The two times I went, I was miserable with asthma for half of the two-hour lecture. So, I decided to watch them online. But the online software is buggy, so the times I've tried, it's often frozen on me part-way through. So I'm sporadic in watching it, now.) This kind of workload isn't really conducive to, you know, having multiple classes and a job, and I find their lack of selectivity and realism--and particularly their lack of flexibility in the face of students' complaints--deeply frustrating.

My big complaint about the program overall is that it feels very undergraduate. No kidding: we have to have our advisors' signatures on our class signup forms--1) we have forms, rather than doing it online, and 2) I didn't have to have an advisor's signature even as an undergrad, that I remember. (I think I had to certify that I'd met with him, but he didn't sign anything.) There are no research assistantships available--internships, most of them outside of Pitt, yes, but those are only allowed to provide up to half our tuition--and we are stuck into a 250-person lecture, then graded on our participation in discussion boards. I realize the program lets in pretty much everyone who applies, so they have to do a certain amount of hand-holding, but couldn't there be, I don't know, an "advanced class," for people who've worked in the real world and don't need to be condescended to?

My second biggest complaint is that the focus--at least this semester, in the particular classes that are taking up the bulk of my time--seems to be on technology, rather than on library skills. Now, it isn't that I don't care what effect Google is having on libraries, or what we should expect the future of the printed word to be, but those things will be different in five years. Also, you know, I already understand technology fairly well. I think it's fantastic that my colleagues with less technical backgrounds are getting this kind of exposure--we need more technical knowledge in the field!--but it is really frustrating to me: I learn technology in my free time; I want to learn about libraries while I'm at school.

My third complaint is about Blackboard. I'll tag this post with the "Blackboard" tag so you can click it and go read all about that, if you care to. Part of that, which I did not cover in the previous post, has to do with changing our in-person classes around and making the bulk of our class discussion happen, as they like to say, virtually. This bothers me. I just don't see the same candor, or quality, in the discussions we have on Blackboard, possibly in part because the professors are watching and grading us on our comments; people are hesitant to criticize or make mistakes. I really think the quality of online classes is lower than the quality of on-campus classes because of it.

Next up: how's the internship going? (Far less complaining in that post. Spoiler: I am enjoying it and learning a lot.)

Labels: , , , , , ,

Monday, October 6, 2008

[2670] Interesting article

LibraryJournal covers some of the controversy around Google Books:

http://www.libraryjournal.com/article/CA6601209.html?nid=3285

Labels: , ,

Saturday, October 4, 2008

[2670] Week 5 Reading Responses & Muddiest Point

Muddy point: I'm not sure I understand what an attribute is in XML. We saw a schema and how to set an attribute up in it, but not how it would look in the XML that fit the schema. (Apologies for imprecise terminology.)

Reading response (digital preservation - list below):

I don't know a lot about physical archiving, but it seems surprising to me that archivers didn't figure out immediately, when beginning digital projects, that of course the rules would be different, and different strategies would have to be employed. (Hindsight is 20/20, yes.)

I keep thinking that the problem of digital preservation shouldn't be so hard. We still have tape drives, after all--which are not so good for on-the-fly access, but do very well at storing large amounts of data for a long time. Why should 160GB hard drives, perhaps arranged RAID-style, not work out for a similarly large amount of time? Do we predict that we will move away from hard drives so soon? (We might! But it isn't as though we'd magically lose the ability to access them right away.) When you migrate to a new technology, migrate your archives, too; it seems logical. I don't think the cost of memory is going to skyrocket, any time soon. I wonder if maybe some kind of networked storage service is going to be the way to go--one institution does all the work for a bunch of others? (I'm thinking of a colloquium of universities more than a corporation, here.)


http://www.sis.pitt.edu/~dlwkshop/paper_hedstrom.pdf
http://www.dpconline.org/docs/lavoie_OAIS.pdf
http://www.dpconline.org/graphics/handbook/index.html
http://www.dlib.org/dlib/july07/littman/07littman.html

Labels:

Thursday, October 2, 2008

Hopefully H.G. Wells and Vannevar Bush had more insight than I do

I confess: I do not believe in a Semantic Web. I sincerely hope to be proven wrong--we should all hope to have information resources that powerful--but I do not believe, given my understanding of the way the Web works, the way search engines work, and computers' consistently poor understanding of natural language, that we should expect anything like Berners-Lee, Hendler, and Lassila's (2001) almost utopian ideas of information retrieval systems within our lifetimes. I also have serious doubts about Uniform Resource Identifiers (URIs) or Digital Object Identifiers (DOIs) ever being implemented consistently, correctly, and for large enough portions of the Web to make a real difference; again, I want to be proven wrong.

Brooks seems, almost, to agree: he discusses the untrustworthiness of user-supplied metadata and search engines' habit of ignoring, or at least devaluing, it. In the past, indexing was done by trustworthy experts, who "possess[ed] a special skill for denoting the meaning of text," and if they failed, they could be found and held accountable. Indexing now is done by various algorithms looking at the content of and links between web pages--and it is imperfect (2004). For the Semantic Web, as Berners-Lee et al. (2001) envisioned it, indexing would be done by the content creators, whom Google correctly distrusts, or perhaps by users of the content, via social tagging/bookmarking. This last approach has shown real promise (Wu), though I have a theory--unexplored in any papers I could find--that the Matthew Effect would apply, and most content would remain untagged by anyone except its creator.

Despite my skepticism, I find the topic fascinating and would love to design technology to mitigate some of these hurdles.


Berners-Lee, T., Hendler, J., and Lassila, O. (2001, May 17). "The semantic Web: A new form of Web content that is meaningful to computers will unleash a revolution of new possibilities," The Scientific American, 284(5), 34+ [Available here]

Brooks, T.A. (2004). "The nature of meaning in the Age of Google," Information Research, 9(3) paper 180. [Available here]

Wu, X., Zhang, L., Yu, Y. "Exploring social annotations for the semantic web," Proceedings of the 15th international conference on World Wide Web, May 23-26, 2006, Edinburgh, Scotland

Labels: ,