News about research data management

A spotlight on the formation of EOSC Nodes

02. December 2025

A man and a woman stand next to each other, smiling at the camera and holding a small, rectangular glass object. — © TU Wien / Livia Beck

Over the past year, TU Wien chaired the Management Board and therefore hosted the 5th General Assembly of the EOSC Support Office Austria at TUtheSky…

TU Wien launches data stewardship pilot

25. November 2025

The photo shows nine people sitting around a table in the foreground and a monitor with a Gantt chart in the background. — © TU Wien / Tomasz Miksa

On October 29, 2025, we kicked off the establishment of data stewardship practices at two TU Wien faculties.

Beyond models

18. November 2025

The image shows a man working on a laptop. Next to him and in the background, graphic point clouds and lines can be seen.

Félix Iglesias Vázquez on open code practices and the development of versatile algorithms for real-world data challenges.

TU Wien Research Data Repository earns CoreTrustSeal

11. November 2025

This certification places TU Wien among the top players in the open repositories league.

“FAIR & AI” symposium on 27 November 2025

06. November 2025

Cluster Forschungsdaten invites you to an exchange at TU Graz on the intersection of RDM and AI.

"Metadata is really everything!"

23. October 2025

The picture shows a photo of a woman, with the words "I care to make it FAIR" and a world map in bright colours in the background. — © TU Wien / Livia Beck

Dr Mariette Vreugdenhil on FAIR Data Management in Remote Sensing Research.

Shared RDM project meeting 2025

01. October 2025

The photo shows about 40 people standing in a semi-circle. — © Shared RDM

How can the Austrian universities work together on RDM topics after the end of the project?

Open Science Festival 2025: Innovation, inspiration, networking

18. September 2025

Four women sit in front of a green area and a fountain on cardboard boxes in the Open Science Festival design. — © Birgit Söser

On 8 and 9 September, the University of Vienna invited Austrian and international guests to an Open Science exchange.

Findings from the FAIR-IMPACT support programme

11. September 2025

Screenshot of the cover of the mentioned Implementation Story: three differently sized rounded squares on a white background, with various logos above them and the title of the report below. — © fair-impact.eu

The programme for repositories and data service providers helped us to reflect on the FAIRness of our services and optimise existing workflows.

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