Notes from our meeting on 17th Dec

1. SCONUL project

1.1 Regina is attending the workshop at Bournemouth Uni on Monday. 

1.2 Discussed which use cases Salford would like to provide - have suggested: 

• No. 7     Co-delivery of print and electronic
• No. 15   Move to e-only
• No. 6     Cancellation of e-journal title

1.3 Discussed who would attend other workshops/ meetings

2 Process maps

2.1 Looked at work on numbering workflows so far - need all processes to be numbered and also to identify inputs/ outputs, processes and descriptions 

3. ERM systems

3.1 Would like to mark systems we have seen against out requirements doc - Charlotte to see if possible to have access to demo sites for any of the systems.

This is an interim blog post, to refelct on the progress of the project so far, and discuss the exciting new developments for the project. Over the past 6 months, we have been looking at electronic resource management, and have had the opportunity to examine our workflows, and present these for the various scenarios that we currently operate. From the workflows, we have created a preliminary set of requirements for an ERM, which can be used by other institutions. We have applied the MoSCoW methodology to the requirements document, in order to prioritise our needs.

We are now in a position where the Salfmeri work is being further developed by the University in the SCONUL Shared Services strand of the JISC LMS programme, The current ERM Requirements and Workflow deliverables be will enhanced as part of that process. We aim to have 3 open source ERMs operational, in order for us to assess how easy they are to install, and also to walk through their functionality. We will continue to blog here, and also on the SCONUL project blog once it has been established.

Notes from our meeting on 26th November

1. Our current processes
1.1. Charlotte has added the Process Map to the blog.

2. Shared Services Project
2.1. Angela has received confirmation that we have definitely had funding approved to extend the project and work on the JISC/SCONUL Shared Services project. Angela will attend a meeting in early December to discuss further details
2.2. Angela has passed the details of some open source systems to Justin Wood, who will sort out hosting etc

3. Visit to Sheffield
3.1. Angela and Regina visited the University of Sheffield to discuss their use of Verde
3.2. They are implementing this system in stages, starting with licences, then moving on to trials

4. Requirements document
4.1. We did some more work on the requirements document, rating the ERMs using the ‘MOSCOW’ scoring system

5. Next meeting
5.1. Charlotte will arrange either an extended or additional meeting where we can work more on the requirements document and will email everyone with the details

Update on our requirements document

We didn't have a team meeting on Friday 19th, as about half the team weren't available. The remainder started to look at our requirements document and rated each criterion using the MoSCoW method:

Must have
Should have if possible
Could have if it does not affect anything else
Would like to have

More will follow on this after our meeting tomorrow (26th), where we will be looking at the document again, and preparing to mark each ERM based on this system.

Our current procedures - map

Here you can see the 'process map' showing all of our E-resources processes in one document:

https://docs.google.com/viewer?a=v&pid=explorer&chrome=true&srcid=0Bxug72ZifwRlODBlMmMzYTgtYWQ1Ni00MGFhLWE2ZDYtNTYxYTg4MjhlMjQ0&hl=en&authkey=CKf3hVQ

Just to clarify, 'Collections' on this document refers to JA & DL/AD (see previous post on people involved in the process), who look after our resources on SFX and Metalib, collect stats etc.

'Acquisitions' refers to ST & RF, who work more with the Talis records, financial information etc

Notes from our meeting on 12th November

1. Our current processes
1.1. The ‘process map’ document is in the MERI folder on the V drive. Please have a look and make any changes/additions, or pass suggestions to Charlotte who will update it
1.2. Angela will email David Kay with the updated workflows
1.3. Regina will organise a meeting with some representatives from Academic Support, Acquisitions team etc to review our processes and work out whether we are including tasks that aren’t necessary

2. Timing our processes
2.1. We will be looking at timing our current processes, as part of working out the cost benefits of an ERM. After the review we will time the ‘new’ processes and compare the two.

3. Feedback from ERM Demos
3.1. Charlotte reminded everyone to give some feedback on the ERM demos, and will contact Andy Callen for feedback on the Verde demo that he attended

4. Visit to Manchester
4.1. Angela, Regina and Jenny visited the University of Manchester to see their ERM system
4.2. Because the ERM market is in a state of flux, Manchester opted to produce their own in-house system. It is due for completion in February 2011, and they hope to use the system for the next 2-4 years. They have a software developer in their team, and received some funding in order to set up the system.
The system stores supplier info, stats, contact details etc – holdings information is acquired from suppliers and inputted, and checked against their holdings on SFX. Links to licence information are via Livelink (content management system)
They are still using Talis to store all the financial information, as they have integration with the finance system
They are also working on Journal Usage Statistics Portal (JUSP), a shared resource which will enable libraries to access statistics from one place (more info at http://www.jusp.mimas.ac.uk/)

5. Requirements document
5.1. We looked at Jenny’s tidied-up version of the Requirements list and clarified some ambiguous points. We will look at this further next week when we will concentrate on rating the ERMs using the ‘MOSCOW’ scoring system

6. Next meeting
6.1. 19th November 11.00am

People involved in the acquisition and maintenance of our E-resources

The flowcharts I added that depict our current processes are the instructions used by our staff. As such, they are very specific to Salford and there are quite a few inititals used to denote the people invovled, so below is a bit of an explanation of the various people and teams involved in the E-resources process:


Collections and Digital Developments Team:

Stella To (ST) - Acquisitions & Serials Officer: creates records on Talis, pays invoices, looks after renewals etc - has quite a lot of contact with vendors and keeps our information up to date on the E-resources spreadsheet as well as Talis

James Allen (JA) - Collections Officer and
David Lockley & Angela Dudley (DL/AD) - Collection Management Team Leader: maintain access to resources via SFX & Metalib - queries from the enquiry desk etc are passed on to the Collections Officer. Collect stats at renewal times; contact suppliers about problems, queries etc. Will speak to suppliers regarding trials and advertise these on the E-library blog

Regina Ferguson (RF) - Collections Manager: Checks & signs licences, manages funds so oversees the whole acquisition process
Licences also need to be read/signed by Sue Hodges (SH), Head of learning and research support; and Julie Berry (JB), our Acting Director


Academic Support Team

Academic Support Librarians (previously called Information Specialists and Liaison Officers) look after the resources for a particular school. They will often receive information from suppliers about new resources, trials etc. They are consulted when ordering, cancelling and renewing resources; they are in contact with acdamic staff so know which resources are most relelvant, on reading lists etc
They also provide training to students on using resources relevant to their subject


Customer Services Team

I spoke to some members of the Customer Services team regarding access issues. Although this team isn't directly involved with the acquisition and maintenance of resources, and not included on the flowcharts, they play a key role in making users aware of available resources, and are the first point of contact for any queries, access problems etc.

Enquiry desk staff (both on the physical desk and on the phone) answer queries from borrowers regarding electronic resources e.g. how to access resources, problems with access etc

Service Delivery Team Leader - currently working on a project to make more electronic resources accessible to external borrowers. Currently there are very few electronic resources made available on walk-in access PCs, but there are more resources that could be made available. Between the Collections and Customer Service teams, we are finding the licences that will allow some access to external users, and making those resources available.

We have been working on presenting our processes in a slightly diffrent format, which breaks down the individual tasks by team, hopefully making it clearer who is responsible for each stage.

Notes from our meeting on 5th November

1. Ex Libris user group conference
1.1. Jenny attended the Ex Libris user group conference earlier this week, and attended a discussion on Verde which was interesting. She spoke to Richard Cross from Nottingham Trent, he is happy for us to contact him and a visit may be possible to see how they use Verde

2. Meeting with David Kay
2.1. James reported on the meeting last week with David Kay from SERO Consulting (attended by JA, RF, AW, SH). David is working with JISC and SCONUL on their shared services plan, and he discussed their upcoming project in relation to ours.
2.2. The project will include around 12 institutions; they will look at their workflows and consider what elements could work at a national level. A lot of the work they will do will be similar to the work we have already done, so we would be brought in as an ‘extra’ institution
2.3. If we join the project, between November and April, we will visit about 6 of the participating institutions; work on a requirements catalogue and workflow templates for other institutions to use; look at open source systems – install, test and rate them; participate in meetings/events; rate the commercial ERMs we have seen; do a costing exercise for the workflows involved
2.4. We will still produce our list of requirements in December as originally planned

3. Feedback from ERM Demos
3.1. Charlotte has been asked for some feedback by some of the ERM suppliers. Can you please send any feedback/questions to Charlotte, particularly for the Swetswise demo as they are waiting for a response

4. Our current processes
4.1. Charlotte has been working on putting our existing workflows into another format. The ‘process map’ document is in the MERI folder on the V drive. Please have a look and make any changes/additions, or pass suggestions to Charlotte who will update it

5. Requirements document
5.1. We discussed whether any further additions need to be made to the requirements list. Jenny is doing some work on this before sending it to David Kay, so if you have any suggestions for items we have missed, please pass them to Jenny by next Tuesday

6. Next meeting
6.1. 12th November 11.00am

E-resources procedures

The flowcharts for our current Electronic Resources processes can be found below:

Overall process:
https://docs.google.com/fileview?id=0Bxug72ZifwRlZmU1MDA2ZjgtMzFmZS00ZjY3LThlNDUtM2IwMTBkM2RmMDg2&hl=en&authkey=CO3n03o

New orders:
https://docs.google.com/fileview?id=0Bxug72ZifwRlY2Y5ZDAzNjYtYTk2NS00MTkyLWIxYjItNDI0M2I2MDZkMTg3&hl=en&authkey=CPmEssAO

Renewals:
https://docs.google.com/fileview?id=0Bxug72ZifwRlOTdiYTExYzYtZTg3Zi00NDRmLWFlZmYtZjk4YTYwYjlmZjAz&hl=en&authkey=CLyO9bwH

Cancellations:
https://docs.google.com/fileview?id=0Bxug72ZifwRlOTQ2ZjkyYmUtM2Q0Ni00YzlmLWFmOGEtMDc1MDIwOTlkNDQy&hl=en&authkey=COTo5KQL

Our current procedures - more information

As the aim of this project is to produce a list of requirements for an ERM system, we first had to establish our existing processes and all the people involved, hence my interviews with various people across the Library. We discovered that a large number of people/teams are involved in the process of looking after Electronic Resources, or have an interest at least.
Obvious people are those responsible for the acquisition of resources and setting up access, as well as Academic Support staff who will nominate resources for trial/purchase in the first place, and who are consulted on renewals etc. We also discovered that there is work going on in our Customer Service team to improve electronic access for external borrowers, and the staff involved need as much information as possible on which resources might be available, what level of access they might have etc. Customer-facing staff on the Enquiry Desk etc need to be able to help and advise our users when they have problems using/accessing our electronic resources.
A lot of the information around electronic resources can be difficult to find - we keep information in various locations, like spreadsheets, filing cabinets, and inside people's heads. Also, we have recently had some staff moves and transferring of certain responsibilities, so it can be difficult to know who to ask and where to look for certain information.
Looking at our current processes turned out to be a worthwhile exercise, as it gave us a chance to review and update processes where necessary, and has prompted people to think about how procedures might be improved.
After going over our current procedures and updating our flowcharts, we're now working on one 'process map' detailing the entire process in stages, and going into more detail where appropriate. The original flowcharts are very specific to Salford, so the new format may be more useful to other institutions.

ERM demos

For the past few weeks we have had some demos of various ERM systems. Some brief descriptions are below:

Swetswise ERM as a Service: This system builds upon services already available through Swetswise; a benefit for existing Swets customers is that a lot of the subscription information, including licensing and financial information, is already in the system. This can also get usage statistics from publishers and present them in user-friendly formats

TDNet Core ERM: looks after the ‘core’ processes of electronic resource management – acquisition of resources, licence information, access, statistics and contact information. It's possible to link to licences from their A-Z list; we were shown the front-facing element of this system. It is possible to import and export data to/from other systems

Innovative Interfaces ERM: designed to manage the whole life-cycle of electronic resources, from identification and trials, to purchasing the resource (or subscribing to it), and then managing access and harvesting of usage statistics using SUSHI, providing information such as cost per use for renewals decisions etc. The system can be populated using data from e.g. an SFX knowledgebase.It can be used as an integrated part of Millennium LMS or as a stand-alone system; at the moment there are no sites using the ERM module with Talis,

Serials Solutions 360 Manager: tracks changes in titles and licences; deals with trials including reminders when the end of the trial period is approaching; The system can include retrieval of statistics which will work with SUSHI and COUNTER. It’s possible to display key points from licences; also to search for resources using alternate titles (abbreviations etc) There is also an online community/support centre

Ex Libris Verde: Can be a stand-alone system, integrates with other Ex Libris products (SFX etc). This system can manage trials, with the option to add notes on reasons to subscribe etc. Licence details can be added manually or a link to website, pdf etc can be added. Uses SUSHI when collecting stats

EBSCO NET ERM: This system works best with resources purchased through EBSCO; it can be automatically populated with all the subscription information. This system is fully customisable, enabling users to match field titles etc in the ERM to existing systems (LMS etc). it is able to work with a library’s catalogue, link resolver etc. Stats are collected using SUSHI/COUNTER; licence and financial information can be tracked; reminders can be set for individuals to perform certain tasks within workflows

Notes from our meeting 8th October

1. ERM System demos
1.1. Charlotte has sent updated meeting requests for the demos with the time/venue confirmed – we are just waiting on one more supplier (EBSCO) to confirm a date and time. The first demos will be on Thursday 14th October
1.2. We will have a representative from Academic Support attending each demo to give us their input; Anne Beech is attending as a representative for Customer Services; Angela W has also asked John Green to attend
1.3. Charlotte will ask the Academic Support team to recommend an academic to attend the demos.

2. Contacting current ERM users
2.1. Charlotte reminded everyone to give her suggestions of specific questions we should ask.
2.2. Charlotte will contact Sarah Robbins at LJMU again to get some more detailed information and discuss a possible visit. Angela W will contact Andy Land at Manchester and Andy Bussey at Sheffield to organise possible visits

3. JISC Project Manager
3.1. We had a meeting with Ben Showers yesterday which went well; we’re awaiting feedback etc

4. System Requirements
4.1. We looked at the requirements document for the ERM systems again, and extra points/questions were added. The document is in the MERI folder on the V drive so anyone can update it or pass any suggestions to Charlotte

5. Next Meeting
5.1. 15th October 11.00am

Notes from our meeting on 1st October

1. ERM System demos
1.1. Charlotte will send updated meeting requests for the demos with the time/venue confirmed as they are sorted out
1.2. We will have a representative from Academic Support attending each demo to give us their input; Charlotte will also ask Sue Hoskins/Maggie Barker to nominate someone from Customer Services to attend

2. Contacting current ERM users
2.1. Ongoing – Charlotte has asked for suggestions of specific questions we should ask.

3. Our current processes
3.1. Charlotte gave some feedback on her meeting with Sue Slade regarding partner colleges
3.2. Charlotte brought the flowcharts showing our current processes to the meeting and asked for feedback. Everyone was happy that they reflect our current procedures accurately; Charlotte will update the Collections management folder on the V drive with the most recent documents

4. JISC Project Manager
4.1. We have a meeting with Ben Showers on 7/10/10 at1pm

5. System Requirements
5.1. We looked at the requirements document for the ERM systems to use at demos in more detail, and extra points/questions were added. The document is in the MERI folder on the V drive so anyone can update it or pass any suggestions to Charlotte

6. Next Meeting
6.1. 8th October 11.00am

Our current procedures

I spoke to colleagues across the Library, to discuss our current procedures regarding electronic resources – looking at acquisition, licences, statistics and access.

Some things that we currently do, or would like to, are as follows:
Run trials and advertise them on the E-library blog
Licences checked at trial stage – this will be done in future by E-resources co-ordinator (recently appointed)
At the minute, we keep paper copies of licence agreements in filing cabinets – we want to start scanning licences and keeping copies on the V drive instead (this is part of the work being undertaken by our E-resources co-ordinator)
We put information on the intranet e.g. passwords page on the Library website; enquiry desk manual is updated.

At present we collect stats on an ad hoc basis, usually when Academic Support Librarians request them (for renewals, journal reviews etc) – usually we get stats through suppliers, sometimes via SFX; we compare price-per-view
We want to look at collecting stats more regularly & storing them in one place that is easy to find, so that it’s easy to get information when someone requests it. We also have to supply stats externally (SCONUL) so it would be beneficial to collect them ‘as we go’
Currently this can be quite a laborious task; would be beneficial if an ERM could make collection of stats quicker and easier

There are a couple of problems with Talis:
Does the ‘basics’ very well – setting up a record, paying invoices etc.
However, it doesn’t handle pro-rata payments, credits, 2 payments in one financial year etc very well – expected cost is worked out using the final amount spent in a year (doesn’t look at individual payments or period covered)
Doesn’t show changes in format very well – we usually cancel an old record and set up an entirely new one for E-upgrades etc
Hopefully an ERM could deal with issues like these and make it easier to track payments etc

I spoke to some colleagues about access to resources, particularly for external borrowers (Access Salford, partner colleges, SCONUL etc):
External borrowers currently have access to a very limited number of resources on walk-in access PCs. Anyone can use these; there is no difference in Electronic access for reference, SCONUL, Access Salford etc.
There is currently work going on to put together a list of more resources that can be accessed by external borrowers – a significant number of licences allow External Borrower access; it’s a matter of finding out what these resources are, then making them available via the walk-in PCs
There are essentially 2 types of partner college student - if students sign up at the University but study at the college, they are UoS students and have access to all our resources including electronic. If they sign up at the college, they are treated as any other external borrower when using our library, so have the limited access.
We would like to see licence agreements recognise different ‘levels’ of user and make some resources available to external borrowers; however we realise this is down to the licence provider rather than an ERM system. However, if different levels of access could be made available, a system that can deal with this and inform us of those different levels would be desirable.
If a resource is available to external users, we need to know this and make the resource available – we want to be accessible to students on foundation courses for example, in order to get them enrolling on degree courses

Notes from our meeting on 24th September

MERI Meeting Minutes
Time/Date:
24/9/10 11.00am

Notes and Actions


1. ERM System demos
1.1. Charlotte will send meeting requests for the demos with the venue ‘TBC’ so that everyone knows when each one will be.
1.2. Jenny spoke to Colin Carter from Innovative at the LMS showcase and found it very useful to see an ERM in action.

2. Contacting current ERM users
2.1. Ongoing – Charlotte to chase up the people already contacted. Jenny to give Charlotte the contact details for Andy Bussey at Sheffield

3. Our current processes
3.1. Charlotte spoke to Kath Kellet & Dan Leach about access for external borrowers and got some useful information from them. Meeting booked with Sue Slade for Thursday 30th to discuss access for members of partner colleges
3.2. Charlotte will bring flowcharts showing our current processes to the next meeting

4. Blog
4.1. Charlotte will add notes on her meetings/talks with various members of staff.
4.2. Meting minutes from last week are on the blog; Angela W has added a post on the benefits to the wider HE community

5. JISC Project Manager
5.1. We have a meeting with Ben Showers on 7/10/10 at1pm

6. Electronic Resources Officer
6.1. Jo Willows has started her post and has been talking to members of the team about various aspects of her work. Charlotte has invited Jo to the meeting with Sue Slade on Thursday, and Jenny will invite her to the weekly meetings

7. System Requirements
7.1. Angela W and Charlotte have made a start on a requirements document for the ERM systems to use at demos. This was passed around the team and extra points/questions added. Any more suggestions to be passed to Charlotte who will add them to the list
7.2. Angela also found a slide show on Verde and asked everyone to have a look at it and think about our requirements in relation to what Verde can do.

8. Next Meeting
8.1. 1st October – this will be an extended meeting, 11.00-13.00

Minutes from our first 'official' team meeting:


MERI Meeting Minutes
Time/Date:
Friday 17th September
Location:
CW Meeting Room 2
Chair or Facilitator:

Note Taker:
Charlotte Murray
Apologies:
Regina Ferguson
Attendees:
Angela Walker, Angela Dudley, James Allen, Charlotte Murray, Jenny McNally


1. ERM system demos

1.1. Charlotte is arranging demos with ERM suppliers for 14th-15th and 21st-22nd October. Times etc are still to be finalised in some cases
1.2. For the Swetswise Webinar we’ve been struggling to find a suitable room. Charlotte to contact Training Team to see if they can help
1.3. Jenny to contact Colin Carter from Innovative Interfaces about speaking to him at the LMS Showcase in Manchester on Wed 22nd September
1.4. Charlotte to compile a basic list of requirements before the demos. Please send any ideas for requirements/problems with current processes to Charlotte


2. Contacting current ERM customers

2.1. Ongoing – so far we haven’t had any responses/feedback from current ERM users. Anyone who knows of an institution or contact please let Charlotte know
2.2. Angela W spoken to Andy Land and Nigel Kimber at Manchester who have created an in-house system and is looking into the possibility of a visit to see their system in action


3. Our current processes

3.1. Charlotte is working on flowcharts that map our current processes (Acquisitions, Licensing, Statistics and Access) and has spoken to all members of the team to get their input.
3.2. Charlotte is meeting with Kath Kellet and Dan Leach on Monday 20th Sept to discuss access for external borrowers etc as they have been working the Access Salford scheme. Will also chat to Anna Langley about maintenance of databases


4. Blog

4.1. Charlotte will post meeting minutes on the blog
4.2. Angela will write a post looking at the benefits of our project to the HE community
4.3. Any ideas/suggestions for items to include in the blog, please let Charlotte know


5. JISC Project Manager

5.1. Ben Showers is our new project manager (replacing David Flanders) – Angela W has contacted him to invite him to one of our meetings.


6. Electronic resources Officer

6.1. Jo Willows will be starting this post next week and will be looking at licensing, statistics etc so will become involved in the project too


7. Miscellaneous

7.1. Angela D asked to see the original project bid, blog etc in order to catch up on what has already been done
7.2. Charlotte and Angela W to meet to discuss progress including examples of requirements documents used in RFID project
7.3. The meeting on 1st October will be an extended meeting where we will look at the final drafts of flowcharts etc mapping our current processes

Following on from the JISC LMS workshop on the 7th and 8th September, this post looks at why our project is important to the HE community. The first part of the project is basically unpicking all the different processes that are involved in the management of electronic resources. There is a wide range of processes in use including the use of spreadsheets, maunally checking items, and use of existing library business systems. We are then examining the commercial products on the market to see if they fulfill our Electronic Resource Management needs, along with meeting users of ERMs to discuss if the system they use fully meets their expcetations, and if they find that there are processes that they still have to carry out, outside of the ERM. Following this review, we will be producing a preliminary set of requirements which will look at an ERM system that can be used by other HEIs, we will also produce a case study examining the process we have gone through, and documenting our findings

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

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.

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