Roles of PM and ST
From DigiRepWiki
Programme manager (PM) role
1. First point of contact with JISC for projects on all matters concerning the conduct, progress and outputs from the project
[interpretation: PM answers any questions (or, at least, manages the answering of any questions) from projects which might impact on how the project works or what it delivers.]
2. Primary source of guidance to projects and to the support team on how their work contributes to the Digital Repositories Programme, and fits with JISC and other work more broadly
[interpretation: PM answers any questions (or, at least, manages the answering of any questions) from projects which might impact on wider JISC or related activities (eg, eFramework)]
Support team (ST) role (derived from workplan)
1. Objective and activity area (v) from the 3/05 Circular: “Defining repository functional components and developing and synthesising frameworks”…
[interpretation: develop guidelines for scenarios, use cases and workflows, and provide advice and training to projects on using the guidelines]
2. Objective and activity area (vi) from the 3/05 Circular: “Developing guidelines and exemplars for the implementation of relevant standards, specifications and good practices in the repository area”…
[interpretation: (i) assess general training needs of projects (and meet them), (ii) act as a dating agency between projects and the technical / standards communities they should be talking to, and (iii) helping projects work with the standards catalogue]
3. Programme synthesis, outside the e-Framework-related work described in (1)
4. Advice on future directions, including advice on scoping future development programmes, and internal and external partnerships.
5. Programme dissemination and liaison with the wider community
[interpretation: working with PM on programme-level dissemination, making sure we don’t duplicate project dissemination or otherwise tread on people’s toes]
6. Consultation and validation of work via wider development (including standards development) communities.
[interpretation, as it says in the workplan, “advising and assisting projects as they liaise with development and standards communities.”. Also, working with the PM to help projects get the most from clusters and other links b/w projects]
7. Identified areas of common interest with international partners.
Queries from projects
I think we've agreed that there are likely to be two main types of question from projects:
A. technical / standards, or related to legal or some other professional domain; these get passed straight to the relevant professionals, be they JISC services, cetis sigs, ukoln experts or whatever. However, in assessing likely training / support needs, ST might want to note these questions down, in case a pattern emerges.
B. questions about JISC / project - type topics, which should come to the PM.
