\subsubsection{Production}

Production across CDRS projects is largely a technical function with programming staff working on open-source and locally developed applications to achieve a range of desired outcomes elicited from project partners. From the outset, CDRS staff and the \textit{Tremor} editor-in-chief wanted to put the journal on an open source publishing platform to ensure a measure of ongoing customization and flexibility. As is done on the majority of its other publishing projects, a CDRS Web developer was tasked by Project Management with the primary responsibility of setting up, developing, and maintaining the \textit{Tremor} codebase. None of center's projects employ a strictly 1:1 relationship between staff and codebase, however. Instead, CDRS developers work in a collaborative environment, submitting and merging code into common repositories, and the efforts of the senior application developer at CDRS were eventually brought in to the project for the purposes of increased development throughput, maintenance backup, and general problem-solving efficiency. 

Journal production, however, also includes a significant number of non-technical tasks related to the preparation, quality checking, and publication of original content (both text and multimedia on the journal Web site and elsewhere). Several staff involved in project management also assume production related duties—namely, the senior project manager and the project coordinator. Add to these the position of the production assistant (a versatile member of the staff who works across many of the center’s teams) and the digital repository assistant (who ensure \textit{Tremor} content is properly represented in Columbia’s digital research repository, Academic Commons)\footnote{See \href{http://bit.ly/TremorJournalInAC}{http://bit.ly/TremorJournalInAC} for all \textit{Tremor} content in Columbia's repository}.