Ways to engage? language? (e.g. IT: 'business continuity', ITIL)

From wiki.dpconline.org
Revision as of 11:45, 31 July 2013 by BVanDerWerf (talk | contribs) (Created page with "For most repositories it is not the intention to become an IT delivery organisation. However many of the action related to digital preservation are executed by IT, either in-h...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

For most repositories it is not the intention to become an IT delivery organisation. However many of the action related to digital preservation are executed by IT, either in-house or outsourced or in the cloud. This implies that thinking in terms of IT governance frameworks (COBIT, TOGAF) or IT delivery frameworks (ITIL) and adopting language and terminology will promoted explicit and clear digital preservation requirement to IT delivery. [Rauber calls “the three major shifts” in the thinking about DP: “DP as capabilities and maturity evaluations: Another important shift we may see coming is a shift from DP being something happening in a data archive or repository setting, i.e. a designated institution or department handling "old" objects, and being audited on its performance via any set of audit and certfication routines to ensure proper preservation at the highest possible level. Rather, we may view DP as a set of capabilities that an institution has, as part of many other operational capabilities, and that are integrated with more routine processes. We are thus currently investigating opportunities of integrating DP in an eGovernance framework. Reference models such as TOGAF [17] and COBIT [8] provide a well-tested basis for designing and managing DP activities alongside other routine IT capabilities. It allows us to manage DP capabilities in the framework of IT governance, benefiting from the well-structured concepts and processes in this domain, defining drivers, constrains and controls [2].” [A. Rauber, 2012]]