Web 2.0 from a publisher perspective, using 2Collab as an example

One of the big challenges for all of us developing Web 2.0 is finding out what the users actually want.  That's part of why libraries and publishers are taking various lab, web development group, developer network and contest approaches.  Another big challenge is trying to build a community around your tools.

Just a quick review of some of the online activities:

There are lots of library labs, and a few publisher initiatives, including Elsevier Labs, Elsevier Scopus Labs (accessible only to Scopus subscribers), Ingenta Labs, and Nature's Web Publishing group (I don't think it has a home page, but you can see some of their work on Nature Launch Pad).  In the sort of library-vendor space OCLC and Talis have developer networks.  I think some of the other library catalogue vendors may have developer spaces, but they are usually closed.

Looking at a few more Elsevier things specifically:

Elsevier has SciTopics, which is also on Twitter.

Elsevier also just announced the winner of their Grand Challenge, the Reflect project (if you follow my FriendFeed, you may see some familiar names in the winning team, like Lars Juhl Jensen and Michael Kuhn).

Which brings us to Elsevier's 2Collab.  I had a chance for an advance preview of 2Collab in late 2007.  It takes a somewhat different tack to other academic bookmarking tools, focusing a lot on group collaboration.  I had a chance to see Camelia Csora present about 2Collab as a research collaboration tool (PDF) at NISO Discovery Tools forum in 2008.

There are lots of challenges with these kinds of tools.  Can we integrate them into user workflows?  Can they understand bibliographic metadata, do lookups on DOIs, read COINS from source and embed COINS into their bookmarking pages?  Can we build standard APIs for these services?

Camelia has moved on to ebooks, and I see in my FriendFeed today that the new Product Manager for 2Collab, Michael Habib, will be presenting about 2Collab as a publisher collaboration tool

http://www.slideshare.net/habibmi/engaging-a-new-generation-of-authors-reviewers-readers-through-web-20

You can read more in his posting Engaging a New Generation of Authors, Editors, and Reviewers - Presentation for Boston Editors' Conference.

One of the big challenges in this area is getting people into the new network in order to collaborate - this is the issue that most of the "scientist social networks" have - there's no one there.  Even using Google Docs to collaborate tends not to scale very well, as you end up having to invite and reinvite groups of people to each new document.  FriendFeed as a collaboration space I think has a lot of advantages, in that it brings an immediate, individual benefit (mindcasting/lifecasting unification of web activity) as well as a critical mass of people, as well as lightweight group and discussion tools.

That's not to say you couldn't use 2Collab along with FriendFeed - and it occurs to me that one immediate step all the publishers (and other service providers) could take would be to work with FriendFeed to add their academic bookmarking services added as top level "import" sites.  Right now, despite a strong scientific user community, FF only has the non-academic sites in its list: 

• delicious
• Diigo
• Furl (which is now gone, bought by Diigo)
• Ma.gnolia
• Mister Wong
• StumbleUpon
• Twine
• はてな

The key point is it can no longer be either/or. It's not my site OR your site, it's all of our sites, interconnected. It's also/and.  I have to be able to go seamlessly from LibX to Zotero to Mendeley to Connotea to EndNote to 2Collab to Papers to FriendFeed and back again.  If Zotero has a great tool, I should be able to call it using an API from LibX.  Data can't be trapped at point of creation, it has to be able to flow around the web to be useful.

Comments

[Aarontay]

"I have to be able to go seamlessly from LibX to Zotero to Mendeley to Connotea to EndNote to 2Collab to Papers to FriendFeed and back again. If Zotero has a great tool, I should be able to call it using an API from LibX. Data can't be trapped at point of creation, it has to be able to flow around the web to be useful."

I agree with this 100%.