Overview and details of the sessions of this conference. Please select a date or location to show only sessions at that day or location. Please select a single session for detailed view (with abstracts and downloads if available).
Florida State University, United States of America
The Florida State University (FSU) Faculty Senate unanimously adopted a campus-wide Open Access policy in February 2016. Although the policy technically requires faculty to deposit their articles in FSU’s institutional repository, very few faculty voluntarily comply with this requirement. To increase our faculty deposit rate, our repository team created utilities and workflows to identify and solicit article manuscripts from faculty at scale. This presentation will provide an overview of these utilities and workflows, as well as the strategies we have pursued to operationalize them. Particular attention will be given to gathering content, staffing requirements, rights issues, workflow challenges and limitations, faculty response, sustainability, and reproducibility for other institutions.
9:30am - 10:00am
Integrating Two Institutional Repositories within One University System
Jodi Carlson Grebinoski1, Valerie Collins2
1University of Minnesota Duluth; 2Univeristy of Minnesota Twin Cities
The University of Minnesota’s five system campuses have, over time, implemented and administered independent repository solutions. The University of Minnesota Twin Cities campus began their repository program, the University Digital Conservancy (UDC), in 2007. The University of Minnesota Duluth (UMD) campus started a repository program, known as d-Commons, in 2010. Both repositories ran on DSpace instances, and were administered locally. In 2015, in the face of rising costs of maintaining and running the repositories separately, the two repositories decided to merge in order to streamline resources. As both repositories ran on DSpace, and were campus repositories within the same larger university system, d-Commons and the UDC made a good fit for integration. The two-year effort to integrate two separate DSpace instances under the umbrella of one repository was completed in 2017, resulting in a multi-campus institutional repository.
In order to streamline processes and allocation of resources, integrating two DSpace instances proved to be an effective choice for the University of Minnesota. Both repositories maintain separate identities and local control, while operating under shared policies. This presentation will discuss the process and results of integration, including technical considerations, policy implications, and managing stakeholder expectations.
10:00am - 10:30am
Transforming a local digital repository into a community project
Pavel Straňák, Jozef Misutka
LINDAT/CLARIN, Charles University, Czech Republic
In 2009, a decision was made in the LINDAT/CLARIN project (i.e. Czech CLARIN European Research Infrastructure) to use DSpace repository as the base for its digital repository. The software stack was branded as lindat-dspace project maintained by the LINDAT/CLARIN development team and substantially customized to meet the sustainable CLARIN digital repository requirements (http://hdl.handle.net/11372/DOC-78) including a working licensing model, persistent identifiers, protocols supporting automated processing, semantically unambiguous metadata models and support for international academic community. The lindat-dspace has become popular among CLARIN member countries with installations in 9 different member states. However, with popularity comes also responsibility to keep the project secure and up-to-date with a reasonable support. These seemingly simple tasks can become rather problematic when the underlying project undergoes radical changes with each major release and core customizations have to be integrated again. Therefore, the local project has been changed to a global one called clarin-dspace with the aim to move towards a community driven project. Along the way, we identified multiple obvious and some not so obvious aspects that had significant impacts on the phase we were currently in. In our talk, we summarize the history and the lessons learned when transforming to a community project.