RDA Europe – Atlas of Knowledge Project Coordinator: Stefan Heinzel Executive Director: Peter Wittenburg Project Manager: Kathrin Beck Administrative Manager: Andreas Schott Raphael Ritz Max Planck Computing & Data Facility (MPCDF) CC BY-SA 4.0
T4.1/2 – Advice, Testing, Adoption Advice to RDA and outside Simple helpdesk Atlas of Knowledge knowledge base about RDA groups and data practices dynamic mindmaps as guidance and new solution for improved guidance need a team that writes and edits Collaboration projects (15 k€ max) 6 projects (first round) 8 projects (second round)
T4.1/2 – European Support Team (EST) Advice to RDA and outside on the RDA machinery as well as key outcomes Simple helpdesk Now: rdaeu-helpdesk@rda-e3.eu Future: together with e-Infrastructures? European Support Team (EST; initially called Senior/Junior Team; SJT) Leif Laaksonen, Anni Jacobsen/Riina Salmivalli (CSC); Herman Stehower (until July 2016), Kathrin Beck, Giuseppe Di Bernardo, Peter Wittenburg (MPG); Francoise Genova (CNRS); Sandra Collins, Kevin Long (NLI); Natalie Harrower, Rebecca Grant (RIA); Dimitris Gavrillis, Panagiota Koltisa (Athena RC); Simon Lambert (STFC); Odile Hologne (INRA); Wolfram Horstmann (LIBER) Initial training of juniors in 2015 (M4.1)
T4.1 – Atlas of Knowledge – Dynamic Maps Initially referred to as Knowledge Base
T4.1 – Atlas of Knowledge – Scope Topical organization / templates RDA output descriptions RDA output flyers Adoption examples Service description Other documents of relevance Well coordinated with the landscape analysis of RDA’s TAB At the moment this is a standalone application at http://core.cloud.dcu.gr/rda_aok/
Atlas of Knowledge – Demo User facing: http://core.cloud.dcu.gr/rda_aok/ Admin backend: http://core.cloud.dcu.gr/rda_aok/admin Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
www.rd-alliance.org - @resdatall Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
www.rd-alliance.org - @resdatall Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
www.rd-alliance.org - @resdatall Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
www.rd-alliance.org - @resdatall Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
www.rd-alliance.org - @resdatall Admin back end Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
www.rd-alliance.org - @resdatall Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
www.rd-alliance.org - @resdatall Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
Edit interface: Mindmap Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
www.rd-alliance.org - @resdatall Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
www.rd-alliance.org - @resdatall Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
And now you: templates for contributions Content to be provided on setting up a new group (WG/IG) Content to be provided when a new output becomes available Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
www.rd-alliance.org - @resdatall For New Groups One short paragraph summarising the group’s motivation, goals and intentions. A few words (maximum 12) that will appear on the link from topic to group on hovering over the link—one level beyond what can be deduced from the name of the group alone. Allocation of group to existing topic(s) - optional Brussels, May 4, 2017 www.rd-alliance.org - @resdatall
A new Output becomes available A set of bullet points, one per output, up to one paragraph each. The first (possibly the only) sentence of each bullet point should state what the output is (a standard, a registry, a demonstrator, a white paper, …) and its purpose or utility with respect to the work of the group (unless this is obvious from the nature of the output). A direct link to the output should preferably be provided. Brussels, May 4, 2017 www.rd-alliance.org - @resdatall