At the Digital Collections and Archives (DCA) at Tufts University we have designed, built, and integrated our archival collection management system and repository’s administrative interface to facilitate ingesting archival objects into our Fedora based repository. This 24x7 session briefly explores the assumptions and functional requirements we have used to guide this development work. The DCA’s unique position as an archives that is one of the key stakeholders and users of the Tufts institutional repository has enabled us to meet this integration challenge. The session describes how the integration of our archival collection management system and our repository relies on the ability to flexibly move metadata from one system to another. and A lightning talk given at the Open Repositories conference in 2015 held in Indianapolis described thus
A panel presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus and Partnerships for shared repositories offer the promise of repository services at a decreased cost due to shared infrastructure and staff. In practice, reduced costs for shared repositories often require tradeoffs in security or access for the shared system. Staff working in a shared system may be geographically distributed or may work for different institutions with different priorities and reporting lines. Effective use of shared services requires thoughtful communication and tools that help maintain consistency and prevent conflicts when multiple people work in the same system. In this panel, shared repository service managers for multisite Islandora installations and a Hydra partnership will discuss methods for distributing system access and communicating with staff who work at our parent organizations, partner institutions, and third-party vendors. Each panelist will discuss the methods used so that distributed staff can have the level of access necessary to use the repository’s unique functions, while also ensuring that widely distributed system access doesn’t result in data loss or system failures.
A presentation given at the Open Repositories conference in 2009. Part of the proposal reads and Repositories have proven themselves as powerful tools for managing digital content in many different contexts. But experience has also shown that there are real, practical limits in trying to extend a single repository solution to meet the manifold needs of most institutions for their full range of digital content and use cases. Relatively narrow and inflexible application front ends can be used to create single-purpose repository-powered solutions, but they do not lend themselves to being quickly and easily repurposed to meet variations in content type or user interactions. There is a clear business need for a flexible, reusable application framework that can support the rapid development of multiple systems tailored to distinct needs, but powered by a common underlying repository. Recognizing this common need, Stanford University, the University of Hull and the University of Virginia are collaborating on “Project Hydra”, a three-year effort to create an application and middleware framework that, in combination with an underlying Fedora repository, will create a reusable environment for running multifunction, multipurpose repository-powered solutions. This presentation will provide demonstrations of the work done to date, including of the prototype ETD application, as well as the set of content models and disseminators that the project has defined so far. The presentation will also present links to the project’s publicly accessible documentation and open source code, as well as solicit the constructive input from community members who may be interested in the project or its outcomes.