If I'm going to turn the scope onto usability testing and meta-information (metadata, information architecture, the "belly of the beast," so to speak), then I need to do a couple of things.
First I must answer, what does usability testing measure.
Second, I must define how metadata functions in the user experience.
Third, I must make a case for why metadata functionality should play a role in the user experience; for instance, if a user is going to search directly for a single item in a website, then why would s/he need to understand the navigability of the site itself?
Does this affect arrangement of finding aids on archival websites? How should arrangement of finding aids be affected, versus should we bother with that?
Finally, I'll need to shape the definition of usability testing to also encompass metadata usability.
Tuesday, May 25, 2010
Friday, May 21, 2010
What does usability test?
Usability, for the purposes of my research interests, measures the functionality of software or a website for people to achieve the purposes for which it was intended and created. Usability tests how graphics and text interact on the image of the page; it tests whether the right words attach to the correct kind of link; it measures how effective specific text is.
Usability testing is not, however, interested in meta-information. I very deliberately choose to call this "meta-information" because I'm approaching the original idea of "meta," and I want to separate "metadata" and all its connotations from this, for right now. Meta-narrative, for instance, is the narrative outside a text that elucidates the text. Metaphysics deals with transcendence from science.
Meta-DATA deals with the outside data, that yes, is descriptive to a website, but that is also representative of a website as a whole; meta-DATA is "beyond" the site; meta-DATA is NOT the site; and in fact, META-data is that which pulls users into a site, though they never actually SEE the means by which they are pulled (metadata).
I've talked to a lot of metadata librarians who keep telling me--whom I wouldn't blame of they get slightly annoyed at my questioning--"Metadata is just a tool." (And I say this fondly because I feel friendship and gratitude for all my metadata librarian friends. I've had such fascinating conversations with them, and their patience is something for which I also have undying gratitude.)
While I agree, metadata is a tool, I also agree that my car is only a tool, a means by which I drove from Lubbock to Austin this past week. As I drove, I stopped and took photographs of windmills between Fluvana and Sweetwater; I pulled off to look at cemeteries when they were marked; after arriving in Austin, I ventured out to Barton Springs one evening and sat on a boulder to watch the rain as it fell in the water.
Let's look at the verbs that the tool, my car, allowed me to use here: "to drive" (in a car), "to stop" (in a car); "to pull off," "to arrive," "to venture." That car is one heck of a tool. Albeit, it is a tool, but it is the tool by which I was able to explore a lot.
I assert that metadata is similarly powerful. Perhaps metadata is only a tool, but I argue that it is the highway by which we access information.* If usability tests structure, functionality, layout, even information architecture of a website, should it not also test usability of the meta-information attached to a website?** Also, while libraries and archives, in digitization, recognize that metadata is important and useful, industry has not started to recognize this--and I do wonder if units of digitization actually do usability testing on the metadata itself. I've heard of libraries running usability tests on their website, but I have only heard of libraries putting together focus groups for search engine ranking improvement--rather than use testing of metadata itself. Even more, metadata is also a set of decisions created by a specific person or persons to limn how the website should be located by/present itself users. It's a powerful and deliberate decision set that brings a person from Chechnya to a website in Texas--perhaps just a tool, but a strong tool nonetheless.
(I had a long talk today with Dr. Still, my dissertation director, and this was what we went over.)
*(Do not mix my car metaphor with the highway metaphor. It's a dangerous thing to get caught in Ana's metaphor land.)
**Writing an article on this right now. Hope to send it out for publication soon.
Usability testing is not, however, interested in meta-information. I very deliberately choose to call this "meta-information" because I'm approaching the original idea of "meta," and I want to separate "metadata" and all its connotations from this, for right now. Meta-narrative, for instance, is the narrative outside a text that elucidates the text. Metaphysics deals with transcendence from science.
Meta-DATA deals with the outside data, that yes, is descriptive to a website, but that is also representative of a website as a whole; meta-DATA is "beyond" the site; meta-DATA is NOT the site; and in fact, META-data is that which pulls users into a site, though they never actually SEE the means by which they are pulled (metadata).
I've talked to a lot of metadata librarians who keep telling me--whom I wouldn't blame of they get slightly annoyed at my questioning--"Metadata is just a tool." (And I say this fondly because I feel friendship and gratitude for all my metadata librarian friends. I've had such fascinating conversations with them, and their patience is something for which I also have undying gratitude.)
While I agree, metadata is a tool, I also agree that my car is only a tool, a means by which I drove from Lubbock to Austin this past week. As I drove, I stopped and took photographs of windmills between Fluvana and Sweetwater; I pulled off to look at cemeteries when they were marked; after arriving in Austin, I ventured out to Barton Springs one evening and sat on a boulder to watch the rain as it fell in the water.
Let's look at the verbs that the tool, my car, allowed me to use here: "to drive" (in a car), "to stop" (in a car); "to pull off," "to arrive," "to venture." That car is one heck of a tool. Albeit, it is a tool, but it is the tool by which I was able to explore a lot.
I assert that metadata is similarly powerful. Perhaps metadata is only a tool, but I argue that it is the highway by which we access information.* If usability tests structure, functionality, layout, even information architecture of a website, should it not also test usability of the meta-information attached to a website?** Also, while libraries and archives, in digitization, recognize that metadata is important and useful, industry has not started to recognize this--and I do wonder if units of digitization actually do usability testing on the metadata itself. I've heard of libraries running usability tests on their website, but I have only heard of libraries putting together focus groups for search engine ranking improvement--rather than use testing of metadata itself. Even more, metadata is also a set of decisions created by a specific person or persons to limn how the website should be located by/present itself users. It's a powerful and deliberate decision set that brings a person from Chechnya to a website in Texas--perhaps just a tool, but a strong tool nonetheless.
(I had a long talk today with Dr. Still, my dissertation director, and this was what we went over.)
*(Do not mix my car metaphor with the highway metaphor. It's a dangerous thing to get caught in Ana's metaphor land.)
**Writing an article on this right now. Hope to send it out for publication soon.
Wednesday, May 19, 2010
What's the difference between an archive and a library?
I have so much to learn. In addition I have so much to learn about archives, libraries, technology, digital project management, digital collection curation, managing people to manage systems, improving efficiency while maintaining standards, creating a name for my institution in preparation for a Web 3.0 environment (which is emerging right in front of our eyes).
Okay, so, in short, I have a lot to learn.
I would like to start an interrogation at one question: What is the difference between archive and library?
There are more than one, so change that verb to "are" and since the subject should agree, make "difference" plural.
1) Library houses copies of data, to be handled, sneezed on, and generally mistreated; archive houses unique materials, to be handled in a controlled environment where sneezing is prevented and mistreatment frowned upon.
Unique materials. Copies of materials.
In learning about managing digital archival projects (special collections), I've been trying to piece together information from archivists, librarians, IT people, technical communicators, and researchers. And I have come up with two things:
A) It is important to make digital avatars of archival materials because this is the only way people might be able to access these materials. (And thus the materials should appear as similar as possible to the original.)
B) It is important to keep people's hands off the original materials. (For very practical, obvious reasons.)
2) In library, what gets scanned is often making a copy of a copy; while this is very important for research availability, the information scanned isn't really something that it is readily apparent must be preserved. In archive, the exact opposite is true--scanning and metadata are tied together, packaged up, and preserved whole, entirely with the goal in mind that this eventually might be the only extant copy of the item.
2B) Then, if library successfully does its job, would no items ever have to go into archive again? (Just a curiosity.)
3) Archive and Library metadata are very different. (Derr...)
4) Sometimes Library and Archive don't communicate or see eye-to-eye with one another in terms of digital practice. Or, sometimes library A will see eye-to-eye with archive B, while archive A and library B say this should not be the case.
What other differences and similarities can we come up with here?
I'm mulling over this one.
Okay, so, in short, I have a lot to learn.
I would like to start an interrogation at one question: What is the difference between archive and library?
There are more than one, so change that verb to "are" and since the subject should agree, make "difference" plural.
1) Library houses copies of data, to be handled, sneezed on, and generally mistreated; archive houses unique materials, to be handled in a controlled environment where sneezing is prevented and mistreatment frowned upon.
Unique materials. Copies of materials.
In learning about managing digital archival projects (special collections), I've been trying to piece together information from archivists, librarians, IT people, technical communicators, and researchers. And I have come up with two things:
A) It is important to make digital avatars of archival materials because this is the only way people might be able to access these materials. (And thus the materials should appear as similar as possible to the original.)
B) It is important to keep people's hands off the original materials. (For very practical, obvious reasons.)
2) In library, what gets scanned is often making a copy of a copy; while this is very important for research availability, the information scanned isn't really something that it is readily apparent must be preserved. In archive, the exact opposite is true--scanning and metadata are tied together, packaged up, and preserved whole, entirely with the goal in mind that this eventually might be the only extant copy of the item.
2B) Then, if library successfully does its job, would no items ever have to go into archive again? (Just a curiosity.)
3) Archive and Library metadata are very different. (Derr...)
4) Sometimes Library and Archive don't communicate or see eye-to-eye with one another in terms of digital practice. Or, sometimes library A will see eye-to-eye with archive B, while archive A and library B say this should not be the case.
What other differences and similarities can we come up with here?
I'm mulling over this one.
Wednesday, May 12, 2010
It takes a lot of people, though maybe it shouldn't be all cooks in the digital kitchen
The more I read about digital project management, the more I learn about how many people it takes to do things the Right Way. The Right Way requires a lot of people who specialize in very specific tasks, things that might be almost too narrow in the view of other professions. The Internet and digital project theory are changing so rapidly that I'm often overwhelmed at how much I have to learn about and attempt to put into practice.
In a way, one might ask the question, "Do you want to be changed, or be a force of change?" Or, Gandhi more applicably, "Be the change you see in the world." (I think.)
In a way, one might ask the question, "Do you want to be changed, or be a force of change?" Or, Gandhi more applicably, "Be the change you see in the world." (I think.)
Thursday, May 6, 2010
Web 3.0, Facebook, Privacy, Identity Control
URL: http://www.huffingtonpost.com/2010/04/29/zuckerberg-privacy-stance_n_556679.html
As this article points out, don't post anything on Facebook that you wouldn't mind the whole world reading.
In fact, I always consider the issue as, don't write anything on the Internet that would make you upset to have publicly distributed to the people most concerned with the topic you've written about. (What does this mean?)
This has a lot to do with identity control--online PR, so to speak.
While yes, we all write things in anger to our nearest and dearest, I always try to remind myself that unless it's an argument that I can rationally and logically support, I probably shouldn't put it online, whether in an email, or Facebook, or a blog. Because, really, there is no surety of privacy on the Internet, and this is only going to get worse. Although I'm a huge proponent of common sense, I recognize that a lot of things get put onto the Internet that violate common sense. Instead, I deviate farther from common sense and closer to pragmatism. If I said to my dearest friend in the world something that I would probably not have said to my boss, it should be something that is at least clear-sighted, about which I could say, "Well, this is true." (Now, I should also say, I think very highly of my boss, and I'm not just saying that because she sometimes reads my blog.)
Two things people need to stop conflating are security and privacy. Take your house, for example--just because you have deadbolts bolted and doorknobs locked, there is nothing to stop the peeping Tom (or Tina) across the street from watching you through an un-curtained window as you change clothes; similarly, you can have plenty of security to protect credit card payments to your electric company, but you're not about to stop anyone from knowing that you've gone to Sprocket's Electric website to pay your electricity bill.
As I told my friend Catherine (friend for 4.3 billion years) in an email--Facebook is actually behind on their privacy settings. I have repeatedly been surprised by how hesitant they are to get their feet wet. I'm not saying I like this lack of privacy; simply, there isn't a whole lot that anyone can do about it, and Facebook was a slightly later sell-out than I would have guessed.
For instance, take the Skittles-Twitter experiment. (Where Wrigley Candy Co. tracked everyone's tweets, and any tweet in which the word "Skittle" had been used was posted onto the Skittles website.) It's not like these abilities don't exist; it's simply a question of, who is going to take the initial heat/hate for doing it first--because, realistically speaking, the people who take the hate/heat (yup, deliberate there) are going to wind up being more advanced.
And yes, I love Google--I'd have loved Palpatine, too, yes--and guess what...they've been doing an awful lot already that you don't know about. So, look at the Facebook implications and be grateful that they're being (more) upfront about it. Web 3.0 is here, and it's not going away. Capitalism is driving it. And I think, eventually, we're going to see more corporate involvement in the writing of laws to accommodate for the digital environment.
Question is: Is the digital environment as real as the "real world?"
Answer: Hard to say. For instance, in grad school we used to have a professor who said that indeed, the digital environment -was- just as real, and he taught his classes over a webcam--which, for the early 2000s, was a very innovative idea. But we'd always threaten to wire the laptop on which he taught into the bathroom, just so we could roll him around on the laptop cart and hear him say, "Where are you taking me?"
Ah, pragmatism. I love you.
As this article points out, don't post anything on Facebook that you wouldn't mind the whole world reading.
In fact, I always consider the issue as, don't write anything on the Internet that would make you upset to have publicly distributed to the people most concerned with the topic you've written about. (What does this mean?)
This has a lot to do with identity control--online PR, so to speak.
While yes, we all write things in anger to our nearest and dearest, I always try to remind myself that unless it's an argument that I can rationally and logically support, I probably shouldn't put it online, whether in an email, or Facebook, or a blog. Because, really, there is no surety of privacy on the Internet, and this is only going to get worse. Although I'm a huge proponent of common sense, I recognize that a lot of things get put onto the Internet that violate common sense. Instead, I deviate farther from common sense and closer to pragmatism. If I said to my dearest friend in the world something that I would probably not have said to my boss, it should be something that is at least clear-sighted, about which I could say, "Well, this is true." (Now, I should also say, I think very highly of my boss, and I'm not just saying that because she sometimes reads my blog.)
Two things people need to stop conflating are security and privacy. Take your house, for example--just because you have deadbolts bolted and doorknobs locked, there is nothing to stop the peeping Tom (or Tina) across the street from watching you through an un-curtained window as you change clothes; similarly, you can have plenty of security to protect credit card payments to your electric company, but you're not about to stop anyone from knowing that you've gone to Sprocket's Electric website to pay your electricity bill.
As I told my friend Catherine (friend for 4.3 billion years) in an email--Facebook is actually behind on their privacy settings. I have repeatedly been surprised by how hesitant they are to get their feet wet. I'm not saying I like this lack of privacy; simply, there isn't a whole lot that anyone can do about it, and Facebook was a slightly later sell-out than I would have guessed.
For instance, take the Skittles-Twitter experiment. (Where Wrigley Candy Co. tracked everyone's tweets, and any tweet in which the word "Skittle" had been used was posted onto the Skittles website.) It's not like these abilities don't exist; it's simply a question of, who is going to take the initial heat/hate for doing it first--because, realistically speaking, the people who take the hate/heat (yup, deliberate there) are going to wind up being more advanced.
And yes, I love Google--I'd have loved Palpatine, too, yes--and guess what...they've been doing an awful lot already that you don't know about. So, look at the Facebook implications and be grateful that they're being (more) upfront about it. Web 3.0 is here, and it's not going away. Capitalism is driving it. And I think, eventually, we're going to see more corporate involvement in the writing of laws to accommodate for the digital environment.
Question is: Is the digital environment as real as the "real world?"
Answer: Hard to say. For instance, in grad school we used to have a professor who said that indeed, the digital environment -was- just as real, and he taught his classes over a webcam--which, for the early 2000s, was a very innovative idea. But we'd always threaten to wire the laptop on which he taught into the bathroom, just so we could roll him around on the laptop cart and hear him say, "Where are you taking me?"
Ah, pragmatism. I love you.
Subscribe to:
Posts (Atom)
