> that most other eLib areas are similar. UKOLN's eLib pages
> (<URL:http://ukoln.ac.uk/elib/>) and Ariadne
> <URL:http://ukoln.ac.uk/ariadne/>) are also a great ways of letting people
> know what eLib projects are planning/doing/done (which is after all why
> JISC funded Ariadne's web version accoring to the copyright page - see
> <URL:http://ukoln.ac.uk/ariadne/about/copyright.html>).
Indeed. For those who don't know, 3 to 5 eLib projects get featured in
*both* the Web and Print edition of Ariadne. In addition, people involved
with projects get to write on various related matters (look out for Stevan
Harnad's excellent piece, and the main article about JISC circular 3/97,
in the next edition on hopefully friday)
> * I noticed that the eLib working papers and reports at
> <URL:http://ukoln.ac.uk/elib/wk_papers/> were a bit thin on the ground;
> maybe we should all write a technical report or two to describe some
> element of our projects and whether we think that we did was the right way
> to do it, what we'd do if we were starting again now, etc, etc. Or maybe
> these should go in Ariadne?
Have been mulling on having a list of pointers to technical reports
written by projects and mounted on their own Web pages in the updated eLib
Web pages; comments from projects to me appreciated on this.
Some projects are very good in writing reports and progress developments
and mounting them. Suspect that a lot of them, in this phase of the
programme/their projects, are a bit overwhelmed with evaluation reports,
annual reports, continuation/further funding requests and masses of other
paperwork (electronic library generates paper like there is no tomorrow
:-) - though in future months (for those with a future), "looking back"
reports would be more feasible.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|