Balancing Community and Local Needs

Releasing, Maintaining, and Rearchitecting the Institutional Repository




This paper examines the decision points over the course of ten years for developing 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.


Adam Wiggins, “The Twelve-Factor App,” accessed September 2021,

Akond Rahman, Chris Parnin, and Laurie Williams, “The Seven Sins: Security Smells in Infrastructure as Code Scripts,” 2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE) (2019): 164–75,

“Browse-Everything,” GitHub, accessed 09/05/2021,

Christopher Mendez et al., “Open Source Barriers to Entry, Revisited: A Sociotechnical Perspective,” in Proceedings of the 40th International Conference on Software Engineering (May 2018): 1004–15,

Dai Clegg and Richard Barker, CASE Method Fast-Track: A RAD Approach (Reading: Addison-Wesley, 1994).

Fredrick P. Brooks Jr., The Mythical Man-Month: Essays on Software Engineering (Reading, Mass.: Addison-Wesley Pub. Co., 1982)

Helen Hockx‐Yu, “Digital Preservation in the Context of Institutional Repositories,” Program 40, no. 3 (2006): 232–43,

Jennifer Marlow and Laura Dabbish, “Activity Traces and Signals in Software Developer Recruitment and Hiring,” in CSCW ’13: Proceedings (ACM, 2013): 145–56,

Joel Spolsky, “Things You Should Never Do Part I,” Joel On Software, April 6, 2000,

Lindsay Larson and Leslie A. DeChurch, “Leading Teams in the Digital Age: Four Perspectives on Technology and What They Mean for Leading Teams,” Leadership Quarterly 31, no. 1 (2020),

“Publisher Data Availability Policies Index,” CHORUS, October 8, 2021,

“Questioning Authority,” GitHub, accessed September 2021,

Raymond Okon, Ebele Leticia Eleberi, and Kanayo Kizito Uka, “A Web Based Digital Repository for Scholarly Publication,” Journal of Software Engineering and Applications 13, no. 4 (2020),

“Registry of Open Access Repository Mandates and Policies,” ROARMAP,

Research Data Access and Preservation, “Browse Data Sharing Requirements by Federal Agency,” SPARC, September 29, 2020,

Sophie Huilian Qiu et al., “Going Farther Together: The Impact of Social Capital on Sustained Participation in Open Source,” 2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE) (2019): 688–99,

Stephen Abrams, John Kunze, and David Loy, “An Emergent Micro-Services Approach to Digital Curation Infrastructure,” The International Journal of Digital Curation 5, no. 1 (2010): 172–86,

“Student Enrollment – Fall 2021,” The Pennsylvania State University Data Digest 2021,




How to Cite

Coughlin, D. (2022). Balancing Community and Local Needs: Releasing, Maintaining, and Rearchitecting the Institutional Repository. Information Technology and Libraries, 41(1).