News about research data management

Git training at the Center for RDM

28. May 2026

The photo shows a presentation screen displaying Git terminology, with a person standing to the right and another to the left. — © TU Wien

Last week, our “Git for newbies” workshop made its debut as part of the TU Wien continuing education programme.

TU Wien Center for RDM secures highly competitive EOSC Gravity funding

12. May 2026

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

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…

We go the extra mile for you!

08. April 2026

The photo shows a large garden with a path, trees, a hut and snow-capped mountains in the background. — © TU Wien / Florina Piroi

RDM training for Digital Humanism PhD students in Reichenau.

AI on the rise, new opportunities for HCI

26. March 2026

The picture shows a man sitting in an office chair, holding a small object in his hands. To the right of him is a graphic, and above him a text banner. — © TU Wien / Livia Beck

Prof. Paweł W. Woźniak on human-centred design despite the AI hype, the diversity of methods in user research, and the development and sharing of…

TU Wien goes TU Graz for the 2026 InvenioRDM partners workshop

19. March 2026

Group photo with 28 people. — © Dietmar Herbst

Max Moser from the Center for RDM led sessions on the improvement of the REST API documentation and data curation workflows.

“Data is nothing without purpose”

12. March 2026

The image shows a man holding a drinking cup in his hand and standing in front of a shelf with models. To the right of the person, a flow chart is indicated, and above the person, lettering can be seen. — © TU Wien / Livia Beck

Dr Gabriel Wurzer on purpose-driven data, clashing research-practice cultures, and architecture’s “data bunkers” hostile to AI.

20th International Digital Curation Conference

03. March 2026

The photograph shows a woman at a standing desk in front of a presentation in a festive room with audience. — © TU Wien / Tomasz Miksa

Tomasz Miksa and Suvini Lai represented the Center for RDM and OSTrails at the IDCC26 in Zagreb.

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