TU Wien
all news

All news at TU Wien

05. May 2026

forschungsdaten.info with a new design

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

After many years of development and refinement, it was time for a major makeover: The information platform forschungsdaten.info, opens an external URL in a new window has been redesigned, streamlined, and enhanced with additional features and content. An overview of all new features is provided in the news article “In eigener Sache: Vieles neu bei forschungsdaten.info”. This article, as well as most pages at forschungsdaten.info, are currently only available in German. The translation of all pages is in preparation, and some information is already available in English on the English pages, opens an external URL in a new window.

Here are some highlights of the relaunch:

New search function for the events calendar

The events calendar, opens an external URL in a new window is increasingly beeing used by Austrian institutions to promote their RDM-related events. It is now more user-friendly and can be filtered by topic when searching for events. Weekly and monthly overviews will also be available shortly. New events can be easily submitted via the calendar-related contact form, opens an external URL in a new window.

New: Collection of job vacancies

A brand-new feature is an overview page that displays job vacancies related to RDM, opens an external URL in a new window. Information on currently advertised positions can be sent via the thematic contact form, opens an external URL in a new window. The job overview, the calendar, and much more information for the RDM (consultancy) practice are now clearly compiled on the Praxis Kompakt, opens an external URL in a new window page.

RDM in Austria at a glance

The information specific to RDM in Austria, opens an external URL in a new window has also been restructured, and the content is now presented more concisely. By selecting the option “FDM im deutschsprachigen Raum” in the main menu, you get an overview of all available Austria pages with just one click.

If you have any requests for additions or updates to the Austria pages, please contact the forschungsdaten.info editorial team or us via the email addresses below. If you are a researcher or work in research support and would generally like to contribute your RDM expertise as an editor, we look forward to hearing from you as well! The TU Wien Center for RDM has been actively involved in the editorial team at forschungsdaten.info for many years. Together with the University of Vienna, we take care of the Austria pages, contribute to the general RDM topics, and greatly appreciate the excellent resources and the exchange with the colleagues in the editorial team.

Well-tried: The newsletter

The newsletter is not new, but highly recommended to stay up to date and connected: forschungsdaten.info newsletter, opens an external URL in a new window.

Contact

TU Wien
Center for Research Data Management
research.data@tuwien.ac.at

Editorial board of forschungsdaten.info
kontakt@forschungsdaten.info

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

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

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