OER projects – liaison with other projects in the institutional strand

Or come to think of it subject and individual strands too…

As a repository development officer working on an OER project – Unicycle – I am interested in how we can most effectively integrate with JorumOpen and liaise with other projects in the institutional strand around technical infrastructure, standardised metadata and version control (to name but a few). We are using the intraLibrary repository platform and our project will aim to disseminate OERs via both our own and the national service; such liaison could be of potential benefit to JorumOpen and the wider community looking at OERs. For example I would like to explore a deposit tool utilising SWORD which could deposit a resource into both repositories simultaneously – such a tool could potentially be used by other projects to deposit resources into their local repository and JorumOpen. (N.B. How would such a tool deal with version control/synchronisation across platforms?) When I saw the recent demonstration of the Jorum OER deposit tool at the programme start-up meeting I hoped this technology might be suitable for this but have since learned that it is based on MrCute and does not actually link in with IntraLibrary or any other repository platform – it simply stores the IMS packages on a file system (Question: Are IMS packages ingested into the repository from there?) I’d be very interested in any feedback from Jorum and/or the community of OER projects.