{"id":2799,"date":"2025-12-18T13:25:01","date_gmt":"2025-12-18T12:25:01","guid":{"rendered":"https:\/\/fair2adapt-eosc.eu\/?p=2799"},"modified":"2025-12-18T13:35:25","modified_gmt":"2025-12-18T12:35:25","slug":"why-we-built-the-fair2adapt-helpdesk-before-writing-a-single-line-of-code","status":"publish","type":"post","link":"https:\/\/fair2adapt-eosc.eu\/index.php\/2025\/12\/18\/why-we-built-the-fair2adapt-helpdesk-before-writing-a-single-line-of-code\/","title":{"rendered":"Why We Built the FAIR2Adapt Helpdesk Before Writing a Single Line of Code"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Author: Anne Fouilloux, FAIR2Adapt coordinator, CTO at Lifewatch <\/em><\/p>

Co-Author: Christine Matauschek, FAIR2Adapt Task Lead, Researcher at Fresh Thoughts Consulting<\/em><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

When we started planning FAIR2Adapt, we knew user support couldn’t be an afterthought. This lesson came directly from our experience in a previous project, where we reached Month 20 and suddenly realised we needed to extend support to external users\u2014but had nothing formalised in place. That experience shaped our approach for FAIR2Adapt: establish the Helpdesk from the very beginning.<\/p>

But “early” isn’t just about timing\u2014it’s about mindset.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Starting Early Means Thinking Inclusively<\/h5>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Climate change adaptation is inherently multi-stakeholder. Our case studies involve data scientists, yes, but also urban planners, environmental agencies, policy advisors, and business analysts assessing climate risk. These users have fundamentally different needs, vocabularies, and entry points into our services. If you design user support with only technical users in mind, you end up with documentation full of API (Application Programming Interface) calls and code snippets\u2014valuable for some, but alienating for others. APIs exist to let software automatically access or exchange data with our services, which is why they matter mainly for technical users. By establishing the Helpdesk in Month 1, we gave ourselves the space to ask: Who are all our users, and how do they each need to be supported? This early reflection shapes everything: how we write documentation, what formats we offer, how we structure our FAQs, and how we train partners to respond to queries. A policy maker exploring how FAIR data can inform adaptation planning needs a different conversation than a developer integrating our APIs. Both are equally valid users of the Helpdesk.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Multiple Channels, Multiple Entry Points<\/h5>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The FAIR2Adapt Helpdesk operates through complementary channels:<\/p>

Email support<\/strong> for users who prefer direct communication or have questions that don’t fit neatly into a technical issue tracker. This is often the more natural entry point for stakeholders from policy, planning, or business backgrounds.<\/p>

GitHub Issues<\/strong> for technical queries, bug reports, and feature requests\u2014but also as a transparent, searchable archive where answers to common questions become accessible to everyone.<\/p>

Documentation in multiple formats:<\/strong> Not everyone learns by reading code. We’re building resources that include conceptual overviews, workflow diagrams, and practical guides written in accessible language alongside the technical tutorials and Jupyter notebooks.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Why GitHub for the Technical Layer?<\/h5>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

For the technical dimension of our support, GitHub remains central. Using tools like Jupyter Book, we can create interactive, rendered pages that walk users through real code examples. Technical staff who need to provide support can directly contribute and iterate without dependencies on other work packages. And for expert users who want to engage more actively\u2014opening issues, suggesting improvements, contributing examples\u2014GitHub provides a collaborative space where the Helpdesk grows with its community.<\/p>

But GitHub is one layer of the Helpdesk, not the whole story.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Placing the Helpdesk in WP5: A Strategic Choice<\/h5>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

We deliberately placed the Helpdesk in WP5 (Community Support and Engagement) rather than in a purely technical work package. In previous projects where helpdesk functions sat within technical WPs, they tended to serve technical users well but became disconnected from broader community engagement. By situating the Helpdesk alongside FAIR capacity building, user requirements gathering, and co-design activities, we ensure it’s integrated into how we engage with all our stakeholders. The Helpdesk isn’t just about answering technical questions\u2014it’s about accompanying diverse communities on their journey to exploit FAIR2Adapt services in ways that make sense for their work. A city resilience officer exploring how FAIRified climate data could inform urban planning should feel just as welcome reaching out as a data engineer implementing RO-Crate profiles.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
The Right Mindset from the Start<\/h5>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Perhaps the most important benefit of establishing the Helpdesk early is cultural. When user support is baked in from Month 1, the entire consortium develops a different relationship with the communities we serve. We document as we build. We ask “who needs this, and how?” before finalising designs. We recognise that a service isn’t truly useful until users can actually use it. This mindset extends beyond the Helpdesk itself\u2014it influences how we design our APIs, structure our training materials, and communicate about FAIR2Adapt more broadly.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Get Involved<\/h5>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The Helpdesk is live and ready to support you\u2014whoever you are and however you work. Visit us at https:\/\/fair2adapt.github.io\/fair2adapt-helpdesk\/<\/a> to explore our resources, or simply reach out with your questions.<\/p>

Whether you’re a researcher working on Arctic environmental monitoring, a developer building climate services, or a policy advisor exploring how FAIR data can strengthen adaptation planning\u2014we’re here to help, and to learn from your experience along the way.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

Author: Anne Fouilloux, FAIR2Adapt coordinator, CTO at Lifewatch Co-Author: Christine Matauschek, FAIR2Adapt Task Lead, Researcher at Fresh Thoughts Consulting When we started planning FAIR2Adapt, we knew user support couldn’t be an afterthought. This lesson came directly from our experience in a previous project, where we reached Month 20 and suddenly realised we needed to extend […]<\/p>\n","protected":false},"author":1,"featured_media":2800,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-2799","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news-events"],"_links":{"self":[{"href":"https:\/\/fair2adapt-eosc.eu\/index.php\/wp-json\/wp\/v2\/posts\/2799","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fair2adapt-eosc.eu\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fair2adapt-eosc.eu\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fair2adapt-eosc.eu\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fair2adapt-eosc.eu\/index.php\/wp-json\/wp\/v2\/comments?post=2799"}],"version-history":[{"count":4,"href":"https:\/\/fair2adapt-eosc.eu\/index.php\/wp-json\/wp\/v2\/posts\/2799\/revisions"}],"predecessor-version":[{"id":2804,"href":"https:\/\/fair2adapt-eosc.eu\/index.php\/wp-json\/wp\/v2\/posts\/2799\/revisions\/2804"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fair2adapt-eosc.eu\/index.php\/wp-json\/wp\/v2\/media\/2800"}],"wp:attachment":[{"href":"https:\/\/fair2adapt-eosc.eu\/index.php\/wp-json\/wp\/v2\/media?parent=2799"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fair2adapt-eosc.eu\/index.php\/wp-json\/wp\/v2\/categories?post=2799"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fair2adapt-eosc.eu\/index.php\/wp-json\/wp\/v2\/tags?post=2799"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}