70 likes | 148 Views
Room 204 group. William Green (UT - Austin) (networking, sometimes devices on network, 4K iPhones on network) John Spadaro ( Brown)(enterprise exchange, biggest service active sync; Blackberry)
E N D
Room 204 group • William Green (UT-Austin) (networking, sometimes devices on network, 4K iPhones on network) • JohnSpadaro (Brown)(enterprise exchange, biggest service active sync; Blackberry) • Mairead Martin (PSU)(library applications on mobile devices, roaming reference for instruction, customization of applications for device) • Tim Sigmon(UVA)(no mobile app development, try to understand what we need to support vis-a-vis mobile devices, some work on mobile-device accessible websites) • Charlie Leonhardt(Georgetown)(not doing much in this area and need to) • Vijay Kumar (MIT) (how can we deliver good academic content on mobile devices) • Michael Gettes(MIT)(developing apps, SourceForge, laundry of apps, need to be enabled, have the money, need the talent) • Steven Sather (Princeton) (doing nothing, would like to be able to have MIT's calendars, maps, transferred to Princeton) • Sue Workman (Indiana)(in strategic plan, but don't have anything as yet; 9K iphone/ipodtouch, 1K blackberries; partnership coming in mobility space; want to get ERPs on mobile) • Ann Hill Duin (Minnesota) mobile initiative, what's our as-is architecture, look very closely at MIT, appreciated source code; my courses, system status • Deborah Keyek-Franssen (CU-Boulder) (no apps, support Windows Mobile and iPhone, some Blackberry for a while)
Key themes • Importance of mobile needs to be stressed. • Tremendous implications for educational delivery, mResearch, outreach, student services... • The opportunity is right for a shared service. • Not entrenched yet. • Nascent service; opportunity to develop and share it collectively as well as cost effectively.
Mobile “We” Proposal 1. Use MIT’s technical framework to bootstrap this effort collectively and locally • Source code is on sourceforge.net • Develop a cadre of expertise – Bootcamp this Fall (possible easy first win) 2. Develop a mobile working group (possible consortium) within higher ed; Mobile Education Services • Environmental scan • Architecture and roadmap • Infrastructure for enabling services and applications • Possible apps: library, registration, mobile CMS, campus maps, directory… • Possible models: membership subscription, outsourcing to pockets of expertise… • Vendor management
Additional points • Create innovation pipeline • Focus on core missions • Access and distribution of content • Align wireless expertise • Product cycles; seamless work • Focus on assessment and analytics • Employ Google analytics • Leverage other groups • Educause constituent group; mLearning
Points from large group discussion • many groups out there (ask Shel what they are); put this group together and create an app exchange, where students are developing the apps • if there was some consortial effort, would work with libraries to determine what apps to develop • differentiate apps that run a device vs. apps that run a service • Berkeley got out of mobile services for email, notify me service buy it as a service; need a notify.me for higher education