You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Project</strong> Identifier:<br />
Version: 2<br />
Contact: Kerstin Mey<br />
Date: 15 December 2011<br />
defined areas of responsibility<br />
and monitoring of project plan.<br />
Recruitment 2 3 6 The core project team will be<br />
seconded from existing posts;<br />
approaching two photographers<br />
will create a contingency plan;<br />
students will be recruited through<br />
course leaders, who will have<br />
been thoroughly briefed on the<br />
project; recruitment of student<br />
assistants will include a reserve<br />
list.<br />
Staff<br />
retention<br />
2 3 6 Identify adequately qualified staff<br />
at UCA and Zandra Rhodes<br />
Studio who could be seconded if<br />
necessary; integrate activities as<br />
far as possible into mainstream<br />
developments at UCA.<br />
Staff skills 2 3 6 Maintain skills profiles and<br />
ensure effective professional<br />
development; establish external<br />
links to source skills on a short<br />
term basis if necessary;<br />
additional photographer as<br />
contingency.<br />
Quality and<br />
robustness of<br />
data<br />
1 5 5 Quality assurance processes<br />
(see section 3.2).<br />
Copyright<br />
and licensing<br />
Technical<br />
viability<br />
4 4 16 Audit copyright status of any<br />
accompanying primary and<br />
secondary source materials early<br />
on in the project, to inform<br />
licensing and OER development<br />
and allow sufficient time to clear<br />
copyright with third party rights<br />
holders if required.<br />
2 4 8 Ensure the team has relevant<br />
experience; reanalyse technical<br />
requirements including specialist<br />
equipment at an early stage in<br />
the project; review technical and<br />
user requirements regularly.<br />
Technical<br />
standards<br />
Page 9 of 20<br />
Document title: JISC <strong>Project</strong> <strong>Plan</strong> Template<br />
Last updated: Feb 2011 – v2.0<br />
3 5 15 Discuss the technical standards<br />
with project team and VADS<br />
early on; use JISC guidance on<br />
standards to ensure accessibility,