Integration and implementation


This section is concerned with the practicalities of embedding; with the processes of integrating the repository with other institutional systems – in the widest sense, including human systems – and with a broader ecosystem of publishing, search and discovery. The section will also deal with implementation of the integration strategy in terms of buy or build, working with developers, selecting vendors and managing relationships with them, and risk management.

Of course, such decisions and processes are likely to be undertaken by project management structures extending considerably beyond the repository or library team (for example, embracing IT services and the research office) but prior experience indicates that the repository/library team should and often has had a central involvement. They have practical knowledge of issues such as metadata management and an understanding of how users find and use information resources.

The drivers, benefits and barriers and making the business case for embedding are dealt with elsewhere in the Guide.

The scenarios which began the guide suggest a wide range of possible contexts for this integration activity, though they are far from exhaustive. Embedding is often taking the form of linking the repository with other institutional systems for recording research information (funding, projects, principal investigator etc), either directly or via a Current Research Information System (CRIS). However, embedding is centrally about integration with researchers’ day to day practices, however that is achieved. It may or may not entail a complex technical integration project but it will certainly imply working more closely with other areas of the university, and much more directly with researchers themselves. Above all, embedding a repository is not merely possible at many different types of institution, it is essential.

No comments yet.

Leave a Reply