Balancing Community and Local Needs: Releasing, Maintaining, and Rearchitecting the Institutional Repository

This paper examines the decision points over the course often years of development of an institutional repository. Specifically, the focus is on the impact and influence from the open-source community, the needs of the local institution, the role that team dynamics plays, and the chosen platform. Frequently, the discussion revolves around the technology stack and its limitations and capabilities. Inherently, any technology will have several features and limitations, and these are important in determining a solution that will work for your institution. However, the people running the system and developing the software, and their enthusiasm to continue work within the existing software environment in order to provide features for your campus and the larger open-source community, will play a bigger role than the technical platform. These lenses are analyzed through three points in time: the initial roll out of our institutional repository, our long-term running and maintenance, and eventual new development and why we made the decisions we made at each of those points in time.