The picture shows a photo of the entrance hall at TU Wien with RDM symbols superimposed.

Research Data Management at TU Wien

You want to manage your data and your code according to the FAIR principles? You want to store, share, and publish your data and need a repository? Your funding agency requires a data management plan? At the Center for Research Data Management (RDM), a multidisciplinary team is on hand to support you.

Technical services and tools

Our “Data publication” icon on a gray background

TU Wien Research Data Repository, TU Wien DMP Tool, TUgitLab, TUsurvey

Data Stewards

Our icon for "Team": graphic with three people depicted in a circle

Your contacts for RDM questions

Infos and guidelines

Our “Data organization” icon on an orange background

DMP handbook, RDM policy, funders' guidelines, basics

Workshops

Our icon for "Workshop": graphic with three people looking at a presentation

Our continuing education courses

Student information

Our icon for "Teaching": Doctor's hat in a circle

Lectures, data publication guide

Projects, initiatives, networks

Graphic representation of a globe: our icon for "international"

TU Wien, national and international

News

TU Wien Center for RDM secures highly competitive EOSC Gravity funding

12. May 2026

© TU Wien

The project DAMAP@EOSC PL focuses on deploying DAMAP as a production ready service within the Polish EOSC Node.

forschungsdaten.info with a new design

05. May 2026

© forschungsdaten.info

The popular platform for information on research data management in the DACH region has been thoroughly revamped and expanded.

Drops, bubbles, and supercomputing

14. April 2026

The picture shows a woman standing in front of a bookshelf. To the right of her is a scientific visualisation, and above her is a banner with text. — © TU Wien / Livia Beck

Dr Francesca Mangani on simulating drops and bubbles in turbulence, supercomputing calculations, and the importance of fundamental physics in…

Events

Events from 20. May 2026

Git for newbies

14:00 16:00

Type of event: WorkshopEvent location: TU Wien, 1040 Wien

Get your DMP done: a practical walkthrough of the TU Wien DMP Tool

13:00 14:30

Type of event: WorkshopEvent location: TU Wien, 1040 Wien

How do you write a data management plan (DMP) - and why anyway?

09:30 12:30

Type of event: WorkshopEvent location: TU Wien, 1040 Wien

Introduction to Git

10:00 12:00

Type of event: WorkshopEvent location: TU Wien, 1040 Wien

Mastering Git

13:30 15:30

Type of event: WorkshopEvent location: TU Wien, 1040 Wien

Contact us

Office location:
Center for Research Data Management,
Favoritenstraße 16 (top floor), 1040 Vienna

Phone: +43 1 58801 406120

research.data@tuwien.ac.at

Matrix: #research.data:tuwien.ac.at, opens an external URL in a new window

Contact us

Office location:
Center for Research Data Management,
Favoritenstraße 16 (top floor), 1040 Vienna

Phone: +43 1 58801 406120

research.data@tuwien.ac.at

Matrix: #research.data:tuwien.ac.at, opens an external URL in a new window

Our website uses cookies and integrates content from third-party providers to ensure you get the best experience on our website, for analytical purposes, to provide social media features, and for targeted advertising. This it is necessary in order to pass information on to respective service providers. If you would like additional information about cookies and content from third-party providers on this website, please see our Data protection declaration.

Mandatory Cookies

These cookies are required to help our website run smoothly.

Name	Purpose	Lifetime	Type	Provider
CookieConsent	Saves your settings for the use of cookies on this website.	1 year	HTML	Homepage TU Wien
SimpleSAML	This is needed to distinguish between the sessions of the logged-in users.	session	HTTP	Login TU Wien
SimpleSAMLAuthToken	This is needed to distinguish between the sessions of the logged-in users.	session	HTTP	Login TU Wien
fe_typo_user	Is needed so that in case of a Typo3 frontend login the session ID is recognized to grant access to protected areas.	session	HTTP	Homepage TU Wien
staticfilecache	Is needed to optimize the delivery time of the website.	session	HTTP	Homepage TU Wien
JESSIONSID	Is needed so that in case of a LectureTube the session ID is recognized to grant access to protected areas.	session	HTTP	LectureTube TU Wien
_shibsession_lecturetube	This is needed to distinguish between the sessions of the logged-in users.	session	HTTP	LectureTube TU Wien

Anonymised Web Statistics

These cookies help us to continuously improve our services and adapt our website to your needs. We statistically evaluate the pseudonymized data collected from our website.

Name	Purpose	Lifetime	Type	Provider
_pk_id	Used to store a few details about the user such as the unique visitor ID.	13 months	HTML	Matomo TU Wien
_pk_ref	Is used to store the information of the users home website.	6 months	HTML	Matomo TU Wien
_pk_ses	Is needed to store temporary data of the visit.	30 minutes	HTML	Matomo TU Wien

Marketing and Third Party

With the help of these cookies and third-party content we strive to improve our offer for our users. By means of anonymized data of website users we can optimize the user flow. This enables us to improve ads and website content.

Name	Purpose	Lifetime	Type	Provider
facebook	Is used to Enable ad delivery or retargeting	90 days	HTTP	Meta
__fb_chat_plugin	Is needed to store and track interactions (marketing/tracking).	persistent	HTTP	Meta
_js_datr	Is needed to save user settings.	2 years	HTTP	Meta
_fbc	Is needed to save the last visit (marketing/tracking).	2 years	HTTP	Meta
fbm	Is needed to store account data (marketing/tracking).	1 year	HTTP	Meta
xs	Is needed to store a unique session ID (marketing/tracking).	1 year	HTTP	Meta
wd	Is needed to log the screen resolution.	1 week	HTTP	Meta
fr	Is needed to serve ads and measure and improve their relevance.	3 months	HTTP	Meta
act	Is needed to store logged in users (marketing/tracking).	90 days	HTTP	Meta
_fbp	Is needed to store and track visits to various websites (marketing/tracking).	3 months	HTTP	Meta
datr	Is needed to identify the browser for security and website integrity purposes, including account recovery and identification of potentially compromised accounts.	2 years	HTTP	Meta
dpr	Is used for analysis purposes. Technical parameters are logged (e.g. aspect ratio and dimensions of the screen) so that Facebook apps can be displayed correctly.	1 week	HTTP	Meta
sb	Is needed to store browser details and security information of the Facebook account.	2 years	HTTP	Meta
dbln	Is needed to store browser details and security information of the Facebook account.	2 years	HTTP	Meta
spin	Is needed for promotional purposes and social campaign reporting.	session	HTTP	Meta
presence	Contains the "chat" status of logged in users.	1 month	HTTP	Meta
cppo	Is needed for statistical purposes.	90 days	HTTP	Meta
locale	Is needed to save the language settings.	session	HTTP	Meta
pl	Required for Facebook Pixel.	2 years	HTTP	Meta
lu	Required for Facebook Pixel.	2 years	HTTP	Meta
c_user	Required for Facebook Pixel.	3 months	HTTP	Meta
bcookie	Is needed to store browser data (marketing/tracking).	2 years	HTTP	LinkedIn
li_oatml	Is needed to identify LinkedIn members outside of LinkedIn for advertising and analytics purposes.	1 month	HTTP	LinkedIn
BizographicsOptOut	Is needed to save privacy settings.	10 years	HTTP	LinkedIn
li_sugr	Is needed to store browser data (marketing/tracking).	3 months	HTTP	LinkedIn
UserMatchHistory	Is needed to provide advertising or retargeting (marketing/tracking).	30 days	HTTP	LinkedIn
linkedin_oauth_	Is needed to provide cross-page functionality.	session	HTTP	LinkedIn
lidc	Is needed to store performed actions on the website (marketing/tracking).	1 day	HTTP	LinkedIn
bscookie	Is needed to store performed actions on the website (marketing/tracking).	2 years	HTTP	LinkedIn
X-LI-IDC	Is needed to provide cross-page functionality (marketing/tracking).	session	HTTP	LinkedIn
AnalyticsSyncHistory	Stores the time when the user was synchronized with the "lms_analytics" cookie.	30 days	HTTP	LinkedIn
lms_ads	Is needed to identify LinkedIn members outside of LinkedIn.	30 days	HTTP	LinkedIn
lms_analytics	Is needed to identify LinkedIn members for analytics purposes.	30 days	HTTP	LinkedIn
li_fat_id	Required for indirect member identification used for conversion tracking, retargeting and analytics.	30 days	HTTP	LinkedIn
U	Is needed to identify the browser.	3 months	HTTP	LinkedIn
_guid	Is needed to identify a LinkedIn member for advertising via Google Ads.	90 days	HTTP	LinkedIn