Developing training materials

At the start of the RePosit project (and probably even before then), one of the planned outputs was a set of generic training materials (user based) to help other repository managers should they head down the route of linking their CRIS to their repository.


There is a huge assumption implicit in this however, and one which we as a project group have found difficult to resolve and reconcile. In essence, regardless of the software you are using for either CRIS or repository, there is an assumption that the underlying process is at least similar if not the same. This is perhaps a little naive and has certainly been a bit of a stumbling block.


On a very basic level, when you present this model to your users, what you want to get across is:
Login
Upload
All done through the same interface, no need to toggle between CRIS and repository, all done at the same time in one simple set of steps


In technical terms, this is broadly the case (login, find publication, browse to find file, upload file). However, when attempting to apply this to a simple (generic) how-to guide, it turns out it's not so simple afterall. Really obvious, really basic actions become really important: logging in, for example. How do you describe what actions constitute the logging in process? If everyone used the same CRIS software, this wouldn't be an issue (other than for the Competition Commission), log in would just be 'log in', simply because there would only be one way to do it. Similarly, getting to the point of browsing for the file to upload would be just 'find publication', all actions could be illustrated with a few snappy screenshots and you'd be done. When you're not using the same software though, it's hard to provide a simple set of instructions that doesn't become obsolete by its very vagueness.


There's also the problem of what the 'link' between your systems is called (if it has a name other than 'link thingy') and the fact that we're all using different repository software too.


In reality, whilst it would be nice to say we could produce glossy guides and materials that will just provide you with a complete package for your CRIS-Repository set up project, the honest truth is, some things you'll just have to do yourself or need to be software and local implementation specific and best dealt with by you or your vendors.


We love collaboration, but now and again, it can make something simple really, really complicated!


Sarah Molloy, Research Support Librarian (Repository and Publications System Manager) Queen Mary, University of London

Collaborative project team

Being part of this JISC project team has turned out to be very enjoyable and a fantastic learning experience for us all. This is due to the diverse roles of the project team in the different Universities and the professional expertise of Symplectic.

Roles range across the Library, the Central Research Office through to Academic Systems. There is also a range of roles within the library giving the perspectives of the Library Liaison staff through to Electronic Resource staff. Having all these different perspectives helps us all to understand how our own University works and was very helpful when putting together the advocacy plans (where we shared good practice).

It has also proven informative to share the experiences of the partner Universities at different stages of their repository implementation. For example those of us who have never had a repository before can learn from both the successes and mistakes of others further down the line. One key message that the project team have learned is that you can't just raise awareness of the repository once, as a one-off exercise, there has to be continuous promotion. Also the more established repositories can also learn new tricks: for example, colleagues have been very interested how Keele has linked its publications database (and repository) to individual staff webpages. This has encouraged academic colleagues to keep their entries up to date (and deposit), as it instantaneously updates their web page, all from one system!

I'm sure there will be more shared knowledge and experiences next year as we move into the advocacy stage.

Ellie James

Keele University