Tag Archives: rsp

The new RSP blog directory

Today we (the JISC-funded Repositories Support Project) launched a new directory of repository related blogs at http://rsp.ac.uk/blogs/

The launch statement says:

The JISC funded Repositories Support Project has today launched a new service – The RSP Blog Directory (http://rsp.ac.uk/blogs/). It provides a list of recommended and informative blogs regarding the repository scene from around the globe. Listed blogs include personal creations from those with firsthand experience of repository management and/or technical development of repository software; blogs for specific repositories, projects and software developers; as well as blogs for groups and societies with an interest in the open access movement and digital curation.

Each entry in the directory has a brief description of what the blog contains, with links to view either the entire blog or just the RSS feed.

Blogs have been arranged into categories by type, and you are able to download an OPML file to view the RSS feeds within your blog reader of choice for a selected category, or for all the blogs listed in the directory.

We hope the directory is pretty comprehensive but if you think there are any blogs missing from this list, please e-mail your suggestion to the RSP team at support@rsp.ac.uk

If you know of any blogs we have missed, please do get in touch!сайт

RSP Summer School 2008 – Repository publicity session

I’m traveling back from the RSP Summer School 2008 which has just finished. It was held up on the Wirral at Thornton Manor. The manor house, formally owned by Lord Leverhulme was a fantastic venue, and the food was top notch! Whilst there I gave an impromptu SWORD masterclass, and chaired the session on ‘Advocacy’.

The first of two presentations was given by Mary Robinson from SHERPA, who talked about her advocacy work for The Depot.

The second of the presentations was given by Niamh Brennan from Trinity College Dublin. This talk just blew everyone away – it was inspirational, practical, based on real experiences, and gave ideas that all the repository managers could take away with them and implement quite easily.

These are some of the insightful snippets I took away with me:

  • TCD populate their repository from their CRIS. Personally I believe this is the way to go, and enjoyed the chance to talk to Niamh about the technical side of the CRIS. I’ve yet to find an open source CRIS, and was wondering if this is because so much local integration would has to take place to stitch a repository into local systems, that once you have done that, the core CRIS might as well be developed from scratch. Niamh says that this is not the case, and that a core CRIS is big enough to be worthwhile sharing (and hopes to share theirs! 🙂 )
  • Get in contact with, and stay in close contact with, your local research support office. They deal with the grant process, and are a good way of making contact with academics. A good time to explain the impact of the funder mandates to researchers is when they are signing the T&Cs for their latest grant.
  • When it comes to publicity events, always celebrate success! Rather than having a formal launch of your repository, why not have a celebration of the items you already have in there, and the impact that has had.
  • Make people feel good – they like that! Possible examples include ringing up academics who have been in the news congratulating them, and offering to archive their work. Or make some of your depositors “Featured Authors”. People like to be ‘featured”!
  • Always try to get drinks at events, and once you have drinks, get some food. Once you have food, get some wine. Once you have wine, get some champagne. Once you have champagne, get a photographer. There’s nothing more that some people like that having a glass of champagne and having their photo taken at an event. This can be a powerful way of attracting senior managers.
There was loads more, but once the slides are uploaded onto the RSP web site I’ll put a link up. I hope I have represented the points made somewhat accurately, and apologise if I haven’t!

This entry was posted in Uncategorized and tagged , , on by .

Lessons from teaching DSpace

Yesterday I spent the day with a colleague delivering a training day aimed at new or potential DSpace administrators as part of my role working with the Repositories Support Project (known as the RSP).

We had a fun, interesting and busy day talking about DSpace, but a few hiccups along the way.

With each event we run, we learn new things about planning and delivering events. Whilst we’ve never had a bad event, there have been issues from time to time. With this event, the main issue was the hardware provided to us in the training suite at New Horizons in Birmingham. The staff were great, and the facilities good, the food was excellent, but the PCs were, ummm, a little on the old side! We were teaching DSpace, which is a piece of server software, so requires quite a bit of ‘infrastructure’ in terms of software requisities. Each trainee had their own PC with a copy of DSpace installed so that they had their own copy to mess about with, configure, and populate. To make this a little easier, we used the Ubuntu Linux distribution.

So when we combined Ubuntu (not a lightweight distro) with Postgres, Java, Tomcat, and Cocoon, lets just say that the poor 7 year old Pentium 866’s with 256 MB of RAM couldn’t quite cope. In fact, they couldn’t cope at all! Our other problem was that we’d configured the machines to launch Firefox as soon as they booted, so that the users were presented with DSpace straight away. Firefox had two tabs opened automatically upon startup, one for the JSP interface, and one for Manakin the XML interface. This meant that Tomcat then had to startup these web applications, at which point the whole machine came unusable and started swapping like crazy.

Our solution was to run round each machine and delete the more resource intensive Manakin user interface, and teach the course using the JSP interface instead. Even then, the machines were slow, so we had a lot of the trainees using one of our test servers back in the office instead.

So what is the lesson to be learnt from this?

Make sure you agree (in writing) the spec of the machines that you’ll be provided with at a training suite.

It sounds obvious, and we were probably just naive to assume that a PC training company would have machines that weren’t quite so old. But we live and learn, and have now negotiated a better room for our next course. Now to get the agreement in writing….реклама недвижимости