[DE] Betreuung wissenschaftlicher Arbeiten (Teil 2/2)

Return to Past Events 2018

19. September 2018, 09:00 until 17:00

[DE] Betreuung wissenschaftlicher Arbeiten (Teil 2/2)

Other

Termin: 18. + 19.09.2018

Zeit/Dauer: 9-17 Uhr

Ort: Sitzungszimmer des Rektorats (Karlsplatz 13, 1040 Wien, 1. Stock)

Trainer_in: Mag.a Andrea Hoyer-Neuhold, opens an external URL in a new window

Gruppengröße: mind. 8, max. 15 Teilnehmer_innen

Zielgruppe: Lehrende, die Bachelor- und Masterarbeiten betreuen und beurteilen oder diese Aufgabe demnächst übernehmen werden.

Ziele:

Ziel des Workshops ist es, pädagogisch-didaktisch bewährte Möglichkeiten der Betreuungsarbeit kennen zu lernen und sich im Kolleg_innenkreis mit den vielfältigen Anforderungen in der Doppelrolle als Betreuer_in und Beurteiler_in einer wissenschaftlichen Arbeit auseinander zu setzen.

Nach dem Workshop sind Sie in der Lage…

Betreuungsaufgaben nach Phasen des wissenschaftlichen Arbeitens zu differenzieren,
Methoden der Betreuung für Gruppen- und Einzelbetreuung einzusetzen,
ein persönliches Betreuungskonzept zu entwickeln,
einen Kriterienkatalog hinsichtlich inhaltlicher, methodischer und formaler Aspekte einer wissenschaftlichen Arbeit zu entwickeln/modifizieren

Inhalt:

Betreuungsaufgaben in den einzelnen Phasen des Entstehungsprozesses einer wissenschaftlichen Arbeit
Möglichkeiten der Betreuungsorganisation
Betreuungsmethoden für Einzel- sowie Gruppensettings (Analyse- und Feedbackgespräche)
Anspruchsniveaus an Bachelor- und Masterarbeiten sowie Dissertationen
Beurteilungskriterien und Benotungsschlüssel hinsichtlich inhaltlicher, methodischer und formaler Aspekte

Methoden:

Methodischer Wechsel zwischen Vortrags-, Erarbeitungs-, Erprobungs- und Reflexionsphasen

Kosten für Mitarbeiter_innen anderer Universitäten: 350 €

Calendar entry

Event location: Sitzungszimmer des Rektorats, 1.OG
1040 Wien
Karlsplatz 13
Organiser: focus:lehre Team
hochschuldidaktik@tuwien.ac.at
Public: No
Entrance fee: No
Registration required: Yes

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

[DE] Betreuung wissenschaftlicher Arbeiten (Teil 2/2)

Event details