Tuesday, 10 August 2010

Post 3: Risk Analysis & Success Plan

The following potential risks have been identified and steps taken to minimise the risk

  • Timescales & staffing -
    • Coordinator post being recruited dedicated to the project
    • Other staff may be made available to support the project if needed (for example, E-resources Coordinator, Acquisitions and Serials Officer)
  • Financial
    • Careful planning and allocation of budget
  • Lack of cooperation from system suppliers
    • Contacting suppliers in good time in order for them to be able to give demos within the required timescales
High demand for the final documents produced by the project will not be a problem as they will be freely available via the Creative Commons Attribution-Share Alike UK 2.0: England and Wales license.

    Post 5: Project Team Relationships and End User Engagement

    The project team will consist of:

    Anna Langley & Angela Walker (Project Manager) job-share the Digital Developments Manager role. They have been involved in making electronic resources available to the University of Salford community, including the purchase and implementation of SFX and Metalib. They are currently working on Salford’s institutional repository, RFID implementation and a review of the LMS market.
    Regina Ferguson, Acquisitions Team Leader, manages the purchase of electronic resources, including the development of the coding system used to distinguish between different types of resources.
    James Allen, Collection Management Team Leader, is developing systems to monitor the use of Salford’s resources, and to track their licence terms.
    Project Administrator - to be recruited. They will support the project manager and be responsible for day to day administation and coordination of the project
    Jenny McNally - Digital Developments Officer, works on the library's systems including the LMS, link resolver and federated search tools

    Post 6: Projected Timeline, Workplan & Overall Project Methodology

    The project will be managed using Salford’s PRINCE 2 project management approach, led by Anna Langley & Angela Walker, Digital Development Team Leaders. 

    Below is the project plan:


    Post 2: Wider Benefits to Sector & Achievements for Host Institution

    Benefits for University of Salford
    • More efficient management of licences
    • Better understanding of the terms of the licences we hold
    • These will both allow us to better exploit our licensed resources
    • Seamless process for purchase to delivery of licensed resources
    Benefits for the sector:
    • List of requirements for reuse
    • Will provide starting point for others to do similar work
    • May highlight issues with current licences which would encourage suppliers to reassess the licences they provide
    • Provide basis for LMS suppliers to provide ERM functionality in their systems

    Friday, 2 July 2010

    Post 4: IPR

    As required by JISC the case study report and all other outputs will be published using the Creative Commons Attribution-Share Alike UK 2.0: England and Wales license.

    Post 7: Budget


    Costs will be split between travel to the workshops and staff costs. The staff costs allocated to the JISC funding will cover a project coordinator working approximately two days per week for the duration of the project. The cost of other staff involved in, and consulted by, the project will be borne by the University of Salford.





    Thursday, 1 July 2010

    Post 1 : Project Aims and Objectives

    The overall aim of the project is to produce a use case of ERM systems and a preliminary set of requirements for an electronic resource management system, for use by the University of Salford and other HE institutions and system suppliers.

    To facilitate this, the project will:

    • Review current manual processes that are in operation at the University of Salford
    • Identify the issues these systems present
    • Evaluate commercial systems and the limitations of these systems in meeting the demands of the HE community
    • Compile a requirements document that is robust and can be adopted by the wider community