a feisty embuggerance of metadata!

The thing that really stands out to me in this post (h/t John) about a particularly picturesque problem with Google metadata is the author’s comment about Google Scholar vs. JSTOR.

He knows there’s a lot of problems with Scholar metadata. It’s not actually subtle; the article he found was not actually written by Messrs. Feisty and Embuggerance. But the Scholar interface lets him interact with data in ways he wants to, and JSTOR doesn’t, so he puts up with it. Which has me wondering two things —

1) Incentives and information flow. I’ve read enough Marginal Revolution by now that my first question is — is there really any way for end users to put pressure on JSTOR, or other scholarly databases? Is there any meaningful communication channel there, any way that user behavior (including workarounds and avoidance) even has a chance of exerting pressure to change? I’m guessing not — too many middlemen, interests too diffuse, too many egos and agendas. I don’t like where that leads.

2) Metadata and interface. In the library world I’ve done a lot of reading about, and been in some conversations about, metadata, and it’s often discussed as its own thing, separate. You have all these conventions surrounding how metadata works, and the boundaries of the system are drawn right there. Except — this points out that that’s really not true. Users aren’t using things like Google Scholar because they’re ignorant about metadata quality (the comment thread in that Chronicle article I talked about should show that that’s definitely not true for this population…) But metadata quality is part of user experience, and users are evaluating it in that context, and they’re willing to make tradeoffs on one UI front in favor of another.

This should not be at all revelatory, huh. But it’s a totally different perspective. New mantra: “Metadata is a part of interface.”

Enh, I’m too sick to blog intelligently today. Lately viruses are a part of interface. Send your hopes for a better UI.