1 / 8

Using DAF as a data scoping tool for institutional repositories

Learn about the Data Audit Framework (DAF) project and how it can enable universities and colleges to assess their data collections, policies, and practices for curation and preservation. Discover the scope of the DAF development project, pilot implementation projects, methodology, and the themes addressed in DAF surveys.

teaguec
Download Presentation

Using DAF as a data scoping tool for institutional repositories

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using DAF as a data scoping tool for institutional repositories Sarah Jones DCC, University of Glasgow s.jones@hatii.arts.gla.ac.uk

  2. Background to DAF project “JISC should develop a Data Audit Framework to enable all universities and colleges to carry out an audit of departmental data collections, awareness, policies and practice for data curation and preservation” Liz Lyon, Dealing with Data: Roles, Rights, Responsibilities and Relationships, (2007)

  3. Scope of work • DAF Development (DAFD) Project (University of Glasgow; King’s College London; University of Edinburgh; UKOLN, University of Bath) • Four pilot implementation projects • University of Edinburgh • King’s College London • Imperial College London • University College London

  4. The methodology http://www.data-audit.eu/DAF_Methodology.pdf

  5. Themes addressed in DAF surveys • Data: type / format, volume, description, creator, funder • Creation: policy, naming, versioning, metadata & documentation • Management: storage, backup, roles and responsibilities, planning • Access: restrictions, rights, security, frequency, ease of retrieval, publish • Sharing:collaborators, requirements to share, methods, concerns • Preservation: selection / retention, repository services, obsolescence • Gaps / needs: services, advice, support, infrastructure

  6. Subject areas of DAF pilots • DAFD test cases: GeoSciences; Archaeology; Mechanical Engineering; Humanities • University of Edinburgh Physiology; Divinity; History; Brain Imaging; Astronomy • University College London Archaeology; Scandinavian Studies; Physics & Astronomy; Life & Medical Sciences • Imperial College London Chemical Engineering; Physics; Business School • King’s College London Geography; Psychiatry; Environmental Research; Biomedical And Health Sciences • DataShare examples Cardiac group; Dept of International Development; Social Sciences

  7. Generalised findings • Lots of data were created • Few policies for data creation, storage and management • Researchers unsure where to begin and were often unaware of available support • Often no place of deposit or funds for preservation Pilot implementation findings http://www.data-audit.eu/findings.html IJDC paperhttp://www.ijdc.net/ijdc/article/view/91/109

  8. Workshop on next steps for DAF • Many of the pilots found the actual process of gathering information on data management was more valuable than the asset register. The DAF approach was felt to be useful for defining requirements to improve data management. (JISC funded DMI projects) • A suggestion was made to enhance DAF with practical examples / guidance from the pilot studies. (Implementation Guide) • Align the DAF process with other data management planning tools. (IDMP project between AIDA, DAF, DRAMBORA, LIFE)

More Related