Designing workflows for quality assured metadata - PowerPoint PPT Presentation

1 / 13
About This Presentation
Title:

Designing workflows for quality assured metadata

Description:

Designing workflows for. quality assured metadata. Jane Barton & John Robertson ... arises from issues identified by early implementers ... – PowerPoint PPT presentation

Number of Views:23
Avg rating:3.0/5.0
Slides: 14
Provided by: janeb97
Category:

less

Transcript and Presenter's Notes

Title: Designing workflows for quality assured metadata


1
Designing workflows forquality assured metadata
  • Jane Barton John RobertsonCentre for Digital
    Library ResearchUniversity of Strathclyde

2
Overview
  • The Metadata Workflow Investigation
  • Metadata quality
  • Metadata workflow
  • Factors influencing quality and workflow
  • Issues to resolve
  • The way forward?

3
The Metadata Workflow Investigation
  • supporting study for X4L and FAIR programmes
  • focus on metadata creation within UK LORs and IRs
  • arises from issues identified by early
    implementers
  • Primary aim is to develop a good understanding
    of
  • the factors which influence both metadata
    qualityand the workflow used to create it
  • the context within which recommendationsare to
    be made

4
Metadata quality why bother?
  • Quality is defined by its absence
  • errors, omissions and ambiguities
  • recall and precision
  • Metadata quality is essential for
  • functionality
  • interoperability
  • participation in aggregated services
  • Enthusiasm, expectation and critical mass

5
Defining metadata quality
  • Quality is fitness for purpose
  • Aspects of metadata quality
  • structure, semantics and syntax
  • metadata metrics
  • Metadata requirements
  • local needs
  • community-level requirements
  • cost-benefit and compromise

6
Managing metadata quality
  • Metadata quality in practice
  • contextual factors determine actual quality
  • immediate and long-term priorities
  • The quality cycle
  • Quality assurance quality by design
  • elements, records, repositories, aggregations
  • tools and techniques
  • embedding quality assurance in metadatacreation
    processes - workflow

7
Metadata workflow why bother?
  • Metadata for libraries
  • well-defined purpose, stable context
  • workflow embedded and tightly controlled
  • community-wide approach to optimise quality
  • Metadata for repositories
  • poorly defined and diverse purpose, evolving
    context
  • workflow distributed, collaborative or both
  • potential of community-wide approach notfully
    exploited

8
Designing metadata workflow
  • Determine purpose of metadata
  • Determine level of quality required
  • Determine level of quality that can be achieved
  • Design and implement workflow
  • Refine workflow
  • Review
  • Opportunities for refinement
  • arise from both local and wider context
  • produce both direct and indirectimprovements in
    quality

9
Factors influencing metadata quality
  • What is the repository for, locally and within
    the wider context? Does this give rise to any
    conflicts?
  • What type of objects will the repository contain?
    How will they be used? And by whom?
  • What functionality is required locally? How will
    it be interfaced? What entry points will be used?
  • What is required for interoperability? Are
    requirements formal or informal, direct or
    indirect?
  • Will access restrictions be imposed locally?And
    in the wider context?
  • Will metadata be meaningful withinaggregations
    of various kinds?

10
Factors influencing workflow design
  • What resources are available locally? Who will be
    involved? What skills do they have?
  • How can these resources be used to best effect?
  • Are resources available within the wider
    community? Does their use require compromises to
    be made, and if so, is it worth it?
  • Are resources sufficient to produce the required
    metadata quality, and if not, what are the
    priorities?
  • What level of commitment exists locallyand in
    the wider community?

11
A typology of factors
  • Repository-level factors
  • Does the repository have a subject specialism? Is
    it required to interoperate with the local VLE?
  • Object-level factors
  • Can objects be repurposed? Is their use
    restricted?
  • Metadata-level factors
  • Does participation in the wider community impose
    specific requirements? Is training available?
  • Local factors
  • Is there a strategic commitment to the repository?

12
Issues to resolve
  • Repository-level issues
  • need a better understanding of what an individual
    repository is for, both locally and as part of a
    wider system of repositories and services
  • Object-level issues
  • need a better understanding of how objects are
    created, used, repurposed, managed
  • Metadata-level issues
  • need to integrate and optimise metadatacreation,
    enhancement and QA processes throughout the wider
    system

13
The way forward?
Write a Comment
User Comments (0)
About PowerShow.com