Poster sessions are an integral part of almost every scientific conference. The posters on display are intended to present and visualize research results as effectively as possible and to put them up for discussion. This makes them an important aspect of scientific publishing.
Get credit where credit is due.
Make your poster citable
The contents of a scientific poster can also be quoted. TUHH Open Research (TORE) is available as a storage location for scientific publications from the TUHH that are to be publicly accessible. There is also room for your poster.
TORE offers you:
- A DOI for the unique referencing of your poster
- The pre-allocation of the DOI so that it can already be integrated into the poster
- Listing of all persons involved
- Connection to your ORCID profile
- A permanent storage
- The optimized availability for (academic) search engines
Security for subsequent use
May a conference twitterer post your poster in a tweet or in a report?
Make it easier for yourself and your colleagues and add a license to your poster. So others know what you want. Creative Commons licenses, which can be put together according to the modular principle, are ideal for this purpose. The optimal license in terms of Open Access is CC BY 4.0.
Lizence generator: creativecommons.org/choose/
Aberle, Christoph/Daubitz, Stephan (2019): „Mobilitätsarmut“ in Berlin und Hamburg? Kombinierte Forschung zu mobilitätsbezogener sozialer Exklusion. Online: https://doi.org/10.15480/882.2327
Software development is often an important part of scientific work at TUHH. Many use GitHub to create and share scientific software together. What was missing for a long time was the possibility to clearly reference this software. Only then it can be quoted without problems in scientific publications.
Digital Object Identifiers (DOI) have become the quasi-standard for referencing electronic publications. So what could be more obvious than using DOIs for software? Since 2014 this is possible through the cooperation of GitHub and Zenodo. Zenodo is an open platform for the permanent archiving of research results of almost any kind, operated by CERN and financed by the EU, among others: zenodo.org/features
If you are already active at GitHub, you can connect an existing repository with a Zenodo account. The repository will then be archived on Zenodo and a DOI for the repository is assigned. Further releases are also provided for.
A current example from the Institute of Communication Networks at TUHH:
Sebastian Lindner. (2018, July 16). ComNetsHH/LRE-OMNeT: Publication release (Version v1.0.1). Zenodo. https://doi.org/10.5281/zenodo.1313054
GitHub describes how it works in just under 10 minutes reading time: Making Your Code Citable
And two more tips about Zenodo:
- Use the TUHH-Community on Zenodo for the assignment to the TU: https://zenodo.org/communities/tuhh/ Assignment is also possible at a later date.
- Add the ORCID iD (Give credit where credit is due) to the authors, if necessary.
p.s. It should not go unmentioned: There is also an alternative repository connection to figshare:
Often asked for; now it’s time: From now on, the DOI for your document will be displayed on tub.dok before you upload a publication.
This allows you to add the DOI to your PDF for better identification of printouts or saved copies of the file or to insert a quotation recommendation.
By the way, tub.dok supports different persistent identifier schemes: DOI (Digital Object Identifier), Handle and URN (Uniform Resource Name). Persistent identifiers are used to ensure that a publication can be referenced unambiguously and permanently. Of these, the DOI is the best known and therefore the most important one for you.
The named persistent identifiers are initially marked, but have not yet been registered. Therefore, they cannot yet be resolved. They will be registered after completion of your publication, if the publication is activated by us. We will let you know by e-mail. Please be patient until then. :-)
tub.dok is Open Source
The extension of the software DSpace-CRIS, which we use as the basis of our open access repository, was realized by The Library Code and is available to the entire DSpace community via a branch on github for subsequent use.