3. Afternoon agenda
3
» ….
» 13:00 - 14:30 Gathering requirements for a Discovery Service and defining an
initial set of use cases - DiscussionGroups
» 14:30 - 14:45 Tea/Coffee break
» 14:45 - 15:45 Reporting back and discussion
» 15:45 - 16:00 Wrap up and questions
4. Workshop Objectives
4
» Introduce the team
» Bring pilot HEIs and Data Centres together
» Communicate the project’s objectives and plan
» Gather requirements for a Discovery Service
» Define an initial set of use cases
5. Aims and Objectives
5
» Break into three groups
» Use requirements gathered in pilot workshop as initial set
› Are these still valid?
› What detail is missing
› What requirements are missing?
» Use cases/stories
› Define an initial set based on different perspectives of stakeholders
» Drink tea/coffee
» Report back and discuss
6. Use Cases – User Stories
6
» Simple narratives that focus specifically on an interchange or interoperability
step in a business process
» As defined inWikipedia a user story is “one or more sentences in the everyday or
business language of the end user or user of a system that captures what a user
does or needs to do as part of his or her job function. It captures the 'who', 'what'
and 'why' of a requirement in a simple, concise way, often limited in detail by what
can be hand-written on a small paper notecard.”
» A typical template for such user stories is:
› "As a <role>, I want <goal/desire> so that <benefit>“
» Iterative process, doesn’t have to be perfect, can be refined later
» What use cases, both for human and system interfaces, can be defined for a
Research Data Discovery Service?
» Volunteers to take ownership of use cases
7. Stakeholders
7
HEIs holding or developing research data
collections
Greater visibility and discoverability of data held in UK
universities.
Discipline-specific Data Centres Potential greater visibility and discoverability of data held by
data centres and promotion of cross-disciplinary reuse. A
Research Data discovery service would direct users to data
centres rather than take them away.
Institutional research data managers and research
support officers
Improved national coordination of metadata approach helps
these stakeholders; supporting universities in better meeting
funder requirements and promoting data assets.
Researchers and their representative bodies Greater visibility for research data; promotes easier association
of traditional publications and research data as called for by the
Royal Society and research funders.
Research Funders Better overview of data outputs from funded research, focus on
detailed information about research data is complementary to
existing research outputs/outcomes systems (Gateway to
Research, RCUK Research Outcomes System, etc); potential for
increased impact through data reuse.
Non-HE consumers of research data in for-profit
and non-profit enterprises
Greater discoverability of research data held in UK universities
and elsewhere, which may have use outside the HE sector.
International organisations, e.g. RDA A UK-wide Discovery Service and outputs from this work will be
of interest internationally as a potential solution in other
countries.
8. Groups
8
Group 1
Christopher Brown, Jisc
Laura Molloy, DCC
Michael Latham, University of Hull
Stuart Lewis, University of Edinburgh
Adrian Cox, University of Southampton
Katie Green, Archaeology Data Centre
David McElroy, University of East London
Group 2
Veerle van den Eynden, UK Data Archive
Catherine Grout, Jisc
Mick Eadie, University of Glasgow
Rachel Proudfoot, University of Leeds
Ian Bruno, Cambridge Crystallographic Data Centre
Michael Charno, Archaeology Data Centre
Carlos de Silva, UCA
Group 3
David Wilson, DCC
Alex Ball, DCC
John Kaye, Jisc
Paddy McCann, University of St Andrews
David Tomkins, University of Oxford
Tom Griffin (STFC), ISIS/ICAT
Jez Cope, Imperial College
Jim Halliday (STFC), Energy Data Centre
10. Find out more…
10
Christopher Brown
Senior Co-design Manager,
Jisc
christopher.brown@jisc.ac.uk
@chriscb
Except where otherwise noted, this
work is licensed under CC-BY-NC-ND