Presenting the document of the Data Versioning Working Group, and considering the next steps, potential use cases, and need for a maintenance group.
Collaborative session notes: https://docs.google.com/document/d/1BrV1OHNXm4aW-5tKwfXXeVFeQDRp0rJ938AYTrc6Z48/edit?usp=sharing
Presentation of the Data Versioning WG report and recommendations
Use case presentations
Discussion on the next steps - do we need more use cases? Apply for “maintenance mode” or not? Should this work be continued with another WG?
Data curators, Data facility managers / data policy managers. They should read the prepared document and consider how it matches their own needs.
The group has worked on the principles of data versioning practices. The group is identifying the kinds of methods that have been adopted (or became ad hoc practices) and is generating the background theoretical framework needed for versioning considerations. The group seeks to answer the questions, “What is a new version?” and “How should it be documented?”, etc.
The group has prepared a report, based on documented use cases, and developed a set of basic considerations for data versioning:
Management: Recognise identification and tracking of data revisions and data releases as an important component of data management
Establish a procedure and policy for consistent management of data revisions and releases.
Identification: Be clear about which dataset is to be identified
Identify data revisions, consider issuing a new persistent identifier per revision and release
Communication: Communicate the significance of the change to the designated user community of this dataset.
Concepts such as Semantic Versioning describe the significance of a version change
Provenance: Track changes and record provenance information between revisions
Provenance information describes the changes that have been made to each newer revision. Display provenance information, attribution and credit on landing pages of each publically released dataset.
Citation: Cite a specific data release
For each released dataset, have a clear recommendation, including a release number, on how to cite a dataset.
P8 Denver (Sept 2016): BoF on Data Versioning
P9 Barcelona (April 2017): Constituting the Data Versioning IG
P10 Montreal (Sept 2017): Data Versioning IG
P11 Berlin (March 2018): Data Versioning WG first meeting
P12 Gaborone (Nov 2018): Data Versioning WG working meeting
P13 Philadelphia (April 2019): Data Versioning WG draft report and recommendations
P14 Helsinki (Sept 2019): Data Versioning WG final report and recommendations, TAB adoption.
Working Group Page: https://rd-alliance.org/groups/data-versioning-wg
Case Statement: https://rd-alliance.org/group/data-versioning-wg/case-statement/data-ver...
Data Versioning Use Cases: https://rd-alliance.org/data-versioning-use-cases
Mapping of use cases to W3C Data Exchange WG use cases: https://docs.google.com/document/d/1lI5HyRnHMLkdDpRMg82HCnyzvxxmb_oymJ4T...
Draft of white paper on data versioning: https://docs.google.com/document/d/1bINRNA2PtumnnNWoPnvzMoCYci6S5HjcX8LG...
REMOTE ACCESS INSTRUCTION
Please join my meeting from your computer, tablet or smartphone.
You can also dial in using your phone.
United States: +1 (571) 317-3117
Access Code: 198-036-325
More phone numbers
Australia: +61 2 8355 1038
Austria: +43 7 2081 5337
Belgium: +32 28 93 7002
Canada: +1 (647) 497-9373
Denmark: +45 32 72 03 69
Finland: +358 972 52 2971
France: +33 170 950 590
Germany: +49 693 8098 999
Ireland: +353 15 360 756
Italy: +39 0 230 57 81 80
Netherlands: +31 207 941 375
New Zealand: +64 9 913 2226
Norway: +47 21 93 37 37
Spain: +34 932 75 1230
Sweden: +46 853 527 818
Switzerland: +41 225 4599 60
United Kingdom: +44 20 3713 5011
New to GoToMeeting? Get the app now and be ready when your first meeting starts:
- 1100 reads