News about research data management

maDMP API specification presented at the 27th RDA Plenary Meeting in London

13. October 2026

A man holding a microphone is standing in front of a presentation screen, pointing at an image on the screen. — © Jakub Jirka

The maDMP Common API Working Group presented its final result at the RDA Plenary Meeting last week.

EULiST partners gather for workshop on PIDINST

08. October 2026

Our Spanish EULiST partner hosted a workshop on PIDINST in Madrid, a metadata schema that provides persistent identifiers for scientific instruments.

Fellowship of the Data Meeting 2026

01. October 2026

The photograph shows a presentation board with two women standing in front of it. In the foreground, you can see the audience sitting down. — © Universität Wien / Jennifer Panis

We were there when the international RDM community met at the University of Vienna on 21 and 22 September.

Our expanded range of training courses for the winter semester

02. September 2026

Our training icon, combined with the logos of various tools. — © TU Wien

We are delighted to offer a Jupyter workshop, held by dataLab, as well as a new lecture on RDM in addition to our established training this autumn.

Cool new TU Wien Research Data features in hot times

18. August 2026

Screenshot of the file preview in TU Wien Research Data — © TU Wien

Thanks to version 14 of the InvenioRDM software, our data repository is now better than ever.

Research Data Management for Information Retrieval – ESSIR 2026

12. August 2026

A woman is standing in front of a large screen, pointing at a graphic on display. In the foreground, several people are sitting, looking towards the presentation. — © Alexandra Andrei

Our colleague Florina Piroi brought the basic RDM concepts to the Information Retrieval community.

Shared RDM: Three years of joint RDM development in Austria

07. July 2026

A group photo of around 35 people under some trees. — © Dietmar Herbst

The Shared RDM Services and Infrastructure project was successfully concluded with the final project meeting on 23 June 2026 in Graz.

Data stewardship is gaining in importance at Austrian universities

02. July 2026

Five speech bubbles containing text, with the title ‘Wishes for a national data steward network’ above them. — © TU Wien

Survey shows that data stewardship is already firmly established at Austrian universities, but roles, responsibilities and organisational integration…

Research Data Management without borders

25. June 2026

Two people are standing in front of a building; mountains can be seen in the background. — © TU Wien

TU Wien is driving better research data practices – from Central Asia to Europe and beyond.

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