After the third time this week I’ve replied to a list when I meant to reply to a person

I want an email client that offers a ‘reply to list’ function in addition to ‘reply to author’ and ‘reply to all’.

Even more importantly, I want it to put my message compose window in bright red or something whenever I’m replying to a list by default ‘reply’, which it should be able to detect.

Oh, while we’re at it, let me pick own my default-reply on a per-list basis.

Is that too much to ask? From how often I see people making this mistake (sometimes embarressingly),  I’d guess this is one of the biggest email usability issues (right after spam prevention).

Email list servs don’t always use list-* headers that would make it easy for a client to do this but I can think of some heuristics that could succesfully identify list traffic much of the time. Like when the “To:” header matches the “Sender:” header, or when the “To:” header matches the “Reply-to:” header–most of the time that’ll be a mailing list, and most mailing list messages can probably be caught by rules like this.


Linking Service to Open Access Repositories

Hadn’t seen this blogged yet anywhere I read, so I’ll cite it, even though I know some people are annoyed by just pointing to existing resources in your blog.

Has some good practical advice for attempting to integrate institutional repository and ‘e-print/pre-print’ content into your link resolver.
Shigeki Sugita et al.
Linking Service to Open Access Repositories
D-Lib Magazine
March/April 2007
Volume 13 Number 3/4 ISSN 1082-9873

Library Subject Guides (does this have something to do with Sakai?)

I have been thinking lately of a library subject guide system. A really great utopian library subject system. I imagined a system where librarians would list databases and other resources (chosen from Metalib and/or some other central repository of our stuff, when possible; URLs entered manually when not); also add other narrative text as desired. And organize the whole thing coherently somehow, without knowing any HTML.

And then we’re kind of at the kind of subject guides most of us have today (but perhaps easier to create), but then there’s all sorts of cool new features (I really hate saying ‘2.0’) we can imagine: Continue reading “Library Subject Guides (does this have something to do with Sakai?)”

Bibliographic Wilderness

So I finally get around to making a blog to write about library matters. Attending the Code4Lib conference was the final impetus. What a great conference. Nice to spend a week discussing with very smart people very interesting ideas about how to make libraries work better in the digital environment. The way we try to extend and grow this community is with communication, right? Less re-inventing of wheels and isolation, more synergy and collaboration. Not just on code, but sharing of analyses, plans and experiences, participation in public discourse to take our collective practice forward. So a blog is one way of doing that public communication (‘publishing’ is just a word for ‘public communication’, right? A blog may not be the best way to do it, but better than nothing).

Continue reading “Bibliographic Wilderness”