<?xml version="1.0" encoding="UTF-8"?>
<rss  xmlns:atom="http://www.w3.org/2005/Atom" 
      xmlns:media="http://search.yahoo.com/mrss/" 
      xmlns:content="http://purl.org/rss/1.0/modules/content/" 
      xmlns:dc="http://purl.org/dc/elements/1.1/" 
      version="2.0">
<channel>
<title>Research Support Handbook</title>
<link>https://rdm-os-cs-vu.github.io/open-handbook/blog.html</link>
<atom:link href="https://rdm-os-cs-vu.github.io/open-handbook/blog.xml" rel="self" type="application/rss+xml"/>
<description>A place for all things open research at VU Amsterdam.</description>
<generator>quarto-1.9.37</generator>
<lastBuildDate>Thu, 19 Mar 2026 00:00:00 GMT</lastBuildDate>
<item>
  <title>Restructuring and redesign</title>
  <dc:creator>Jolien Scholten</dc:creator>
  <dc:creator>Peter Vos</dc:creator>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2026-03-19tools-redesign.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>In the past few weeks, we did two major updates in the VU CS Department RDM and Open Science Handbook. The tool documentation has been restructured and renamed. The website as a whole has been redesigned.</p>
<section id="tool-documentation" class="level2">
<h2 class="anchored" data-anchor-id="tool-documentation">Tool documentation</h2>
<p>This is what we updated regarding the tool documentation:</p>
<ul>
<li>What we previously called ‘Manuals’ is now called <a href="../tools.html">‘Tools’</a>.</li>
<li>The topic pages about tools (basic information about the tools we provide/support) are moved to the ‘Tools’ section, so that basic information and more elaborate documentation (if available) now sit together.</li>
<li>As a result of the previous action, the ‘Tools’ category in the topics has disappeared. Note that we created aliases for the URLs, meaning that the old tool topic URLs will refer to the home page of the relevant tool in the Tools section.</li>
<li>We restructured the basic information that was in the old Topic pages into separate pages to make it easier to navigate: description of the tool, costs and getting access, support and contact, quick start.</li>
<li>Some tools have an additional documentation section for more elaborate manuals, tips and how-to’s.</li>
<li>The OSF documentation was moved from Guides to the new Tools section.</li>
<li>The tools are no longer displayed as tiles on the overview page, but are now presented as a list. They can be filtered by category (type of tool).</li>
</ul>
<p>If you’re interested in the specifics of this update, you can read all documentation in <a href="https://github.com/ubvu/open-handbook/issues/717" target="_blank">Issue #717</a>.</p>
<p><strong>N.B. 1</strong>: If you are working on a fork of the VU CS Department RDM and Open Science Handbook, make sure to sync it, so that these changes will be updated in your fork as well. <strong>N.B. 2</strong>: If you refer to documentation about the tools we support (e.g.&nbsp;Yoda, Research Drive, ADA, Qualtrics) from another website (e.g.&nbsp;a faculty page on the VU website), make sure to check your URLs. If you need help with finding a page’s new location on the website, let us know.</p>
<p>These updates are done in the context of the Tools Documentation Project. We’re aiming to have comprehensive documentation for all research-related tools we provide/support, as much as possible along the same structure, by the end of the year. If you have questions about this project, you can send an email to j2.scholten@vu.nl.</p>
</section>
<section id="redesign" class="level2">
<h2 class="anchored" data-anchor-id="redesign">Redesign</h2>
<p><a href="https://im-studio.eu/" target="_blank">IM Studio</a> created a new design for the VU CS Department RDM and Open Science Handbook and this was implemented by Peter Vos. The new design involves a restructured homepage, new colours for topics, guides and manuals, and icons for prominent pages like calendar, trainings and questions. We have changed the overview pages of topics, guides and tools as well, so that they are presented in the same structure.</p>
<p>We will do some finetuning in the coming weeks. Let us know if you’re missing something.</p>


</section>

 ]]></description>
  <category>Handbook</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2026-03-19tools-redesign.html</guid>
  <pubDate>Thu, 19 Mar 2026 00:00:00 GMT</pubDate>
</item>
<item>
  <title>Seventh Handbook Hackathon</title>
  <dc:creator>Diógenes Cruz de Arcelino</dc:creator>
  <dc:creator>Kirianne Goossen</dc:creator>
  <dc:creator>Sergio Gutierrez Maury</dc:creator>
  <dc:creator>Elisa Rodenburg</dc:creator>
  <dc:creator>Jolien Scholten</dc:creator>
  <dc:creator>Peter Vos</dc:creator>
  <dc:creator>Tycho Hofstra</dc:creator>
  <dc:creator>Jessica Hrudey</dc:creator>
  <dc:creator>Tim Veken</dc:creator>
  <dc:creator>Janna Toebosch</dc:creator>
  <dc:creator>Sreenithya Avadakkam</dc:creator>
  <dc:creator>Wiebe Timmers</dc:creator>
  <dc:creator>Abeer Pervaiz</dc:creator>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2025-11-27hackathon.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>On November 27, 2025, all authors participated in the seventh hackathon for the Research Support Handbook. For this hackathon, we focused on <strong>Consolidating content and adding new content</strong>.</p>
<section id="overview-of-results" class="level2">
<h2 class="anchored" data-anchor-id="overview-of-results">Overview of results</h2>
<p>We updated the information about Pure and about data and software registration in Pure (link to LibGuide manuals instead of PDFs, information about Elsevier no longer supporting DataMonitor).</p>
<p>We created two practical pages related to the RDM Support Desk:</p>
<ul>
<li>General information about the RDM Support Desk</li>
<li>Landing page for requesting access to datasets</li>
</ul>
<p>Regarding videos in the VU CS Department RDM and Open Science Handbook: We stored relevant videos in Panopto and embedded them in our website from there, replacing the YouTube videos. This helps us maintain all video material in a central place and another advantage is that we don’t get suggestions for other videos once a video has ended, as on YouTube.</p>
<p>We expanded the Research Software topic by referring to related information in the VU CS Department RDM and Open Science Handbook.</p>
<p>We continued working on the topic de-identifying data, but this is still in progress.</p>
<p>A few updates have been done in tools documentation for Yoda, ADA and SciStor before, during and after the hackathon. We have improved navigation in the tools section as well.</p>
<p>Finally, a <a href="https://zenodo.org/records/17937465" target="_blank">new release of the Handbook</a> has been created on Zenodo.</p>
</section>
<section id="hackathon-issues-and-pull-requests" class="level2">
<h2 class="anchored" data-anchor-id="hackathon-issues-and-pull-requests">Hackathon Issues and Pull Requests</h2>
<ul>
<li>Data and software registration updates: <a href="https://github.com/ubvu/open-handbook/issues/250" target="_blank">Issue #250</a>, <a href="https://github.com/ubvu/open-handbook/pull/621" target="_blank">PR #621</a> and <a href="https://github.com/ubvu/open-handbook/pull/623" target="_blank">PR #623</a>; <a href="https://github.com/ubvu/open-handbook/pull/627/changes" target="_blank">PR #627</a> for updates in the general information about Pure. Note that the information about Pure has been transferred from topics to tools see <a href="https://github.com/ubvu/open-handbook/issues/675" target="_blank">Issue #675</a> and see <a href="https://github.com/ubvu/open-handbook/pull/678" target="_blank">PR #678</a>.</li>
<li>RDM Support Desk: <a href="https://github.com/ubvu/open-handbook/issues/588" target="_blank">Issue #588</a> and <a href="https://github.com/ubvu/open-handbook/pull/610" target="_blank">PR #610</a> for the information page and <a href="https://github.com/ubvu/open-handbook/issues/589" target="_blank">Issue #589</a> and <a href="https://github.com/ubvu/open-handbook/pull/631" target="_blank">PR #631</a> for the landing page with information about requesting access to datasets.</li>
<li>Research software information: <a href="https://github.com/ubvu/open-handbook/issues/410" target="_blank">Issue #410</a> and <a href="https://github.com/ubvu/open-handbook/pull/624" target="_blank">PR #624</a>.</li>
<li>Topic de-identifying data: <a href="https://github.com/ubvu/open-handbook/issues/492" target="_blank">Issue #492</a></li>
</ul>


</section>

 ]]></description>
  <category>Handbook</category>
  <category>Hackathon</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2025-11-27hackathon.html</guid>
  <pubDate>Thu, 27 Nov 2025 00:00:00 GMT</pubDate>
</item>
<item>
  <title>New Manuals section in the Handbook</title>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2025-07-28manuals.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>Last week we added a new section to the VU CS Department RDM and Open Science Handbook: <a href="../tools.html">Manuals</a>. Manuals are short pages describing how to accomplish specific tasks in a <a href="../topics.html#category=Tools">Tool</a> and should be easily understood by individuals with varying levels of technical knowledge. Manuals on the handbook will be written in the form of a how-to. The aim is to provide guidance for specific tasks “How do I?”. From the basic: “How do I log in” to the more in-depth “How do I use CUDA on ADA”.</p>
<p>We have started by migrating the <a href="../tools/yoda/index.html">manuals on using Yoda</a>, from their old spot on yoda.vu.nl. Next step will be migrating the <a href="../tools/ada/index.html">ADA HPC</a> manuals from <a href="https://ada-hpc.readthedocs.io/en/latest/" target="_blank">readthedocs</a>.</p>
<p>By consolidating all user manuals on the VU CS Department RDM and Open Science Handbook we hope to increase the findability of both the manuals and the rest of the VU CS Department RDM and Open Science Handbook.</p>
<section id="maintaining-the-manuals" class="level2">
<h2 class="anchored" data-anchor-id="maintaining-the-manuals">Maintaining the manuals</h2>
<p>Even more than Topic and Guide pages, Manuals have a short shelf life. Hence, they must be checked regularly. Each manual will have one or two support staff responsible for keeping it up to date. To make sure enough time is set aside to work on the manuals we plan to have two update moments per year, perhaps in the form of a Hackathon.</p>


</section>

 ]]></description>
  <category>Handbook</category>
  <category>Yoda</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2025-07-28manuals.html</guid>
  <pubDate>Mon, 28 Jul 2025 00:00:00 GMT</pubDate>
</item>
<item>
  <title>Sixth Handbook Hackathon</title>
  <dc:creator>Emily Barabas</dc:creator>
  <dc:creator>Diógenes Cruz de Arcelino</dc:creator>
  <dc:creator>Kirianne Goossen</dc:creator>
  <dc:creator>Charlie Greene</dc:creator>
  <dc:creator>Sergio Gutierrez Maury</dc:creator>
  <dc:creator>Sam Heijnen</dc:creator>
  <dc:creator>Marcel Ras</dc:creator>
  <dc:creator>Elisa Rodenburg</dc:creator>
  <dc:creator>Jolien Scholten</dc:creator>
  <dc:creator>Dimitri Unger</dc:creator>
  <dc:creator>Peter Vos</dc:creator>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2025-07-24hackathon.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>On July 24, 2025, all authors participated in the sixth hackathon for the Research Support Handbook. For this hackathon, we focused on <strong>adding and updating topics</strong>.</p>
<section id="overview-of-results" class="level2">
<h2 class="anchored" data-anchor-id="overview-of-results">Overview of results</h2>
<p>New topics that we have added during or in the days after the Hackathon:</p>
<ul>
<li>ITvO</li>
<li>Pure</li>
<li>CARE Principles</li>
<li>Software Archiving</li>
<li>Software Publishing</li>
<li>OSF</li>
</ul>
<p>We have started on the following topics, but these still need some work before they can be published:</p>
<ul>
<li>RDM tools overview (to replace the <a href="https://vu.nl/en/about-vu/divisions/university-library/more-about/rdm-tools" target="_blank">current one on the VU website</a>)</li>
<li>De-identifying data: Pseudonymisation and Anonymisation</li>
<li>Informed consent forms (content will be discussed with the privacy experts)</li>
</ul>
<p>The following topics have been updated:</p>
<ul>
<li>DMP: we moved the instructions for selecting the VU DMP template to the guide <a href="../guides/plan-and-design.html">How can you set up research data management from the start?</a></li>
</ul>
<p>We worked on some guides as well:</p>
<ul>
<li>We updated the guide <a href="../guides/data-lifecycle.html">What research data services and support are available for VU researchers?</a></li>
<li>We transferred all information related to OSF from the VU OSF Wiki to the Handbook, resulting in a topic (see above) and a guide <a href="../tools/osf/quick_start.html">How can you use Open Science Framework (OSF) in your research project?</a></li>
<li>We updated the guide <a href="../guides/plan-and-design.html">How can you set up research data management from the start?</a>, where we included the instructions for selecting the VU DMP template</li>
</ul>
<p>In addition, we introduced a new type of page: Manuals (a big thanks to Peter, who put a lot of effort in preparing this 🙏). A user manual provides guidance and instructions to users of a tool. User manuals are created to be easily understood by individuals with varying levels of technical knowledge. It can be assumed that most of the tools will already have their own manuals on the suppliers website. We will link to those as much as possible, we don’t want to duplicate information. If you’re interested, you can read more in <a href="https://github.com/ubvu/open-handbook/issues/416" target="_blank">Issue #416</a>. The Yoda manuals have now been included in the Handbook (the website yoda.vu.nl will be phased out). Manuals on the handbook will be written in the form of a how-to, the aim is to provide guidance for specific tasks “How do I?”. From the basic: “How do I log in” to the more in-depth “How do I use CUDA on ADA”.</p>
<p>Finally, we also worked on contributing guidelines and categorised the blog posts, introducing a new type of blog post by ITvO:</p>
<ul>
<li>Instructions for using VSCode to contribute</li>
<li>Updated instructions for rendering the VU CS Department RDM and Open Science Handbook locally</li>
<li>Introduced Blog categories and ITvO Blog</li>
</ul>
</section>
<section id="hackathon-issues-and-pull-requests" class="level2">
<h2 class="anchored" data-anchor-id="hackathon-issues-and-pull-requests">Hackathon Issues and Pull Requests</h2>
<ul>
<li>(Yoda) manuals: <a href="https://github.com/ubvu/open-handbook/issues/416" target="_blank">Issue #416</a> and <a href="https://github.com/ubvu/open-handbook/pull/484" target="_blank">PR #484</a></li>
<li>Information about ITvO: <a href="https://github.com/ubvu/open-handbook/issues/344" target="_blank">Issue #344</a> and <a href="https://github.com/ubvu/open-handbook/pull/516" target="_blank">PR #516</a></li>
<li>Software Archiving: <a href="https://github.com/ubvu/open-handbook/issues/354" target="_blank">Issue #354</a> and <a href="https://github.com/ubvu/open-handbook/pull/500" target="_blank">PR #500</a></li>
<li>Software Publishing: <a href="https://github.com/ubvu/open-handbook/issues/354" target="_blank">Issue #354</a> and <a href="https://github.com/ubvu/open-handbook/pull/501" target="_blank">PR #501</a></li>
<li>OSF: <a href="https://github.com/ubvu/open-handbook/issues/100" target="_blank">Issue #100</a> and <a href="https://github.com/ubvu/open-handbook/pull/538" target="_blank">PR #538</a> (topic) and <a href="https://github.com/ubvu/open-handbook/pull/541" target="_blank">PR #541</a> (guide)</li>
<li>CARE Principles: <a href="https://github.com/ubvu/open-handbook/issues/448" target="_blank">Issue #448</a> and <a href="https://github.com/ubvu/open-handbook/pull/503" target="_blank">PR #503</a></li>
<li>What research data services and support are available for VU researchers? <a href="https://github.com/ubvu/open-handbook/pull/530" target="_blank">PR #530</a></li>
<li>Pure: <a href="https://github.com/ubvu/open-handbook/issues/482" target="_blank">Issue #482</a> and <a href="https://github.com/ubvu/open-handbook/pull/497" target="_blank">PR #497</a> and <a href="https://github.com/ubvu/open-handbook/pull/537" target="_blank">#PR 537</a></li>
<li>How can you set up research data management from the start?: <a href="https://github.com/ubvu/open-handbook/pull/524" target="_blank">PR #524</a></li>
<li>DMP: <a href="https://github.com/ubvu/open-handbook/pull/525" target="_blank">PR #525</a></li>
<li>Using VSCode to contribute: <a href="https://github.com/ubvu/open-handbook/pull/525" target="_blank">PR #509</a></li>
<li>Rendering Handbook locally: <a href="https://github.com/ubvu/open-handbook/pull/463" target="_blank">PR #463</a></li>
<li>Introducing Blog categories and ITvO Blog <a href="https://github.com/ubvu/open-handbook/pull/533" target="_blank">PR #533</a></li>
</ul>
</section>
<section id="ai-generated-texts" class="level2">
<h2 class="anchored" data-anchor-id="ai-generated-texts">AI-generated texts</h2>
<p>In preparation for this hackathon, we had some texts for new topics drafted by Claude LLM, as part of a trial to explore AI-assisted content creation for the handbook. The idea was that it is easier for people to review existing content than creating something from scratch. During the hackathon, most people seemed to have a preference for writing text themselves. It is more fun, and part of the content created by Claude LLM was not useful. So for now, we think we will keep writing our own texts.</p>


</section>

 ]]></description>
  <category>Handbook</category>
  <category>Hackathon</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2025-07-24hackathon.html</guid>
  <pubDate>Thu, 24 Jul 2025 00:00:00 GMT</pubDate>
</item>
<item>
  <title>ITvO blog</title>
  <dc:creator>Sergio Gutierrez</dc:creator>
  <dc:creator>Peter Vos</dc:creator>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2025-07-29itvoblog.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<section id="first-itvo-blog" class="level2">
<h2 class="anchored" data-anchor-id="first-itvo-blog">First ITvO Blog</h2>
<p>From now on the <a href="../topics/itvo.html">ITvO (IT for Research)</a> team will be using the Handbook Blog for sharing news, updates, and important announcements related to <a href="../tools/scicloud/index.html">SciCloud</a>, <a href="../tools/ada/index.html">ADA HPC</a>, <a href="../tools/scistor/index.html">SciStor</a>, and other services provided by ITvO. Here you will find information about new features, scheduled maintenance, service improvements. Stay tuned for the latest developments and insights from the ITvO team.</p>


</section>

 ]]></description>
  <category>IT for Research</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2025-07-29itvoblog.html</guid>
  <pubDate>Thu, 24 Jul 2025 00:00:00 GMT</pubDate>
</item>
<item>
  <title>How to embed handbook pages using iframes</title>
  <dc:creator>Chris Hartgerink</dc:creator>
  <dc:creator>Elisa Rodenburg</dc:creator>
  <dc:creator>Jessica Hrudey</dc:creator>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2025-05-15embed-iframe.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>If you want to reuse content from the VU CS Department RDM and Open Science Handbook, you can do so using an HTML <code>iframe</code>. This post will help you through the steps to successfully embed a handbook page on a website you administer.</p>
<section id="selecting-what-to-embed" class="level2">
<h2 class="anchored" data-anchor-id="selecting-what-to-embed">Selecting what to embed</h2>
<p>Before we can embed a page, we need to select what to embed.</p>
<p>Each page in the VU CS Department RDM and Open Science Handbook has sections, which can be used as anchors for embedding the content. This ensures that the right page shows up displaying the right content.</p>
<p>For example, if you are interested in the <a href="../tools/dataversenl/index.html">DataverseNL</a> page, you can select any of the headings as an anchor. Here are the steps involved:</p>
<ol type="1">
<li>Identify the specific anchor to embed at (for example, “How to request access”)</li>
<li>Click the link icon next to the anchor</li>
</ol>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://rdm-os-cs-vu.github.io/open-handbook/public/Screenshot 2025-05-08 at 10.49.51.png" class="img-fluid figure-img"></p>
<figcaption>Screenshot of the anchor and the link icon highlighted</figcaption>
</figure>
</div>
<ol start="3" type="1">
<li>Go to your browser’s navigation bar and copy the new link (<code>https://rdm.vu.nl/topics/dataversenl.html#how-to-request-access</code>)</li>
</ol>
<p>This link is all you need to anchor the embedding itself, which we explain in the section How to embed.</p>
</section>
<section id="how-to-embed" class="level2">
<h2 class="anchored" data-anchor-id="how-to-embed">How to embed</h2>
<p>After you identified the page and possible anchor to embed, we can now move on to actually embedding it. Embedding the pages themselves is supported by all major browsers using the HTML element <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/iframe" target="_blank"><code>iframe</code></a>.</p>
<p>Concretely, you can use the following example code for the link we found in Selecting what to embed.</p>
<div class="code-copy-outer-scaffold"><div class="sourceCode" id="cb1" style="background: #f1f3f5;"><pre class="sourceCode html code-with-copy"><code class="sourceCode html"><span id="cb1-1"><span class="dt" style="color: #AD0000;
background-color: null;
font-style: inherit;">&lt;</span><span class="kw" style="color: #003B4F;
background-color: null;
font-weight: bold;
font-style: inherit;">iframe</span></span>
<span id="cb1-2"><span class="ot" style="color: #003B4F;
background-color: null;
font-style: inherit;">    src</span><span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">=</span><span class="st" style="color: #20794D;
background-color: null;
font-style: inherit;">"https://rdm.vu.nl/topics/dataversenl.html#how-to-request-access"</span></span>
<span id="cb1-3"><span class="ot" style="color: #003B4F;
background-color: null;
font-style: inherit;">    title</span><span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">=</span><span class="st" style="color: #20794D;
background-color: null;
font-style: inherit;">"How to request access to DataverseNL"</span></span>
<span id="cb1-4"><span class="ot" style="color: #003B4F;
background-color: null;
font-style: inherit;">    width</span><span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">=</span><span class="st" style="color: #20794D;
background-color: null;
font-style: inherit;">"100%"</span></span>
<span id="cb1-5"><span class="ot" style="color: #003B4F;
background-color: null;
font-style: inherit;">    height</span><span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">=</span><span class="st" style="color: #20794D;
background-color: null;
font-style: inherit;">"300px"</span></span>
<span id="cb1-6"><span class="ot" style="color: #003B4F;
background-color: null;
font-style: inherit;">    loading</span><span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">=</span><span class="st" style="color: #20794D;
background-color: null;
font-style: inherit;">lazy</span></span>
<span id="cb1-7"><span class="ot" style="color: #003B4F;
background-color: null;
font-style: inherit;">    style</span><span class="op" style="color: #5E5E5E;
background-color: null;
font-style: inherit;">=</span><span class="st" style="color: #20794D;
background-color: null;
font-style: inherit;">"border: solid 1px #0080c9"</span><span class="dt" style="color: #AD0000;
background-color: null;
font-style: inherit;">&gt;</span></span>
<span id="cb1-8"><span class="dt" style="color: #AD0000;
background-color: null;
font-style: inherit;">&lt;/</span><span class="kw" style="color: #003B4F;
background-color: null;
font-weight: bold;
font-style: inherit;">iframe</span><span class="dt" style="color: #AD0000;
background-color: null;
font-style: inherit;">&gt;</span></span></code></pre></div></div>
<p>You can switch out the link, title, and other attributes to your liking – we include some styling options here to get started. You can copy-paste this into any handbook page directly or into any HTML editor:</p>
<iframe src="https://rdm.vu.nl/topics/dataversenl.html#how-to-request-access" title="How to request access to DataverseNL" width="100%" height="300px" loading="lazy" style="border: solid 1px #0080c9; overflow: hidden;">
</iframe>
<p>You can find the <a href="https://github.com/ubvu/open-handbook/blob/main/blog/2025-05-15embed-iframe.qmd#L43" target="_blank">detailed code on how this page embeds the content, on GitHub</a>, from line 43.</p>
<p>Thanks for reading and good luck creating your own embeds of the VU CS Department RDM and Open Science Handbook across VU Amsterdam pages 😊 If you have questions or it does not work and you don’t understand why, please <a href="rdm@vu.nl">contact the RDM Support Desk</a> and one of the editors will try to help you.</p>


</section>

 ]]></description>
  <category>Handbook</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2025-05-15embed-iframe.html</guid>
  <pubDate>Mon, 19 May 2025 00:00:00 GMT</pubDate>
</item>
<item>
  <title>Fifth Handbook Hackathon</title>
  <dc:creator>Lena Karvovskaya</dc:creator>
  <dc:creator>Jolien Scholten</dc:creator>
  <dc:creator>Kostas Vilkelis</dc:creator>
  <dc:creator>Tycho Hofstra</dc:creator>
  <dc:creator>Irene Martorelli</dc:creator>
  <dc:creator>Peter Vos</dc:creator>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-11-28hackathon.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>On November 28, 2024, all authors participated in the fifth hackathon for the Research Support Handbook. For this hackathon, we focused on adding new content and consolidating requests.</p>
<p>We had a large number of contributions related to tools. The handbook now has information about Research Cloud, SciCloud and Yoda. These were long-standing issues and it is really nice that they turned into topics.</p>
<p>Irene helped us to revise the metadata topic.</p>
<p>Tycho is working on a page for ORCID, the <a href="vu.nl/orcid">ORCID Libguide page</a> will be adjusted to redirect to the handbook.</p>
<p>Lena was working on a data backup topic, trying to make it generic and applicable to multiple tools.</p>
<p>We had a discussion of an overview page. New colleagues also within support miss an overview of the services available. There are many pages that give some ideas: <a href="https://vu.nl/en/about-vu/divisions/university-library/more-about/rdm-tools" target="_blank">the RDS portal on Tools</a>, the <a href="https://deploy-preview-274--ubvu-open-handbook.netlify.app/guides/data-lifecycle" target="_blank">guide on available services</a> and <a href="https://vu.nl/en/research/portal/research-impact-support-portal" target="_blank">RISP</a> - but all these overviews have diverse struggles so we are still looking for a good way of doing it.</p>
<p>ITvO colleagues noticed that they miss an official VU page which gives a summary of what ITvO is and does.</p>
<p>Question that came up: how to add new contributors? Do they need access rights? Do they work with forks or branches?</p>
<section id="hackathon-issues" class="level2">
<h2 class="anchored" data-anchor-id="hackathon-issues">Hackathon Issues</h2>
<p><a href="https://github.com/ubvu/open-handbook/issues/275" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/275</a></p>
</section>
<section id="hackathon-pull-requests" class="level2">
<h2 class="anchored" data-anchor-id="hackathon-pull-requests">Hackathon Pull Requests</h2>
<p><a href="https://github.com/ubvu/open-handbook/pull/277" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/277</a></p>
<p><a href="https://github.com/ubvu/open-handbook/pull/276" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/276</a></p>
<p><a href="https://github.com/ubvu/open-handbook/pull/140" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/140</a></p>
<p><a href="https://github.com/ubvu/open-handbook/pull/273" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/273</a></p>
<p>Merged <a href="https://github.com/ubvu/open-handbook/pull/270#pullrequestreview-2467652120" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/270#pullrequestreview-2467652120</a></p>


</section>

 ]]></description>
  <category>Handbook</category>
  <category>Hackathon</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-11-28hackathon.html</guid>
  <pubDate>Thu, 28 Nov 2024 00:00:00 GMT</pubDate>
</item>
<item>
  <title>Fourth Handbook Hackathon</title>
  <dc:creator>Chris Hartgerink</dc:creator>
  <dc:creator>Lena Karvovskaya</dc:creator>
  <dc:creator>Jolien Scholten</dc:creator>
  <dc:creator>Tycho Hofstra</dc:creator>
  <dc:creator>Elisa Rodenburg</dc:creator>
  <dc:creator>Stephanie van de Sandt</dc:creator>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-11-01hackathon.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>On October 30th, 2024, all authors participated in the fourth hackathon for the Research Support Handbook. Since the <a href="https://rdm.vu.nl/blog/2024-09-30hackathon.html" target="_blank">third hackathon</a>, we migrated to <code>rdm.vu.nl</code>, which is a huge milestone! 🎉</p>
<p>For the fourth hackathon, we focused on tying up loose ends that we accumulated. The migration means we are now in a stable state, yet there is always more work to be done. During this hackathon, we focused on picking up stale discussions, reviewing open pull requests, and generally closing issues that we took too long to revisit.</p>
<p>We considered how (un)balanced the various <a href="https://rdm.vu.nl/topics.html" target="_blank">Topics</a> had gotten, because we want readers to be able to form consistent expectations. We observed that some topics are related to tools, others to concepts. Some topics are concise, whereas others are lengthy.</p>
<p>One breakout group focused on creating templates for both kinds of topics, resulting in an initial structure that will make it easier to start new topics in the future. Specifically we propose the following template structure for tools (for example, Qualtrics, HPC, DMPonline):</p>
<ul>
<li>What is it?</li>
<li>What can it be used for?</li>
<li>How to request access</li>
<li>Are there costs involved</li>
<li>Getting started (with screenshot)</li>
<li>How does it work/more detailed instructions</li>
<li>Contact</li>
</ul>
<p>And the following structure for concepts (for example, DMP, data citation, data storage):</p>
<ul>
<li>What is it</li>
<li>Examples</li>
<li>Tools/services/resources related to concept provided by VU</li>
<li>How does this help you in your research?</li>
</ul>
<p>We will follow up with a new hackathon in late november.</p>
<section id="issues-worked-on" class="level2">
<h2 class="anchored" data-anchor-id="issues-worked-on">Issues worked on</h2>
<p><a href="https://github.com/ubvu/open-handbook/issues/232" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/232</a></p>
<p><a href="https://github.com/ubvu/open-handbook/issues/233" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/233</a></p>
</section>
<section id="pull-requests-worked-on" class="level2">
<h2 class="anchored" data-anchor-id="pull-requests-worked-on">Pull Requests worked on</h2>
<p><a href="https://github.com/ubvu/open-handbook/pull/229" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/229</a></p>
<p><a href="https://github.com/ubvu/open-handbook/pull/231" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/231</a></p>
<p><a href="https://github.com/ubvu/open-handbook/pull/234" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/234</a></p>
<p><a href="https://github.com/ubvu/open-handbook/pull/235" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/235</a></p>
<p><a href="https://github.com/ubvu/open-handbook/pull/236" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/236</a></p>
<p><a href="https://github.com/ubvu/open-handbook/pull/237" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/237</a></p>


</section>

 ]]></description>
  <category>Handbook</category>
  <category>Hackathon</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-11-01hackathon.html</guid>
  <pubDate>Fri, 01 Nov 2024 00:00:00 GMT</pubDate>
</item>
<item>
  <title>Why was rdm.vu.nl down for ten hours?</title>
  <dc:creator>Chris Hartgerink</dc:creator>
  <dc:creator>Lena Karvovskaya</dc:creator>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-10-22post-mortem.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>On Friday October 18th 2024, we experienced around ten hours of downtime on the <code>rdm.vu.nl</code> website. The downtime started around 10AM after merging changes to the handbook and was resolved the same day, by 8PM.<sup>1</sup></p>
<section id="root-cause" class="level2">
<h2 class="anchored" data-anchor-id="root-cause">Root cause</h2>
<p>The downtime started after merging changes to the handbook in commit <a href="https://github.com/ubvu/open-handbook/commit/669b06528731f95566d605d65b9c3a507f58bced" target="_blank">669b065</a>. These changes themselves, did not cause the downtime. The root cause was an incorrect configuration in the deployment of the webpage, which inadvertently removed the <code>rdm.vu.nl</code> domain name from the GitHub settings every time we made changes in the handbook and redeployed the website. This resulted in 404 errors that the page could not be found.</p>
<p>We first observed this issue on Thursday, one day prior to the downtime, in commit <a href="https://github.com/ubvu/open-handbook/commit/678ff8843dc018f76661b24ee25c64bff5c459df" target="_blank">678ff88</a>. We proposed a fix for this issue in <a href="https://github.com/ubvu/open-handbook/pull/220" target="_blank">#220</a>, before the downtime started.</p>
</section>
<section id="how-could-the-downtime-happen-if-the-fix-was-clear" class="level2">
<h2 class="anchored" data-anchor-id="how-could-the-downtime-happen-if-the-fix-was-clear">How could the downtime happen if the fix was clear?</h2>
<p>The fix for the domain specification was not merged in time for two reasons.</p>
<section id="reason-1" class="level3">
<h3 class="anchored" data-anchor-id="reason-1">Reason 1</h3>
<p>At this time, we require two reviews before merging changes to the handbook. The fix was proposed at 1.11PM on Thursday, and did not receive the required reviews by the time the downtime happened (reason 1). However, this was a technical administration task and could have been merged immediately, as this supercedes regular review procedures.</p>
</section>
<section id="reason-2" class="level3">
<h3 class="anchored" data-anchor-id="reason-2">Reason 2</h3>
<p>The domain specification fix was not immediately merged to allow time to pass and ensure the fix was appropriate upon further reflection. This is because administrator <span class="citation" data-cites="chartgerink">(<strong>chartgerink?</strong>)</span> both proposed the fix and would also be the one to supercede the “two reviews” requirement. Due to travel, the administrator forgot about it in the morning, and only saw the messages about the downtime at 8PM. At that time, the fix was quickly merged and the downtime resolved.</p>
</section>
</section>
<section id="improvements" class="level2">
<h2 class="anchored" data-anchor-id="improvements">Improvements</h2>
<p>The domain configuration is corrected and the deployment ensures the domain name is re-added to the GitHub settings every time there are changes to the handbook. This is now automated, which ensures that the domain name will not be removed inadvertently when future changes are incorporated.</p>
<p>However, we also learned that critical administration fixes should not be left open for longer than is absolutely necessary. Here it was left open for longer than absolutely necessary due to travel, and a second administrator could have caught this issue sooner. This means we should work towards resilient reporting mechanisms to escalate such critical issues, and build capacity in the editor team to ensure no one person is responsible for merging critical fixes that are already available.</p>
</section>
<section id="acknowledgements" class="level2">
<h2 class="anchored" data-anchor-id="acknowledgements">Acknowledgements</h2>
<p>We would like to thank the editors for dealing with the stress from this inadvertent issue. We also thank the community for their patience as we only recently migrated to <code>rdm.vu.nl</code> and figure out these initial unexpected hurdles.</p>
</section>
<section id="references" class="level2">
<h2 class="anchored" data-anchor-id="references">References</h2>
<ul>
<li>Root cause for the downtime first observed in commit <a href="https://github.com/ubvu/open-handbook/commit/678ff8843dc018f76661b24ee25c64bff5c459df" target="_blank">678ff88</a></li>
<li>Proposed a fix for the root cause in <a href="https://github.com/ubvu/open-handbook/pull/220" target="_blank">pull Request #220</a></li>
<li>Downtime started at <a href="https://github.com/ubvu/open-handbook/commit/669b06528731f95566d605d65b9c3a507f58bced" target="_blank">commit 669b065</a> is where the</li>
<li>Resolved downtime in <a href="https://github.com/ubvu/open-handbook/commit/678ff8843dc018f76661b24ee25c64bff5c459df" target="_blank">commit 678ff88</a></li>
</ul>


</section>


<div id="quarto-appendix" class="default"><section id="footnotes" class="footnotes footnotes-end-of-document"><h2 class="anchored quarto-appendix-heading">Footnotes</h2>

<ol>
<li id="fn1"><p><code>ubvu.github.io/open-handbook</code> remained online during this entire time, and functions indirectly as a backup.↩︎</p></li>
</ol>
</section></div> ]]></description>
  <category>Handbook</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-10-22post-mortem.html</guid>
  <pubDate>Tue, 22 Oct 2024 00:00:00 GMT</pubDate>
</item>
<item>
  <title>Third Handbook Hackathon</title>
  <dc:creator>Alex van der Jagt, FGB, sec. KNOP</dc:creator>
  <dc:creator>Chris Hartgerink (host)</dc:creator>
  <dc:creator>Diogenes Cruz de Arcelino</dc:creator>
  <dc:creator>Elisa Rodenburg, UBVU</dc:creator>
  <dc:creator>Jessica Hrudey, FGB</dc:creator>
  <dc:creator>Jolien Scholten, UB</dc:creator>
  <dc:creator>Lena Karvovskaya, UBVU</dc:creator>
  <dc:creator>Stephanie van de Sandt, UBVU</dc:creator>
  <dc:creator>Tycho Hofstra, UBVU</dc:creator>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-09-30hackathon.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>In the third hackathon for the Research Support Handbook, held on September 25th, 2024, contributors gathered to make significant progress towards migrating the handbook to the VU domain (rdm.vu.nl). The event centered around sprinting to a finish line by refining existing content and ensuring accessibility standards are met.</p>
<p>Key activities included:</p>
<ol type="1">
<li><p><strong>Proofreading and Topic Refinement</strong>: Participants reviewed existing topics to ensure clarity and focus. This led to the realization that some topics, like “Data Publication,” would benefit from being split into more specific subtopics, such as “Open Science” or “Software Licensing.”</p></li>
<li><p><strong>Guide Titles Revision</strong>: We started normalizing guide titles into questions, making navigation easier and more value informed. We ideated options for guides now titled “Plan &amp; Design” to be converted into actionable questions like “How do I plan for managing my data?”</p></li>
<li><p><strong>Alt Text Improvement</strong>: We reviewed existing alt texts for images and refined them to ensure accessibility. We also identified some remaining images that had no alt text, and added it.</p></li>
<li><p><strong>Image Selection</strong>: Contributors identified and proposed openly licensed images to enhance the visual appeal of the guides, with some creative choices from <a href="https://doi.org/10.5281/zenodo.11147887" target="_blank">Zenodo’s RDM LEGO collection</a> <span class="citation" data-cites="bres_2024_11147887">(Bres and Bittner 2024)</span>.</p></li>
</ol>
<p>Overall, the hackathon was a productive session, and the handbook is now in its final stage, with the team preparing for the official launch on &lt;rdm.vu.nl&gt;. In next hackathons, we may focus on splitting existing topics and adding new ones, as our list of idea topics is growing rapidly.</p>
<section id="hackathon-issues" class="level2">
<h2 class="anchored" data-anchor-id="hackathon-issues">Hackathon Issues</h2>
<p><a href="https://github.com/ubvu/open-handbook/issues/175" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/175</a> <a href="https://github.com/ubvu/open-handbook/issues/178" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/178</a></p>
</section>
<section id="hackathon-pull-requests" class="level2">
<h2 class="anchored" data-anchor-id="hackathon-pull-requests">Hackathon Pull Requests</h2>
<p><a href="https://github.com/ubvu/open-handbook/pull/118" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/118</a> <a href="https://github.com/ubvu/open-handbook/pull/165" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/165</a> <a href="https://github.com/ubvu/open-handbook/pull/176" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/176</a> <a href="https://github.com/ubvu/open-handbook/pull/177" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/177</a> <a href="https://github.com/ubvu/open-handbook/pull/179" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/179</a> <a href="https://github.com/ubvu/open-handbook/pull/180" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/180</a> <a href="https://github.com/ubvu/open-handbook/pull/181" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/181</a> <a href="https://github.com/ubvu/open-handbook/pull/184" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/184</a> <a href="https://github.com/ubvu/open-handbook/pull/186" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/186</a> <a href="https://github.com/ubvu/open-handbook/pull/188" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/188</a></p>



</section>

<div id="quarto-appendix" class="default"><section class="quarto-appendix-contents" id="quarto-bibliography"><h2 class="anchored quarto-appendix-heading">References</h2><div id="refs" class="references csl-bib-body hanging-indent">
<div id="ref-bres_2024_11147887" class="csl-entry">
Bres, Ewa Elizabeth, and Christian Bittner. 2024. <em><span class="nocase">A collection of AI generated images visualising various RDM aspects</span></em>. Version 1.0.0. Zenodo. <a href="https://doi.org/10.5281/zenodo.11147887">https://doi.org/10.5281/zenodo.11147887</a>.
</div>
</div></section></div> ]]></description>
  <category>Handbook</category>
  <category>Hackathon</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-09-30hackathon.html</guid>
  <pubDate>Mon, 30 Sep 2024 00:00:00 GMT</pubDate>
</item>
<item>
  <title>Second Handbook Hackathon</title>
  <dc:creator>Alex van der Jagt</dc:creator>
  <dc:creator>Chris Hartgerink</dc:creator>
  <dc:creator>Elisa Rodenburg</dc:creator>
  <dc:creator>Jens de Bruijn</dc:creator>
  <dc:creator>Jolien Scholten</dc:creator>
  <dc:creator>Joy Jiayi Cheng</dc:creator>
  <dc:creator>Lena Karvovskaya</dc:creator>
  <dc:creator>Meron Vermaas</dc:creator>
  <dc:creator>Peter Vos</dc:creator>
  <dc:creator>Stephanie van de Sandt</dc:creator>
  <dc:creator>Tycho Hofstra</dc:creator>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-09-05hackathon.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>On September 5th, 2024, all authors participated in the second hackathon for the Research Support Handbook. For this hackathon, we focused on quality assurance. Quality assurance is crucial in ensuring that all parties at VU Amsterdam feel confident adopting this evolving, community-led resource as an official university page. Our goal is to migrate the handbook to rdm.vu.nl in the near future, which requires us to everything is in tip-top shape.</p>
<p>Collectively, we proofread the migrated LibGuide pages. The result of this are seven GitHub issues and nine pull requests for revisions. These include <a href="https://github.com/ubvu/open-handbook/issues/125" target="_blank">making sure all images are migrated into the handbook</a>, <a href="https://github.com/ubvu/open-handbook/issues/124" target="_blank">ensuring appropriate page titles</a>, and <a href="https://github.com/ubvu/open-handbook/issues/131" target="_blank">refining the contribution guide</a>.</p>
<p>During the hackathon, we observed a lot of links in <a href="https://libguides.vu.nl/rdm" target="_blank">the old LibGuide resource</a>, are broken. We did some much needed maintenance work during the hackathon, given that the Research Support Handbook will replace the LibGuide resource. We identified broken links and replaced them where possible. There is a need to make this a less manual process in the future and will seek out automations to help us maintain the links moving forward. Additionally, there are many internal links that need updating, changing from LibGuide URLs to GitHub pages. We also discovered several links accessible only with university credentials, which we believe detract from the user experience; these links will require special labeling and contextualization.</p>
<p>The general sentiment at the end of the hackathon is that there is still lots of work to do. The community standards are manifesting themselves, and it is clear that pathways need more work to be production ready. These discussions surfaced a wish to have more frequent hackathons at this time, until the standards are set and the included content is ready for rdm.vu.nl.</p>
<section id="hackathon-issues" class="level2">
<h2 class="anchored" data-anchor-id="hackathon-issues">Hackathon Issues</h2>
<ul>
<li><a href="https://github.com/ubvu/open-handbook/issues/123" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/123</a></li>
<li><a href="https://github.com/ubvu/open-handbook/issues/128" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/128</a></li>
<li><a href="https://github.com/ubvu/open-handbook/issues/125" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/125</a></li>
<li><a href="https://github.com/ubvu/open-handbook/issues/124" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/124</a></li>
<li><a href="https://github.com/ubvu/open-handbook/issues/123" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/123</a></li>
<li><a href="https://github.com/ubvu/open-handbook/issues/130" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/130</a></li>
<li><a href="https://github.com/ubvu/open-handbook/issues/131" class="uri" target="_blank">https://github.com/ubvu/open-handbook/issues/131</a></li>
</ul>
</section>
<section id="hackathon-pull-requests" class="level2">
<h2 class="anchored" data-anchor-id="hackathon-pull-requests">Hackathon Pull Requests</h2>
<ul>
<li><a href="https://github.com/ubvu/open-handbook/pull/126" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/126</a></li>
<li><a href="https://github.com/ubvu/open-handbook/pull/110" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/110</a></li>
<li><a href="https://github.com/ubvu/open-handbook/pull/127" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/127</a></li>
<li><a href="https://github.com/ubvu/open-handbook/pull/129" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/129</a></li>
<li><a href="https://github.com/ubvu/open-handbook/pull/132" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/132</a></li>
<li><a href="https://github.com/ubvu/open-handbook/pull/133" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/133</a></li>
<li><a href="https://github.com/ubvu/open-handbook/pull/134" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/134</a></li>
<li><a href="https://github.com/ubvu/open-handbook/pull/135" class="uri" target="_blank">https://github.com/ubvu/open-handbook/pull/135</a></li>
</ul>


</section>

 ]]></description>
  <category>Handbook</category>
  <category>Hackathon</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-09-05hackathon.html</guid>
  <pubDate>Thu, 05 Sep 2024 00:00:00 GMT</pubDate>
</item>
<item>
  <title>First Handbook Hackathon</title>
  <dc:creator>Alex van der Jagt</dc:creator>
  <dc:creator>Chris Hartgerink</dc:creator>
  <dc:creator>Dimitri Unger</dc:creator>
  <dc:creator>Elisa Rodenburg</dc:creator>
  <dc:creator>Jessica Hrudey</dc:creator>
  <dc:creator>Jolien Scholten</dc:creator>
  <dc:creator>Lena Karvovskaya</dc:creator>
  <dc:creator>Lucy O&#39; Shea</dc:creator>
  <dc:creator>Mar Barrantes-Cepas</dc:creator>
  <dc:creator>Meron Vermaas</dc:creator>
  <dc:creator>Peter Vos</dc:creator>
  <dc:creator>Stephanie van de Sandt</dc:creator>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-06-27hackathon.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>On June 27th, 2024, the first hackathon for the Research Support Handbook took place with all the post authors. For this hackathon, we focused on non-GitHub based contributions, to make it as easy as possible to contribute. To make getting started with contributing easier, <a href="https://ubvu.github.io/open-handbook/public/20240627hackathon.html" target="_blank">we created a choose your own adventure game</a>. We document some lessons and clarifications below, in addition to <a href="https://github.com/ubvu/open-handbook/issues?q=created%3A2024-06-27" target="_blank">the twelve reported problems and suggested changes</a>.</p>
<p>The workshop helped articulate the <strong>dynamic relation between topics and pathways</strong>. Topics are contained pages around a specific subject; pathways are a collection of topics. This means that pathways include the topics directly and that this content should be up to date at any given time. When topics are changed, pathways are dynamically updated, making sure there are no discrepancies. The only situation where this may not be the case, is when a pathway is still a work in progress and the topics are not yet properly linked.</p>
<p>Pathways will become more efficient to create as we include more topics in the handbook. Given that pathways are primarily collections of topics, this means that there is barely any new content in there, if any at all. As we include more topics (eight at this time), pathways can focus more and more on the structuring of content, and focus less on creating the content itself.</p>
<p>With new contributions, contributors surfaced the need to preview the changes to the handbook. We documented two ways to render the handbook for such previews: (1) creating a Pull Request automatically deploys a preview website and (2) running <code>quarto render</code> locally on the code. Option 1 requires no additional software to be installed, but requires some knowledge of GitHub. Option 2 does not require much knowledge of GitHub, but requires the Quarto software to be installed. There was also the note that deploying the handbook using GitHub pages required a change to the URL, which may cause issues when merging the changes back into the main handbook. This highlights that ensuring reliable previews of contributed content is of importance to some contributors to the handbook.</p>
<p>Lastly, the hackathon surfaced many questions and discussions around the collaborative decisions that will need to be made. When does a topic become too long and should it be split up into multiple topics? Can a topic include subtopics? How is the GitHub environment maintained? How much technical expertise is necessary to ensure the content does not go offline? What contributor roles are there and who has which role? How do roles get distributed and can people volunteer for them? This highlights the engagement with the handbook, and we encourage everyone (including ourselves) to generously surface these discussions in issues or in a next hackathon.</p>
<p>In summary, the first hackathon is a success! This is the start of the next phase of the handbook journey, moving from design and scaffolding to nurturing and growing the contents. There will be more hackathons, and these will be announced on this blog and on other channels at VU Amsterdam. Until the next one!</p>



 ]]></description>
  <category>Handbook</category>
  <category>Hackathon</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-06-27hackathon.html</guid>
  <pubDate>Thu, 27 Jun 2024 00:00:00 GMT</pubDate>
</item>
<item>
  <title>Hello world!</title>
  <link>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-05-23welcome.html</link>
  <description><![CDATA[ 
<div class="handbook-title">Research Support Handbook</div>




<p>This is the first blog entry on the Research Support Handbook. We will be posting more at a later time, and are looking forward to your contributions as well.</p>
<p>We will follow up with more details later.</p>



 ]]></description>
  <category>Handbook</category>
  <guid>https://rdm-os-cs-vu.github.io/open-handbook/blog/2024-05-23welcome.html</guid>
  <pubDate>Thu, 23 May 2024 00:00:00 GMT</pubDate>
</item>
</channel>
</rss>
