Epistemographer

Among the most nerve-wracking implications of recent life changes was the need for us to figure out what to do with our condo. Thankfully, after an attempt at a word-of-mouth FSBO and then a formal listing with a realtor, we were offered a contract over the weekend. While the offer wasn’t everything we wanted, we find solace in the fact that we bought at the height of the market and are selling less than two years later at a price that lets us at least limp away with all limbs intact. The movers come on Friday, and by the end of the weekend we’ll be happily getting our bearings in a new apartment in Brooklyn.

For those of you who’ve seen me through the past two years of home ownership, it’ll come as little surprise that I spent our last Sunday afternoon in DC spread out on our patch of outdoor space, toolbox open and tools scattered about, sawing and hammering away. The particular project at hand was the making of window screens (a requirement of our buyer), and so I managed to pick up one last bit of DIY knowledge, adding to what in hindsight is a pretty substantial list. Two years ago, I didn’t know how to:

• Hang sheetrock
• Pull up carpet
• Lay hardwood plank flooring
• Refinish stair treads
• Put up glass tile
• Caulk a bathtub
• Mud a drywall corner
• Move an electrical socket
• Install butcher block
• Replace a kitchen garbage disposal
• Build a built-in bookcase
• Sink cabinets into a wall
• Install built-in wardrobes
• Replace a bathroom ceiling fan
• Grow a tomato plant
• Build a wall

It’s been a good run…how we’re going to go back the world of renting (where even painting a wall might require a landlord’s permission) is beyond me…

File under ironic…

Several pieces of news that I’ve been sitting on for a few weeks, but might as well announce publicly before I head to SXSWi on Monday (heading down late ’cause my sister chose this weekend to get married, one of the handful of events worth missing “Geek Spring Break” for):

1) In mid-April, I’ll be leaving the Center for History and New Media to take a newly-created job as the Director of Digital Strategy and Scholarship at the New York Public Library. While I’m incredibly sad to be leaving the amazing team at CHNM, this is a ridiculously amazing opportunity, and I’m looking forward to continued work on the intersection of scholarship, education and information technology.

2) My first book, From Betamax to Blockbuster, has been officially launched by the MIT Press and should drop in early 2008 (was hoping for sooner, but they’re pitching it as a trade press and we missed the window for an early Fall 2007 release.

3) Jenny and I will be moving up to NYC sometime in late April / early May (I’ll be commuting back and forth for my first few weeks at NYPL). Right now, we’re looking to sell our place in DC; if interested, (or you know of anyone who might be) please do get in touch. And if you know of any good 2.5-3BR apts opening up in the general Park Slope area, we’re looking for a rental.

4) Yeah, I said we’re ideally looking for a 3BR apt. We’ll need the extra room(s), ’cause come September-ish, there’ll be three of us. More on that to come…

(for those of you who aren’t in the academic tech community, this is going to seem a bit inside-baseball…feel free to move right along)

Over the weekend, Bruce D’Arcus wrote a blog post about Zotero in which he said that “one gets the sense of a project at the portals of the cathedral gazing out at the bazaar, but not yet ready to step out the door.” This has sparked a bunch of discussion among us Zoterons over the past few days, and I wanted to distill a bit of it here.

From my particular perspective within the Zotero project, it’s less that we’re not ready to step out the door than the simple fact that we’ve been so focused on short-term goals that bigger conversations like the ones Bruce wants to open up have fallen by the wayside. Yes, we’ve been less than responsive to Bruce’s requests, but not out of any deep or unconscious desire to stay within the cathedral. In fact, I’d argue that the cathedral/bazaar dichotomy, while useful for highlighting different modes of work, is also rather reductionist, and can distill the gray areas of actual practice into black and white strawmen.

There are a number of models for open source projects; the one we’ve been trying to follow at Zotero is one of open participation, driven by participants themselves. At this point, if you want to participate, you can get full read access to our bug tracking and versioning system, and write access once you’ve proven yourself. While the dev list has been low-traffic (I wouldn’t go so far as to call it “dead”), the forums are extremely active, and we’re proud of a level of responsiveness by the whole team there that far surpasses expectations for an open source project. There are mechanisms for discussion, and we are deeply committed to F/OSS principles (along those lines, we’re going a step further and opening up our bug tracking system to full anonymous read access; Dan Stillman posted the details on the dev list yesterday). When we introduce something new, we see it as the beginning of a conversation, not the end of one: the Word plugin, for example, is a first draft, and we’d *love* to see someone elaborate on it. As for OpenOffice functionality, we haven’t had time yet to really start that conversation (either with words or code), but we’d love to see someone else do so (and in fact might be able to compensate them for their time).

On the Word plugin: it seems to have come out of nowhere mainly because it did come out of nowhere. One of our developers, who’s currently in college, needed to write a paper and came back with a working Word plugin. This wasn’t a top-down directive so much as him saying “Hey, this’d be cool,” and pulling it out of thin air (he’s actually got quite a reputation around CHNM for suddenly producing incredibly cool bits of code). As for the OpenOffice functionality, when Kari wrote “We do indeed have plans to add support for OpenOffice–it should happen sometime in 2007″ the meaning behind that was “We’ve been talking to Bruce and others, and we’re hoping to work with them later in 2007 to get a similar plugin running for OpenOffice.” The statement was more opaque than it might have been, but it doesn’t belie a master plan evolving within CHNM to exclude OpenOffice folks (heck, we’d *love* it if someone else would step up and start building that functionality, rather than waiting for us to do so).

In the end, I think (and this is now just speaking for myself, rather than on behalf of Zotero as a whole) that the one thing that we *could* do better is make the process of feature development more transparent; it seems that Bruce’s main concern is that there are discussions happening and decisions being made behind closed doors, without real community participation. This is true on some levels; since most of us have offices along the same hall, we have a bunch of informal conversations that we don’t report back to the dev list or forums immediately (unlike most traditional open source projects, in which virtually *all* essential discussion happens in public, electronic fora). Our first concern has been simply getting software out the door that appeals both to our sense of good design as well as what our grant funders want, and in that rush we’ve often taken the route of quick conversations and decisions which can appear opaque from outside the CHNM offices. With that in mind, we’re going to try to do better, pushing those discussions out onto the dev list (where anyone else who’s concerned can join in while things are being figured out) when possible, and doing frequent reports on in-house projects and planned features out to the group…

Beyond that, however, there is an aspect by which Zotero will be always a bit cathedral-like; our current model is more like a service, where the core app is developed by a relatively small group of in-house or vetted devs, but with tons of hooks and an API enabling the flourishing of third-party utilities that extend it. We’ve created detailed developer documentation, including a sample utility, and we’ll be adding more to this as our APIs stabilize. Zotero has been built from Day 1 to be extensible in nearly every way possible. In short, less a massive cathedral than a small building in the middle of the bazaar…

Inspired by a post by Jean Burgess, a tag cloud visualization of my book manuscript, (currently being copyedited):

(via TagCrowd)

The CES Swarm went swimmingly (there’s really something to this idea of collaborative research), and now I’m back home starting to fit the pieces together and figure out what I make of them. Some fragments:

* Going into this year’s show, I had a few established interests: the relationship between amateurs/enthusiasts and professionals, the role of conventions as social spaces for communities to cohere, and the fetishization of technology.
* One of the things I kept hearing prior to and during the show was an underlying narrative questioning the relevance of CES as a show. In several press accounts before the show, you had retailers asking themselves whether it was even worth attending the show, given its cost and sprawl, a sense which was echoed by a few of the attendees I spoke with.
* There seems to be a core contradiction in the gatekeeping mechanisms for the show – CES bills itself as the world’s biggest technology trade show (a claim which bears no small resonance with earlier World’s Fair hype), and there’s a sense that the sheer size of the trade show floors and numbers of attendees are some of CES’s greatest assets (the show is measured in square feet and bodies), thus more attendees = better. However, perhaps in response to the aforementioned relevancy questions, the registration process repeatedly emphasized that attendees (who could register for free up to a week before the show) *must* be affiliated with the consumer electronics industry, implicitly restricting attendance (and going against the bigger = better rhetoric by which the show is advertised).
* This tension is, of course, ultimately bunk…one of the worst-kept secrets around CES is how ridiculously easy it is, in fact, to get an attendee badge. My favorite interview of the show was with a guy who fabricated a video store two decades ago, and attends every year with his made-up business cards; most don’t go to those lengths, however, and one could argue that it would be pretty difficult, in this day and age, for an interested party to find a consumer technology relationship, however tenuous, with his or her own work.
* Which leads me to the relative unusefulness of “Consumer Electronics Industry” as a category, consumer technology being so vague and pervasive that virtually anything might conceivably fit under its umbrella.
* On the press coverage: while the registration and gatekeeping mechanisms were all about keeping the public out, the media narratives were all about simulating the experience of being an enthusiast visiting the show. Press coverage bypassed the “Industry” part of the show almost entirely, except in the sense that manufacturers were displaying their wares…from the vantage of the television cameras and newspaper reports, retail and distribution were functionally invisible.
* Another axis: the main CES foci were screens and mobile devices. That said, the really big announcement of the week didn’t even come out of Vegas, but hundreds of miles NW in San Francisco, where Apple unveiled both the iPhone and AppleTV. On the CES floor, there was only a very small sense of impact, but in the Press Room on that Tuesday morning the buzz was all about MacWorld, and a cursory look at press coverage seems to bear that assessment out.

As I wrote a few days back, one of the threads underlying much of my thinking over the past year has been how we might use technology to nudge “scholarship” in a more publicly engaged direction. As a good STS do-bee, however, I’m the first to say that the technology isn’t what effects change, but rather it’s the people using it. That in mind, I’m heading off to the 2007 Consumer Electronics Show in Las Vegas this Sunday for a group experiment in new modes of scholarship.

The original idea came out of an ECHO workshop that I ran at GMU a year and a half ago. A few of us (Julian Kilker and Alex Russo, to be precise) were talking about the general isolation of research and writing in the humanities, and wondering if there were some way to set up a more collaborative research project. Somehow (I can’t recall exactly how), we hit on the Consumer Electronics Show as an intriguing site, one which was way too big for any one person to tackle as a researcher. What if, we thought, we could get a bunch of scholars from across the disciplines together in that one place, turn the pack loose on the site and then bounce ideas off of each other? What kind of scholarship could that produce?

Over the next year and a half, the idea mutated a bit; at some point, it took on the name “Swarm Scholarship.” We looked into funding, but nothing really panned out. Finally, at this year’s SHOT meeting in Las Vegas, we decided to do something about this for real, on the cheap. Julian could line up housing and some space on campus through UNLV, and the only other costs for participants would be airfare and food. In the span of a month and a half, we circulated a proposal (see the full proposal below) via a few mailing lists and word of mouth, and received dozens of expressions of interest.

So, on Sunday about 15 scholars from around the country will be meeting up at Julian’s house in Las Vegas. We’ll compare interests, coordinate schedules, and then spend the next two days immersed in CES. Afterwards, we’ll spend the better part of a day giving from-the-hip “talks” on our ideas-in-progress, then head home to write. The goal is to get this published in some form or another sooner than later, aiming for something with the substance of scholarship but the latency of feature journalism.

And I’m sure I’ll blog more about it sooner than later.

Finally (after three months of “I’ll get to it one of these days”) switched this site over to Dreamhost. If you find anything that seems buggy, please let me know…

I’ve been thinking a lot about the various strands of work I’ve been cultivating over the past year (while working on a series of round-up posts), and there seems to be an underlying thread of reinventing scholarship, particularly with regard to transparency of the research process. With that in mind, I found Chris Anderson’s recent posts on Radical Transparency extremely resonant:

Six tactics of transparent media
1) Show who we are. All staff edit their own personal “about” pages, giving bios, contact details and job functions. Encourage anyone who wants to blog to do so. Have a masthead that actually means something to people who aren’t on it. While we’re at it, how about a real org chart, revealing the second dimension that’s purposely obscured in the linear ranking on a traditional masthead?
Upside: Readers know who to contact. The organization is revealed as a collection of diverse individuals, not just a brand, an editor and some writers.
Risk: Competitors know who to poach; PR people spam us even more than usual.

Read: public websites / blogs for scholars.

2) Show what we’re working on. We already have internal wikis that are common scratch pads for teams working on projects. And most writers have their own thread-gathering processes, often online. Why no open them to all? Who knows, perhaps other people will have good ideas, too.
Upside: Tap the wisdom of crowds
Risk: Tip off competitors (although I’d argue that this would just as likely freeze them; after all the prior art would be obvious to all); Risks “scooping ourselves”, robbing the final product of freshness.

This is the trickiest thing for humanists and social scientists to get past – the idea that describing your work in public before it’s “published” (whatever that means anymore) leaves you open to idea theft, where what it really does is allow you to marshal the community behind your project (shades of Latour) and allow you to claim the territory early.

3) “Process as Content”*. Why not share the reporting as it happens, uploading the text of each interview as soon as you can get it processed by your flat-world transcription service in India? (This may sound ridiculous, but it’s exactly what wire services such as the AP have long done–they update their stories with each new fragment of information). After you’ve woven together enough of the threads to have a semi-coherent draft, why not ask your readers to help edit it? (We did it here, and it worked great). And while you’re at it, let them write the headlines and subheads, not just for the site but also the punchier ones for the RSS feed and the one that has to work with the art for the magazine.
Upside: Open participation can make stories better–better researched, better thought through and deeper. It also can crowdsource some of the work of the copy desk and editors. And once the story is done and published, the participants have a sense of collective ownership that encourages them to spread the word.
Risk: Curating the process can quickly hit diminishing returns. Writers end up feeling like a cruise director, constantly trying to get people to participate. And all the other risks of the item above.

We’ve got plans afoot for syndication of research streams via Zotero – I want a sidebar alongside this blog that would let colleagues see what I’ve been reading, and arguably how I’ve been fitting it together as I move through a body of work. Add in the ability go generate feeds based on tags or particular projects, and things get really interesting. Let me do this collaboratively, on the level of topical projects or discipline-wide organizations, and you’re reinventing the role of departments and associations/societies.

4) Privilege the crowd. Why not give comments equal status to the story they’re commenting on? Why not publish all letters to the editor as they’re submitted (we did that here), and let the readers vote on which are the best? We could promise to publish the top five each month, whether we like them or not: “Harness our tools of production! Make us print your words! Voting is Power!”
Upside: Maximizes participation.
Risk: If we don’t deploy voting tools or (sigh) a login system, trolls may rule.

Two words: peer review. We already do it, we’re just not calling it that.

5) Let readers decide what’s best. We own Reddit, which (among other things) is a terrific way of measuring popularity. Why should we guess at which stories will be most popular and give those preferential treatment? Why not just measure what people really think and let statistics determine the hierarchy of the front page?
Upside: A front page that reflects reader interest better.
Risk: A more predictable and lowbrow front page.

The risk here is particularly problematic for academics, though anything that drags us into more engagement with the world on the other side of the ivory walls is useful; the way to get past it is to allow for the creation of many “front pages” – one for History writ large, one for American historians, one for historians of 20th century American technology. Have people join whichever communities they choose, and vote there and there alone.

6) Wikifiy everything. The realities of publishing is that at some point you push the publish button. In the traditional world, that’s the end of the story. It is a snapshot in time, as good as we could make it but inevitably imperfect. The errors (and all articles have them) are a mix of commission and omission–we hope for the best yet brace ourselves for the worst. But what if we published every story on a wiki platform, so they could evolve over time, just like Wikipedia itself? The original story would be the foundation of what could eventually become a version expanded and updated by readers (our Fortune 500 blogging wiki was an experiment in this). If you want to see the original version, just push the “original” button, or see any changes in-between by looking at the version history.
Upside: Stories live and grow, remaining relevant long after their original publication (at no cost to us!)
Risk: Stories get progressively less coherent as many cooks mess with them. Whatever brand authority the Wired name brings is diminished over time as the stories become less and less our own work.

There’s a lot of exploration that needs to be done here, particularly on the tension between allowing wikified *editing* and granular *commenting* – the latter preserves the authorial voice but requires a shift in how we read (seeing a text as the site of a discussion rather than a univocal lecture). I’ve been hearing a lot of murmurs about commenting and annotation lately, and I think that’s going to be the solution once we get past the initial experimentation phase.

Kevin just tagged me with the latest blog meme (actually, I think this one’s been going ’round for a while) – while it’s kind of fluffy to break my recent blog-silence with something as trivial as a meme, maybe it’ll get the juices flowing again:

1.Grab the book closest to you

Had to reach for the shelf, as I just spent the better part of today reorganizing my home office-area (consider it a bit of purge-cleaning after sending my final manuscript off to MIT Press for copyediting and page proofs earlier this week).

2. Open to page 123, go down to the fifth sentence

Yup.

3. Post the text of next 3 sentences on your blog

“‘The food is unfussy and ingredient-driven, usually constructed around a main course that’s essentially an iealized version of your standard ‘meat and two veg’ combo – one night it might be an aged Niman Ranch shell steak with spring peas and truffled mashed potatoes; another night it might be a Hoffman Farm chicken stuffed with wild mushrooms and greens, served with Chino Ranch carrots , turnips, leeks, and a horseradish sauce; and still another night it might be Laughing Stock Farm pork cooked in the fireplace with cardoon gratin, served with black kale and rosemary roasted potatoes. You might smirk at the menu’s relentless use of proper-noun pedigrees, but the overall Chez Panisse experience is, in a word, unpretentious. Yet, paradoxically, no restaurant in America has inspired, yea, invited more cultuish worship and precocious food-crit overdrive.”

4. Name the book and the author

The United States of Arugula: How we Became a Gourmet Nation, by David Kamp

Guess it’s my turn to point the meme onward: Sam, Sandy, Jeremy