This page contains a Flash digital edition of a book.
44 | ARMA | VIEWPOINT


W: www.universitybusiness.co.uk | T: @UB_UK


"A lack of cost- effective information flow is a root cause of growing reporting burden on researchers and their institutions"


TOWARD A ‘STANDARDS STACK’ FOR INTEROPERABILITY


By David Baker, Executive Director, CASRAI and Board Member, EuroCRIS


Our common interoperability challenges are becoming a growing problem. The problem spans the entire research enterprise. It is not limited to research information management systems but also reaches scholarly communications systems. It also affects the ancillary systems we need to connect with (HR, finance, etc) to do our work. A lack of cost-effective information flow is a root cause of growing reporting burden on researchers and their institutions. It is also a root cause of a growing challenge for research funders as they try to use information to beter understand the results of their investments.


The most complete definition of interoperability is included in this article: htp://www.ariadne.ac.uk/ issue24/interoperability: “To be interoperable one should actively be engaged in the ongoing process of ensuring that the systems, procedures and culture of an organisation are managed in such a way as to maximise opportunities for exchange and re-use of information, whether internally or externally.”


Standards are the best solution. Standards (disambiguated below) are a way of solving our interoperability problems in the most cost-effective, open and sustainable manner available. Without standards in your national interoperability infrastructure you are forced to either all adopt the same software or root storage model or, alternatively, to write and maintain custom bilateral mappings between software instances. Neither approach (alone) is cost-effective, sustainable, or innovation-friendly (ie anti-monopoly). Standards come in different flavours. The traditional


concept of standards are the ‘formal’ flavour. These are developed in long cycles under the auspices of nationally accredited standards bodies. Formal standards development is best suited to subject mater that is highly stable and well-known and likely not to change very often. A relatively new (since the Eighties) flavour of


standards are the ‘consortial’ flavour. These standards are developed and set by a consortium of leading stakeholder organisations in a community; using stable but less-formal approaches. This alternate approach arose to fill a gap in formal standards development in cases where the subject mater requirements were still in flux and changing frequently. They are seen as a more flexible and rapid solution to standards-seting in a seting of dynamic change. No single standard is a complete solution. There


are different consortial/informal standards, some competing in the same space but most complementary and modular. In the research and scholarly information space in the UK there are at least three key standards initiatives that can play an important role and that are complementary and non-competing. euroCRIS and their CERIF standards for storage and exchange; ORCID and their standards for uniquely identifying persons and resolving IDs to research activity; CASRAI and their standard terminology and profiling platform. In a single ‘standards stack’ we therefore have the key ingredients needed for standards-based interoperability:


Agreement on how we define and contextualise our policy requirements for information (CASRAI) Agreement on how we identify people and link to their works (ORCID) Agreement on our storage and exchange technology (CERIF)


An integrated approach helps stabilise a national strategy on interoperability. While good value is still present while these standards organisations operate independently on their respective ‘pieces of the puzzle’ there could be greater efficiencies and returns-on-investment if the organisations formalised an ability to work together seamlessly in an integrated workflow on those projects that are ready to pilot a standards-based approach as the best solution to interoperability problems. UB


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74