1 / 10

Which One’s Which? Strategy and Advocacy 22 nd April 2008

Which One’s Which? Strategy and Advocacy 22 nd April 2008. Strategy and Advocacy. VIF Recommendations, Dave Puplett Policies and OpenDOAR, Peter Millington Demo of Subversion, Peter van Huisstede Discussion on issues for repository managers. VIF Recommendations:.

lilith
Download Presentation

Which One’s Which? Strategy and Advocacy 22 nd April 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Which One’s Which? Strategy and Advocacy 22nd April 2008

  2. Strategy and Advocacy • VIF Recommendations, Dave Puplett • Policies and OpenDOAR, Peter Millington • Demo of Subversion, Peter van Huisstede • Discussion on issues for repository managers

  3. VIF Recommendations:

  4. Be clear on what you want to you your repository for and what you want it to handle Consider what sort of version confusion could arise from your repository Get the right software and exploit its functionality Strategy

  5. Policy • What do you consider to be a version? • How will versions be organised in the repository? • What versions will your repository keep? • Ingest policy? • OpenDOAR

  6. FRBR and Different Object types • FRBR: Work, Expression, Manifestation and Item • This structure allows objects to be linked in relationships to the unifying concept of ‘work’ • More and more objects that aren’t simple text are being deposited in repositories, such as data, learning objects, audio and video. • Make policy decisions about how these will be stored, what formats and where.

  7. Metadata, Ingest Process • Metadata is being discussed next door – the framework has detailed suggestions on what information to put in metadata and how to expose metadata better. • Ingest is the best opportunity to clarify version status directly with the content creator. Can this be done automatically? Methodically? What questions to ask? • Check for duplication within home repository and, if possible, external repositories.

  8. Advocacy • Obviously getting people to deposit in the first place is hard enough, let alone getting them to worry about versioning. • However, there is much advice and support for content creators that can help their own versioning habits. • Suggest that content creators look at the Content Creation section of the Framework (more on that later). • The VIF flyer introduces headline recommendations and advice to help work be recognised and identified correctly. • Distribute copies of the VERSIONS project Toolkit, to your academics; it is aimed at authors and content creators.

  9. VIF Recommendations:

  10. Project Director: Frances Shipsey,LSE Library,f.m.shipsey@lse.ac.uk Project Manager:Jenny Brace, LSE Library, j.e.brace@lse.ac.uk Project and Communications Officer:Dave Puplett, LSE Library, d.puplett@lse.ac.uk Project Officer:Paul Cave, University of Leeds, p.l.cave@leeds.ac.uk Project Officer:Catherine Jones, Science and Technology Facilities Council, c.m.jones@rl.ac.uk

More Related