Tuesday, 30 September 2008

iPres 2008 Building Trust

Tyler Walters of GIT comparing trust in the banking system with trust in repositories. The upheavals in banking currently show how easily trust can be upset, and how hard it is to regain once lost. Further desk study on trust; 3 major sources (see paper for references). Useful idea of trust antecedents: what comes before an event that helps you trust, subjectively. Trust that endures is more likely to continue if there’s a breach of trust. Trust is a relationship between people, more than institutions. Trust development: engage, listen, frame issues, envision options, commit. Looks like a paper that’s well worth reading; it’s always seemed to me that trust is about much more than certifying against checklists.

Susanne Dobratz from Humboldt University on quality management and trust, work done in the nestor programme. Should we have separate standards and certification mechanisms (as in the CCSDS Repository Audit and Certification work), or build on existing security and quality management standards? Working though a project to assess applicability of these latter standards (ISO 9000, ISO 27000 etc). Did an analysis and a survey with a questionnaire to 53 persons, got responses from 18 (most responded but were not really able to answer the questions). DINI guidelines the most popular, formal standards little used. Standards mostly used as guidelines rather than formally (makes sense to me, having used ISO security standards that way). 94% knew their designated community, but only 53% have analysed the needs of their designated community. 61% were unsure whether a separate standard for trusted repositories was important; similar proportion unsure whether they would go through any certification process. As a result, I think they are interested in creating a smaller, more informal quality standard along the lines of DINI etc.

Sarah Jones on developing a toolkit for a Data Audit Framework: to help institutions to determine what data are held, where they are located and how they are being managed. 4 pilot sites including Edinburgh and Imperial already under way, UCL and KCL in planning. Detailed workflow has been developed as a self-audit tool. Four phases in the audit process, the second being identifying and classifying the assets; looks like major work. Turns out the pilots are related to department level rather than institutions, which makes sense knowing academic attitudes to “the Centre”! I did hear from one institution that it was difficult getting responses in some cases. Simple online tool provided. DAF to be launched tomorrow (1 October) at the British Academy, together with DRAMBORA toolkit.

Henk Harmsen from DANS on the Data Seal of Approval.. Since 2005, DANS has been looking after data in the social sciences and humanities, in the Netherlands. Aim was make archives DANS-proof, ie to follow acceptable standards; initially not sure how to implement. Looked at existing documents, aim to be complementary to all these requirements. Go for guidelines and overview rather than certifying and many details, trust rather than control. So Seal of Approval almost more a Seal of Awareness. Funding agencies beginning to require the Seal. Data producer responsible for quality of research data, repository responsible for storage, management and availability of data, and the data consumer responsible for quality of use. 17 guidelines, 3 for producers, 11 for repositories, 3 for consumers! Requirement 13 says technical infrastructure must explicitly support tasks and functions from OAIS… not necessarily implemented the same way, but using that vocabulary. How to control? Certification takes a long time, major standards, elaborate agencies, high cost.. Trust does need some support, though. First step: Data Seal of Approval Assessment, then other instruments like DRAMBORA etc. Looks like a nice, low impact, light touch first step towards building trust.


Post a Comment

Please note that this blog has a Creative Commons Attribution licence, and that by posting a comment you agree to your comment being published under this licence. You must be registered to comment, but I'm turning off moderation as an experiment.