Göttingen-CODATA RDM Symposium 2018

Abstracts are invited for the Göttingen-CODATA RDM Symposium 2018 on ‘The critical role of university RDM infrastructure in transforming data to knowledge’.  The symposium will take place in Göttingen from 18-20 March 2018: it is a collaboration between the University of Göttingen and CODATA and is intended as a precursor event to the RDA plenary meeting in Berlin on 21-23 March 2018.

Abstract submissions of should be made at: http://conference.codata.org/2018_Goettingen_RDM/submit/ - the deadline for submissions is Friday 22 December.

Prospective participants that do not already have an account on the CODATA Conference Platform will need to sign up and create an account here: http://conference.codata.org/author/register/

Topic of the Symposium: ‘The critical role of university RDM infrastructure in transforming data to knowledge’

All over the world universities and libraries have started the task of developing research data services. Ideally such initiatives aim to result in a complete service portfolio covering the entire research lifecycle: support in writing proposals and data management plans, repository infrastructures for the storage of data, support in publishing data, assignment of persistent identifiers, lecturing in data management, etc. This broad scope means that such services are often seen as requiring a joint effort from from university, library, IT centre, faculties and other stakeholders.

Nowhere in the world has such a complete support scenario been perfected. It is timely for actors in the various dimensions of such initiatives internationally to share their practical experiences, research and insights.

Please note the range of themes listed below and at http://conference.codata.org/conference/2018_Goettingen_RDM/symposium-themes/

Important Points About Abstract Submissions

  • Proposals for long papers should be 1200-2000 words.

  • Proposals for short papers should be 300-600 words.

  • When submitting a proposal the author should choose the session corresponding to the theme for which the abstract is intended.

  • The programme committee hopes to inform successful papers by mid-January 2018.

Key Dates

Deadline for abstracts: 22 December 2017

Announcement of accepted abstracts and outline programme: mid January 2018

Symposium: 18-20 March 2018

Structure of the Symposium

Sunday 18 March, icebreaker event and keynote in the evening 17.00-19.00

Monday 19 March, full day of symposium, 09.00-18.00

Tuesday 20 March, half day of symposium, 09.00-14.00

Symposium Themes

Proposals should be submitted against one of the following themes.  Depending on the theme, either a long paper, discussion of a number of dimensions, or a short paper focussing on a particular issue is invited.

  1. Solutions (long papers): Papers describing in detail the technical solutions and infrastructures provided.  Topics to be covered include, the philosophy behind the solutions and the functionality it provides.  The support through the research / research data lifecycle should be described.  How has RDM support been conceptualised and mapped against research activity / lifecycle and the compliance requirements for research projects?  Papers covering solutions that are a) at the planning stage; b) established with lessons to share, or c) pioneering new services that are more advanced and leading edge; are all in scope, but the level of maturity should be clearly indicated.  How can more services at different levels of maturity be assessed and compared?

  2. Strategy (long papers): How do you make the business case for the service and present this within the strategy of the university or research organisation?  What is the business model to sustain the service?  How do you define and measure success?  What strategies and policies are required to support the service?

  3. Structure, organisational (long papers): How is the service conceived, structured and organised in the university or research organisation?  What priorities were identified in terms of the institution's management of core research information?  What research areas were identified for priority RDM support and why?  What criteria for prioritisation were used?  Who is working on what?  What are the reporting relationships and divisions of labour between units?  How has coordination been ensured between library, IT services, research offices and or equivalents?  Are there different archetypes that are emerging in how the services are structured?  Is the scope of the service generic or subject specific?  Which part of the lifecycle are you addressing?  What is the context and rationale for decisions about the focus and the structure of the service?

  4. Success (short papers): How do you assess maturity and measure success?  What sort of maturity model is being used?  Where does the institution place its development and how?  What are the key criteria of success?  How were these determined?  How are indicators against them defined and what metrics are used?  How is maturity and progress presented within the institution?

  5. Skills and Support (short papers): What skills are you developing to deliver the service, what roles are required to deliver the service, what recruitment and what training is being given to service providers?  What advocacy and skills training for researchers is being provided and why?  How has the need and focus been determined?  What is the strategy?

  6. Stitch ’n’ Bitch / Steam, letting off… / Sticking Points / Success and its Shadow (short papers): Share challenges, frustrations, failures and its lessons.  This session will be conducted under THE Chatham House Rule https://www.chathamhouse.org/about/chatham-house-rule which will also apply to any subsequent publication and communication about this session.

  7. Sustainability (short papers): What business models are being developed?  How is the service being financed?  What budgetary considerations are at play, what revenue sources are being considered or drawn upon?  What has been the level of investment so far and what are the projected levels of investment?  How has the institution financed the investment in RDM support?  Is the institution considering any form of cost recovery from research grants or otherwise?  How does the institution plan to ensure the sustainability of the service and the long term stewardship of the data?

  8. Shared and Outsourced Services (short papers): What steps are being taken to share or outsource services?  How are networks of institutions working together?  What is being done ‘in house’ as opposed to outsourced?  What relationships with commercial providers and hosting services are emerging?  What opportunities are there to establish consortia around particular services, including Open Source solutions?  What are the potential benefits of shared services across institutions, regionally, nationally, internationally?  What would be the most beneficial areas for shared services?

  9. Service Points (short papers): What points of service are being established?  What divisions of labour between e.g. front-office and back office functions?  How are these service points defined?

  10. Service Level, Trust and FAIR (short papers): What consideration of ‘service level’ has been undertaken?  Is the institution considering any approach to certification of ‘trusted digital repositories’, CoreTrustSeal or its predecessors?  Is the institution assessing the FAIR-ness of data curated and if so how?  

  11. Champions and Engagement (short papers): How is the RDM service engaging with researchers and particular communities?  What role to champions and advocates play in this and how?  What has been the role of the PVC / vice-rector for research etc?  What other possible champions have been identified and how?  What lessons have been learnt from engagement with research groups, departments, projects…?