Noel Welsh, after reading the last post, also suggested Citeseer. I hadn’t forgotten it, but I had instead assumed I’d make a “second pass” through the material I was examining.
Now, my approach was to spider my way through some bibliographies, until I exhausted what looked like viable/useful material. Along that path, I’d incidentally find other things of interest (by crawling author’s homepages, for example). However, I think the idea of having to go back, and retrace steps, is (obviously?) a bad idea.
So, I’ll retrace my steps for what I’ve done so far, and think about any other resources I can use in my search.
The interesting bit that came out of the exchange, however, was
From: Noel Welsh
Date: Fri Mar 7, 2003 11:43:21 AM Europe/London
To: Matt Jadud
Subject: Re: citeseer
<snip/>
You can add papers to citeseer. Give it a URL and it
will index everything it finds there. <snip/> I did this with
readscheme.org to get it to index our paper from the
Scheme Workshop. See e.g.
http://citeseer.nj.nec.com/site/551066
HTH,
N.
And yes, it does. However, before I do that, I have to figure out where papers I’ve written will continue to live for a reasonably long time. Put another way, I don’t like the fact that every time I leave one university location, the paper will have to move from one WWW home to another. A few things come to mind
- I could put things on jadud.com, but that is a personal site, not an academic one.
- I may be able to make use of some facility of MoveableType to allow CS-ED.org participants to keep papers there. This way, even if the entire project moves, the URL will remain.
- Sourceforge is in the business of hosting content for open-source projects… perhaps I can create a CS-ED.org project, and we could actually store academic content there? There are certainly copyright issues here… but, then again, some of the papers I just checked for in Citeseer (they are there) are available from the authors themselves, when legally they probably shouldn’t be…
It needs more thought.
Postscript:
This post raises the question of how I should properly include private communication in a blog. One approach would be to always ask first. Another approach would be to assume that communication via email is a dangerous thing at best, and you should always assume it might be logged, blogged, or otherwise published with or without your consent. I imagine, if I simply exercise good judgment, then I won’t get myself into trouble. Besides, I can always edit/remove posts if someone complains (“it’s easier to ask forgiveness…”).
|