News about research data management

22. June 2021

Successful start for FAIR Office Austria

Representatives from ministries, universities and the GO FAIR initiative gave presentations on the topic of FAIR from different angles. The recordings and presentation slides of the event are now available.

On 9 June, the FAIR Office Austria, opens an external URL in a new window, which was developed and set up as part of the FAIR Data Austria, opens an external URL in a new window project, was officially opened in an online event with numerous presentations and participants. The topics of the presentations varied, focusing on European developments and the technical side of FAIR in addition to the activities of GO FAIR. Case studies were used to explain how the FAIR principles facilitate the handling of sensitive data and the cooperation between different institutions.

The launch event was a first step of FAIR Office Austria towards its self-set goals of networking stakeholders from research and service institutions and jointly advancing the implementation of the FAIR principles in Austria. The next milestone relates to the establishment of a closer link to the global GO FAIR initiative and is coming up soon: as of tomorrow, FAIR Office Austria will be the official GO FAIR National Support and Coordination Office for Austria.

Material for review

The presentation slides and video recordings of the launch event are now available for viewing in the Phaidra Collection FAIR Office Austria Launch Event, opens an external URL in a new window. Additionally, all presentations are listed individually in the following overview:

Video recording of the event

Presentation slides

Hana Pergl, GO FAIR International Support and Coordination Office (GFISCO) & CODATA: GOing FAIR (Inter)nationally
Peter Kraker, Open Knowledge Maps & GO FAIR Executive Board: GO FAIR in Practice: The Discovery Implementation Network
Stefan Hanslik, Austrian Federal Ministry of Education, Science and Research (BMBWF), Paolo Budroni, TU Wien Bibliothek, Head of EOSC and International Liaison Office: Web of FAIR Data and Services – EOSC: The Austrian Use Case
Martin Semberger, Federal Ministry for Digital and Economic Affairs (BMDW): Making Public Data FAIR
Barbara Sánchez, TU Wien, Center for Research Data Management: FAIR Office Austria –An Initiative to Connect Research Communities and Service Providers
Andreas Rauber, TU Wien, Institute of Information Systems Engineering: FAIR technical infrastructures currently in development
Stefanie Lindstaedt, TU Graz and Know-Center GmbH: FAIR Research at TU Graz

Contact

TU Wien
Center for Research Data Management
Favoritenstraße 16 (top floor), 1040 Vienna
research.data@tuwien.ac.at

Twitter: @RDMTUWien

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