paper.md

title	title_short	tags	authors	affiliations	date	cito-bibliography	event	biohackathon_name	biohackathon_url	biohackathon_location	group	git_url	authors_short
BioHackEU23 report: Template for the very long title	BioHackEU23 #26: unknown chemical substances	cheminformatics PubChem unknown chemical substances	name affiliation First Author 1 name orcid affiliation Last Author 0000-0000-0000-0000 2	name index First Affiliation 1 name ror index ELIXIR Europe 044rwnt51 2	8 November 2023	paper.bib	BH23EU	BioHackathon Europe 2023	https://biohackathon-europe.org/	Barcelona, Spain, 2023	Project 26	https://github.com/biohackrxiv/publication-template	First Author \emph{et al.}

Introduction

As part of the BioHackathon Europe 2023, we here report...

Author information

Information about the authors is given in the YAML format at the top of this template. For authors you provide their names, their affiliations, and ideally their ORCID identifier. For affiliations, the Research Organization Registry (ROR) identifier can be given. For example, this is the author information for this template:

authors:
  - name: First Author
    affiliation: 1
  - name: Last Author
    orcid: 0000-0000-0000-0000
    affiliation: 2
affiliations:
  - name: First Affiliation
    index: 1
  - name: ELIXIR Europe
    ror: 044rwnt51
    index: 2

Formatting

This document use Markdown and you can look at this tutorial.

Subsection level 2

Please keep sections to a maximum of only two levels.

Tables and figures

Tables can be added in the following way, though alternatives are possible:

Table: Note that table caption is automatically numbered and should be given before the table itself.

Header 1	Header 2
item 1	item 2
item 3	item 4

A figure is added with:

Other main section on your manuscript level 1

Lists can be added with:

1. Item 1
2. Item 2

Citation Typing Ontology annotation

You can use CiTO annotations, as explained in this BioHackathon Europe 2021 write up and this CiTO Pilot. Using this template, you can cite an article and indicate why you cite that article, for instance DisGeNET-RDF [@citesAsAuthority:Queralt2016].

The syntax in Markdown is as follows: a single intention annotation looks like [@usesMethodIn:Krewinkel2017]; two or more intentions are separated with colons, like [@extends:discusses:Nielsen2017Scholia]. When you cite two different articles, you use this syntax: [@citesAsDataSource:Ammar2022ETL; @citesAsDataSource:Arend2022BioHackEU22].

Possible CiTO typing annotation include:

• citesAsDataSource: when you point the reader to a source of data which may explain a claim
• usesDataFrom: when you reuse somehow (and elaborate on) the data in the cited entity
• usesMethodIn
• citesAsAuthority
• citesAsEvidence
• citesAsPotentialSolution
• citesAsRecommendedReading
• citesAsRelated
• citesAsSourceDocument
• citesForInformation
• confirms
• documents
• providesDataFor
• obtainsSupportFrom
• discusses
• extends
• agreesWith
• disagreesWith
• updates
• citation: generic citation

Results

Discussion

...

Acknowledgements

...

References