{"id":223,"date":"2010-08-19T16:19:09","date_gmt":"2010-08-19T20:19:09","guid":{"rendered":"http:\/\/sites.scranton.edu\/tag\/?p=223"},"modified":"2010-08-19T16:19:09","modified_gmt":"2010-08-19T20:19:09","slug":"meeting-summary-819","status":"publish","type":"post","link":"https:\/\/sites.scranton.edu\/tag\/2010\/08\/19\/meeting-summary-819\/","title":{"rendered":"Meeting Summary 8\/19"},"content":{"rendered":"<p>TAG met for the first time today and had a very productive meeting.\u00a0 Our main questions for discussion were the following:<\/p>\n<ul>\n<li>How do we set up lines of communication between the faculty and IR?<\/li>\n<li>How do we communicate with and solicit feedback from the faculty as a whole?<\/li>\n<li>How should we communicate within TAG?<\/li>\n<\/ul>\n<p>And here&#8217;s what came up in discussion&#8230;<\/p>\n<ul>\n<li>IT  Services has been focusing on pushing announcements through the my.scranton portal  (and then as secondary outlets, Bboard, mass emails to faculty). \u00a0Most  committee members agreed that neither my.scranton portal nor Bboard were  used frequently by faculty members.\u00a0 We discussed the bureaucratic limitations on mass email to faculty.\u00a0 One possible outlet for faculty communication could be a RoyalList specifically for discussion of tech issues.<\/li>\n<li>We noted that there&#8217;s an age\/ability divide among faculty on campus.\u00a0 Some might still want paper notices, and only about major IT outages, while others want to know every detail and want that information through Facebook\/Twitter\/other social media.\u00a0 How do we filter what&#8217;s relevant to faculty members and put it into terms they can understand?<\/li>\n<li>IR often has to make decisions based on meeting the needs of the majority of campus users, sometimes at the cost of convenience to a minority of users (e.g., less support for Macs on campus since fewer people use Macs).\u00a0 Often unified solutions that work campus-wide may not meet specific individual needs.<\/li>\n<li>Compromises often have to be made, since resources are limited.\u00a0 How do we explain these compromises to faculty? We can say &#8220;No&#8221; when we need to, but it should be phrased as &#8220;No, but here&#8217;s why not.&#8221;<\/li>\n<li>Faculty often feel like they don&#8217;t have input in IR decisions.\u00a0 Many times there is faculty representation on a product\/project committee, but other faculty don&#8217;t know about it and feel their voice isn&#8217;t being heard.<\/li>\n<li>Regarding the role of TAG &#8211; the group could serve as guinea pigs for testing out new classroom technologies.\u00a0 We should also be keeping eyes\/ears open for other faculty who are already doing this, and make sure we link to their presentations, notes, or syllabi to help other faculty learn from them.<\/li>\n<\/ul>\n<p>And here&#8217;s what we decided on as next steps&#8230;<\/p>\n<ul>\n<li>Set up RoyalLists for TAG-Members and TAG-Discussion, and invite any tech-interested faculty to join TAG-Discussion<\/li>\n<li>Create a New Technologies tab on the TAG website to start sharing information about which faculty are using new technologies in the classroom<\/li>\n<li>Invite 1st year faculty to join TAG-Discussion and give TAG feedback on the technology aspects of their transition<\/li>\n<li>Survey FT and PT faculty on how they&#8217;d like to receive IT updates (and why)<\/li>\n<li>Meet again after the survey results have been received and compiled<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>TAG met for the first time today and had a very productive meeting.\u00a0 Our main questions for discussion were the following: How do we set up lines of communication between the faculty and IR? How do we communicate with and solicit feedback from the faculty as a whole? How should we communicate within TAG? And [&hellip;]<\/p>\n","protected":false},"author":80,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[495],"tags":[535,622],"class_list":["post-223","post","type-post","status-publish","format-standard","hentry","category-tag-administrative","tag-communication","tag-meetings"],"_links":{"self":[{"href":"https:\/\/sites.scranton.edu\/tag\/wp-json\/wp\/v2\/posts\/223","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sites.scranton.edu\/tag\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sites.scranton.edu\/tag\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sites.scranton.edu\/tag\/wp-json\/wp\/v2\/users\/80"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.scranton.edu\/tag\/wp-json\/wp\/v2\/comments?post=223"}],"version-history":[{"count":0,"href":"https:\/\/sites.scranton.edu\/tag\/wp-json\/wp\/v2\/posts\/223\/revisions"}],"wp:attachment":[{"href":"https:\/\/sites.scranton.edu\/tag\/wp-json\/wp\/v2\/media?parent=223"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sites.scranton.edu\/tag\/wp-json\/wp\/v2\/categories?post=223"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sites.scranton.edu\/tag\/wp-json\/wp\/v2\/tags?post=223"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}