Upload
others
View
5
Download
0
Embed Size (px)
Citation preview
4
§ The Research Data Alliance (RDA) is a new organization § Interoperability § specific, short-term efforts § Accelerate sharing § Bottom up § Inspired by IETF
§ Addresses the need to do something § Data is an issue (also in the humanities) § In 5-10 years it will be unmanageable § Open new questions to research
RDA: Research Data Alliance
5
§ Still establishing structure / definitions § Major structure in place
§ Working groups § Interest groups § Support
§ Secretariat § Council § TAB § Funders body
§ Two regular Plenary meetings per year. § Regional bodies RDA/US, RDA/EUROPE
§ Support RDA activities locally
Steady state of RDA
6 Initial Group of Funders (iGoF)
§ The Research Data Alliance is being brought into existence by an initial three research funding organizations: § The Australian Commonwealth Government (ANDS). § The European Commission (RDA/EUROPE) § National Science Foundation (US)
7 Organizational Framework
RDA Strategy: Council
Technical Advisory Board
(TAB)
Administrative: Secretariat
Organizational Advisory Group
(OAG)
RDAMem
bership
Community Impact: Working and Interest Groups
8
§ Increase membership through the rd-alliance.org website and forums
§ Create a pipeline of impact-oriented deliverables through the development and backing of RDA Working Groups
§ Foster RDA Plenary events as a gathering place for the community
Developing the RDA Community
9
§ Populate the initial Council, Technical Advisory Board, Organizational Advisory Board, Secretariat
§ Work with active community members to take on leadership roles and responsibilities
Populating RDA Bodies
11
§ Working Groups § Interest Groups § Current Groups § Collaboration § Nine Updates § Upcoming Events
Overview
12
§ Case Statement § Concrete problem § 12-18 month timeline § Requirements wrt coverage of stakeholders and
geography
Working Groups
13
§ Charter § Short statement
§ Loosely defined goal § Not always the case, requirements less strict
§ May produce working groups § Usually the case, with some exeptions § E.g. Engagement
Interest Groups
14
§ PID Information Types § Data Type Registries § Metadata Standards Directory § Data Foundation and Terminology § Practical Policy § Data Categories and Codes
Current Groups: WGs: Recognised & Endorsed (6)
15
§ Metadata Interest Group § RDA-CODATA Working Group on Legal Interoperability of
Research Data § The Engagement Group § Certification of Digital Repositories § Preservation e-Infrastructure Interest Group § Agricultural Data Interoperability § Structural Biology § Digital Practices in History and Ethnography § Toxicogenomics Interoperability § Brokering Interest Group § The Long Tail of Research Data § Research Data Provenance Interest Group
Current Groups: IGs: Recognized & Endorsed (12)
16
§ Community Capability Model § Working Group on Data Citation: Making Data Citable § Wheat Data Interoperability
Current Groups: WGs: Upcoming
17
§ UPC Code for Data § Publishing Data Interest Group
§ linked to the WDS Data Publication WG
§ Defining Urban Data Exchange for Science § Marine Data Harmonization § Data in Context § Economic Models & Infrastructures for Federated
Materials Data Management § Big Data Analytics
Current Groups: IGs: Upcoming
18
§ Many more IGs than WGs § WG paradigm is seen as restrictive § WG paradigm is restrictive § Does mean getting work done
§ Many exciting developments § Overall groups are very active and productive
§ A handful are not doing so well
§ 6 official WGs § 12 official IGs
Current Groups
19
§ Bottom-up Collaboration § Motivate § Synchronize outcomes § Provide active feedback
§ Several groups: § Practical Policy § Metadata (WG and IG) § PID Inforation Types § DFT § Data Type Registries
§ Meeting every 4-6 weeks § Group reports § Small deliverables
§ Core data exchange
Collaboration
20
§ Data Citation: Making Dynamic Data Citable WG § Many meetings to get going. § Currently revising Case Statement § First prototype (for databases) presented at DATA2013
§ MASDIR - Metadata Standards Directory WG § Currently revising the charter § Developing Metadata IG § Meetings at Plenary and CAMP-4-DATA
§ PID Information Types WG § Gathering use-cases
§ Expectations and Issues § Creating technical use case documents
§ Will present these at Plenary2 § Started Architecture and API
Nine Updates
21
§ Practical Policy WG § Developing multiple testbeds
§ evaluation of common data management policies § testing of interoperability mechanisms
§ First Policy: automated data set replication § DataVerse, dCache, e-IRODS, IRODS
§ Agricultural Data Interoperability IG § Re-evaluating charter at Plenary2 § Spawning Wheat Interoperability WG
§ Engagement IG § Provides a forum for discussion and implementation § Session at ESIP meeting
Nine Updates
22
§ Metadata IG § Old MD IG is now MASDIR
§ concerned primarily with a directory of metadata 'standards’ § Metadata IG is wide-ranging and long-standing § acts as an umbrella
§ Structural Biology IG § Initial results of enquiry show need § Eukaryotic, complexes, problems combining software/data
§ Toxicogenomics Interoperability IG § conducting a survey
§ community data needs and limitations § identify an approach to improve toxicogenomics
§ data sharing, access and analysis
Nine Updates
23
§ Datacite: Washington § EUDAT Conference: Rome, 28-30/10
§ RDA Track § SSH tackle the Big Data Challenge Workshop
§ RDA/E Science Workshop: Munich, February § Plenary 3: Dublin
Upcoming Events
24
§ Individual § Become a member (register) § Engage on the online forum § Join WGs/IGs § Start a WG or IG
§ Support RDA as a nation/region/Industry § Encourage individual participation (travel grant, time grant, etc.) § Become a funding member.
Participation
25
Thank You
§ Information: rd-alliance.org
§ Questions, comments: [email protected]
§ Registration and Forum: on website
27
§ Collects, Validates, Publishes capability profiles § framework for describing and evaluating data-intensive
research across domains
Community Capability Model WG
28
§ Citing subsets of data § From Databases § Many problems to address
§ Versioning § Ordering § Etc.
Data Citation WG
29
§ Basic, Abstract data model § Reference data terminology § Synchronize between communities
§ I.e. people can use the same concepts. § Better communication
Data Foundation and Terminology WG
30
§ Create a Type Registry infrastructure § Technical description of the data type § Tools that can be used on the data § Etc.
Data Type Registries WG
31
§ Three goals: 1. Prototype wiki listing metadata standards relevant to
scientific data 2. consensus on a minimum metadata set supporting the
exchange and interoperability of scientific data resources
3. Establish a resource of re-used terms and blocks of terms
Metadata Standards WG
32
§ What kind of specific information types should be associated with a PID? § Checksum § Author § Etc.
§ Structural elements (e.g. collections) § Define a profile-system for PID information types § Definition of a common API for PID systems
PID Information Types WG
33
§ Collect Practical Policy in use in data centers. § Organize these policies § Find commonalities § Produce “starter kits” of policy
Practical Policy WG
34
§ Domain IG on agricultural data § (All data related to achriculture)
§ Will work closely with CIARD § Make sure data is not lost
Agricultural Data Interoperability IG
35
§ Deals with different standards (NOSQL, multi-dimentional tables, graph databases)
§ What works and what doesn’t?
Big Data Analytics
36
§ Contextual metadata § Contextual information in the metadata § Needs understanding to be useful
Data in Context IG
38
§ Together with CODATA § 4 case studies of legal interoperability
§ Geoscience § Biodiversity § Social sciences § Humanities
§ Core principles and guidelines § For making legal interoperability happen
§ Promote legal interoperability
Legal Interoperability
39
§ Management of marine data § A lot of (diverse) data
§ Population of species § DTP § Chemical analysis § Satellite images § Etc.
Marine Data Harmonization
40
§ E-Infrastructure services § Preserve § Interoperability § Service Providers
Preservation e-Infrastructure IG
41
§ Certification is needed for trust § Benefits § Awareness § Maintenance of certification § With collaborators from ISO, DIN, DSA
Repository Audit and Certification