Proposal to form a
Repository and Scholarly Communication Services Technical Team
2 October 2009 (revised 13 October 2009)
Proposed by Sarah Shreeves, Bill Mischo, Tim Donohue, Beth Sandore, Tom Habing, John Weible
This proposal calls for the formation of a Repository and Scholarly Communication Services Technical Team to provide the technical leadership and staffing for the development, implementation, and ongoing maintenance of a production repository for the preservation and management of digital assets and of the technical infrastructure needed to support scholarly communication services in the Library.
This group would be responsible for:
® A production repository for the preservation and management of digital assets in the Library;
® Continued development and support of IDEALS and the Electronic Dissertation and Theses system;
® Management of the technical interactions with external repositories like the Hathi Trust;
® Development and support of the technical infrastructure for tools such as BibApp and the eScholarship tools developed at Grainger;
® Investigation of and development of emerging technologies and infrastructures to support data curation, preservation of digital content, and scholarly communication services.
This group would be focused in large part on production Library-wide systems, but should routinely allocate a reasonable percentage of time to involvement in the more research-oriented and experimental work done within the Library and GSLIS around digital repositories and services (especially until a production system is up and running).
This group would be made up of the following staff:
® A technical architect to provide leadership for the team and high level planning for the repository efforts and other technical infrastructure; would also participate in development. This position- Technical Architect for Repositories and Scholarly Communication Services --would have a reporting line to the AUL for IT Policy and Planning. (suggested 60% of Tom Habing's time towards this)
® A repository developer (Tim Donohue's position -proposed as a permanent position) to provide the main development support for the repository infrastructure. This position would report to the Technical Architect.
® A scholarly communication services developer (the visiting EScholarship and Data Curation position) to assist with the development support for the repository infrastructure with a special focus on the associated services such as BibApp and the eScholarship tools. This position would report to the Technical Architect.
® A member of ISD (initially the Head of ISD)
® Participation from other areas of Library IT, particularly ISD, and others as well.
In addition, this team would need to work closely with a range of individuals in the Library. The chief stakeholders, at least initially, would be: the IDEALS Coordinator, the Head of Grainger, the Preservation Librarian, the head of Digital Content and Creation, a representative from the Archives, and the head of Infrastructure and Software Development. These stakeholders, particularly the IDEALS Coordinator, the Preservation Librarian, and the head of Digital Content and Creation, would have the largest stake in the technical services provided by the team, the team, or at least the technical architect will need to work with these stakeholders regularly. It would be expected that this wider group (with others added as needed) would be responsible for setting the policies and guidelines necessary for the implementation of a digital preservation management plan. The team will report regularly to this group and the AUL for IT Policy and Planning on goals, progress, and accomplishments, and will be expected to complete an annual unit report as do other IT units.
Several factors point to this being the right time to act on this proposal:
Included in this proposal below are two job descriptions - the first for the repository developer (Tim Donohue's old position) and the second for the scholarly communication systems developer (funded out of the Library/IT fee). Also, included is a job description for the Technical Architect for Repositories and Scholarly Communication Services which we propose would be a reassignment of 60% of Tom Habing's time.