\documentclass[10pt]{article}

\usepackage{fullpage}
\usepackage{setspace}
\usepackage{parskip}
\usepackage{titlesec}
\usepackage[section]{placeins}
\usepackage{xcolor}
\usepackage{breakcites}
\usepackage{lineno}
\usepackage{hyphenat}





\PassOptionsToPackage{hyphens}{url}
\usepackage[colorlinks = true,
            linkcolor = blue,
            urlcolor  = blue,
            citecolor = blue,
            anchorcolor = blue]{hyperref}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother


\usepackage{natbib}




\renewenvironment{abstract}
  {{\bfseries\noindent{\abstractname}\par\nobreak}\footnotesize}
  {\bigskip}

\titlespacing{\section}{0pt}{*3}{*1}
\titlespacing{\subsection}{0pt}{*2}{*0.5}
\titlespacing{\subsubsection}{0pt}{*1.5}{0pt}


\usepackage{authblk}


\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}%

\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[english]{babel}



\usepackage{float}








\begin{document}

\title{Is Authorea FAIR?}



\author[1]{Authorea Team}%
\affil[1]{Affiliation not available}%


\vspace{-1em}



  
  \date{May 04, 2024}


\begingroup
\let\center\flushleft
\let\endcenter\endflushleft
\maketitle
\endgroup





\selectlanguage{english}
\begin{abstract}
In this post, we assess Authorea's compliance to FAIR principles
(\url{https://www.go-fair.org/fair-principles/}), i.e. how the
repository observes principles of machine-actionability: to
\textbf{f}ind, \textbf{a}ccess, \textbf{i}nteroperate, and
\textbf{r}euse data with none or minimal human intervention%
\end{abstract}%



\sloppy


\selectlanguage{english}
\begin{figure}[H]
\begin{center}
\includegraphics[width=0.35\columnwidth]{figures/FAIR-EN-364x366/FAIR-EN-364x366}

\end{center}
\end{figure}

\section*{Findable}

{\label{628163}}

\begin{quote}
The first step in (re)using data is to find them. Metadata and data
should be easy to find for both humans and computers.~
\end{quote}

\par\null

\subsection*{F1: (Meta) data are assigned globally unique and persistent
identifiers}

{\label{938293}}

Yes. Preprints and other research materials posted on Authorea are
assigned with a Digital Object Identifier (DOI). For example, the
DOI~\href{https://doi.org/10.22541/au.161401194.47276716/v2}{10.22541/au.161401194.47276716/v2}~points
uniquely and persistently to an article titled
"\href{https://www.authorea.com/doi/full/10.22541/au.161401194.47276716/v2}{Supporting
Information for "Microengineered materials with self-healing features
for soft robotics}". Moreover, data objects that are part of the
document along with their metadata are also assigned a unique,
persistent URL (e.g.,
\href{https://www.authorea.com/users/391311/articles/505459/master/folder/figures/image1}{this
dataset} in the same document).

\par\null

\subsection*{F2: Data are described with rich
metadata}

{\label{430241}}

Yes, but it is up to users to provide rich metadata. Authorea offers the
infrastructure to provide rich metadata alongside content, but does not
mandate it. In the case of scholarly article content, some metadata are
mandatory and are described in the JATSXML of the published articles. As
for data and other research materials, content is always associated with
a YML metadata file. For example, for
\href{https://www.authorea.com/users/391311/articles/505459/master/folder/figures/image1}{this
dataset}, the \texttt{config.yml} file looks like this:

\begin{verbatim}
---
version: 2
multicolumn: false
web-width: 500
align: center
float: h!
grid:
  rows: 1
  columns: 1
  grid_elements:
  - path: figures/image1/image1.png
    type: static
    from:
    - 1
    - 1
    to:
    - 1
    - 1
    url: "/users/391311/articles/505459/master/file/figures/image1/image1.png"
    folder_url: "/users/391311/articles/505459/master/folder/figures/image1"
\end{verbatim} 

This YAML file can be extended by authors to include additional
metadata.

\par\null

\subsection*{F3: Metadata clearly and explicitly include the identifier
of the data they
describe}

{\label{106365}}

Yes. In the example above, the metadata file contains a clear link to
the data it describes.

\par\null

\subsection*{F4: (Meta)data are registered or indexed in a searchable
resource}

{\label{228639}}

Partly. For scholarly content, all metadata and identifiers are indexed
and crawled daily by Google and other search engines. All Authorea
content is visible and presented in Google Scholar as well. However,
data folders are not systematically crawled and indexed.

\par\null

\pagebreak

\section*{Accessible}

{\label{181336}}

\begin{quote}
\textbf{}Once the user finds the required data, she/he/they need to know
how can they be accessed, possibly including authentication and
authorisation.
\end{quote}

\par\null

\subsection*{A1: (Meta)data are retrievable using a standardised
communication
protocol}

{\label{222683}}

Yes. All identifiers to scholarly content, data, and other research
materials in Authorea use a secure HTTP (HTTPS) protocol.

\par\null

\subsection*{A1.1: The protocol is open, free and universally
implementable}

{\label{145927}}

Yes.

\par\null

\subsection*{A1.2: The protocol allows for an authentication and
authorisation where
necessary}

{\label{868089}}

Yes.

\par\null

\pagebreak

\section*{Interoperable}

{\label{350538}}

\begin{quote}
The data usually need to be integrated with other data. In addition, the
data need to interoperate with applications or workflows for analysis,
storage, and processing.
\end{quote}

\par\null

\subsection*{I1: (Meta)data use a formal, accessible, shared, and broadly
applicable language for knowledge
representation}

{\label{475998}}

Partly. Authorea does not currently use RDF, OWL, JSON LD, or other
Linked Data and semantic web languages to describe its contents. It
embraces standard JATSXML for scholarly content and an accessible,
shared, open (but not formal) YAML for data and other materials.

\par\null

\subsection*{I2: (Meta)data use vocabularies that follow the FAIR
principles}

{\label{269274}}

Partly. The JATSXML schema used by scholarly resources on Authorea is
documented (\url{http://www.w3.org/2001/XMLSchema-instance}), but the
YAML file used for data, while simple, is not.

\par\null

\subsection*{I3: (Meta)data include qualified references to other
(meta)data}

{\label{433481}}

Not applicable / not at the moment. A~qualified reference is possible
but not applicable or applied in any of the current schemas or datasets.

\par\null

\pagebreak

\section*{Reusable}

{\label{353640}}

\begin{quote}
The ultimate goal of FAIR is to optimise the reuse of data. To achieve
this, metadata and data should be well-described so that they can be
replicated and/or combined in different settings.~
\end{quote}

\par\null

\subsection*{R1: (Meta)data are richly described with a plurality of
accurate and relevant
attributes}

{\label{298072}}

Yes, but it is up to users to provide accurate and relevant attributes
in the metadata.

\par\null

\subsection*{R1.1: (Meta)data are released with a clear and accessible
data usage
license}

{\label{103968}}

Yes. On Authorea, four kinds of usage licenses can be assigned to
scholarly content (and they also apply to any underlying data and
materials): Non-exclusive, no reuse; CCBY 4.0;~ CC0 1.0; MIT.

\par\null

\subsection*{R1.2: (Meta)data are associated with detailed
provenance}

{\label{811155}}

Yes. Posted scholarly articles on Authorea can be cited giving detailed
provenance (and version history) for both the full text, data, and
research materials associated with the article.

\par\null

\subsection*{R1.3: (Meta)data meet domain-relevant community
standards}

{\label{390272}}

Partly. Similar to I2 ({\ref{269274}}), only Authorea's
JATSXML meets community standards.~~

~

\pagebreak

\par\null

For more details, visit \href{https://bit.ly/Authorea-FAIR}{Authorea's
FAIR Implementation Profile}.







\par\null\par\null

~

\selectlanguage{english}
\FloatBarrier
\end{document}

