From a678365d4c8e973ebae53833d9519ac5e4850a39 Mon Sep 17 00:00:00 2001
From: Mohammad Akhlaghi <mohammad@akhlaghi.org>
Date: Thu, 9 Jul 2020 09:55:14 +0100
Subject: Uncommented the slide on relevant RDA output

Since this is an RDA-affiliated talk, its better for these slides to
be present.
---
 slides-intro-short.tex | 54 +++++++++++++++++++++++++-------------------------
 1 file changed, 27 insertions(+), 27 deletions(-)

(limited to 'slides-intro-short.tex')

diff --git a/slides-intro-short.tex b/slides-intro-short.tex
index 096819f..6019986 100644
--- a/slides-intro-short.tex
+++ b/slides-intro-short.tex
@@ -95,33 +95,33 @@
   \usebackgroundtemplate{ }    %% undeclare it
 
 
-%  \begin{frame}{Challenges of the RDA-WDS Publishing Data Workflows WG {\small (DOI:\href{https://doi.org/10.1007/s00799-016-0178-2}{10.1007/s00799-016-0178-2})}}
-%    Challenges (also relevant to researchers, not just repositories)
-%    \begin{itemize}
-%    \item \emph{Bi-directional linking}: how to \alert{link data and publications}.
-%    \item \emph{\alert{Software management}:} how to manage, preserve, publish and cite software?
-%    \item \emph{Metrics:} \alert{how often} are data used.
-%    \item \emph{Incentives to researchers:} how to \alert{communicate benefits} of following good practices \alert{to researchers}.
-%    \end{itemize}
-
-%    \begin{center}
-%      \includegraphics[width=4cm]{img/rda.png}\hspace{1cm}
-%      \includegraphics[width=4cm]{img/wds.jpg}
-%    \end{center}
-
-%    \ifdefined\longformat\pause\fi
-
-%    ``\emph{We would like to see a workflow that results in all
-%      \textcolor{blue!30!green}{\bf scholarly objects being connected},
-%      linked, citable, and persistent to allow researchers to navigate
-%      smoothly and to \alert{\bf enable reproducible research}.  This
-%      includes \alert{{\bf linkages} between documentation, code, data, and
-%        journal articles in an integrated environment}. Furthermore,
-%      in the ideal workflow, all of these objects need to be
-%      \alert{\bf well documented} to enable other researchers (or
-%      citizen scientists etc) to reuse the data for new
-%      discoveries.}''
-%  \end{frame}
+  \begin{frame}{Challenges of the RDA-WDS Publishing Data Workflows WG {\small (DOI:\href{https://doi.org/10.1007/s00799-016-0178-2}{10.1007/s00799-016-0178-2})}}
+    Challenges (also relevant to researchers, not just repositories)
+    \begin{itemize}
+    \item \emph{Bi-directional linking}: how to \alert{link data and publications}.
+    \item \emph{\alert{Software management}:} how to manage, preserve, publish and cite software?
+    \item \emph{Metrics:} \alert{how often} are data used.
+    \item \emph{Incentives to researchers:} how to \alert{communicate benefits} of following good practices \alert{to researchers}.
+    \end{itemize}
+
+    \begin{center}
+      \includegraphics[width=4cm]{img/rda.png}\hspace{1cm}
+      \includegraphics[width=4cm]{img/wds.jpg}
+    \end{center}
+
+    \ifdefined\longformat\pause\fi
+
+    ``\emph{We would like to see a workflow that results in all
+      \textcolor{blue!30!green}{\bf scholarly objects being connected},
+      linked, citable, and persistent to allow researchers to navigate
+      smoothly and to \alert{\bf enable reproducible research}.  This
+      includes \alert{{\bf linkages} between documentation, code, data, and
+        journal articles in an integrated environment}. Furthermore,
+      in the ideal workflow, all of these objects need to be
+      \alert{\bf well documented} to enable other researchers (or
+      citizen scientists etc) to reuse the data for new
+      discoveries.}''
+  \end{frame}
 
   \newcommand{\allopacity}{1}
   \ifdefined\longformat
-- 
cgit v1.2.1

