Your SlideShare is downloading. ×
it.emory.edu
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

it.emory.edu

4,914
views

Published on

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
4,914
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Wimba is a java-based online voice-recording solution. Although available as a standalone product, we have purchased and implemented it at Emory in an add-on version available to our faculty and students through Blackboard. Meets the need of creating simple audio learning materials within Blackboard without the burdens of copyright, analog digitization & streaming, or the steep learning curve of a new software tool. It is too early to tell what it has done to the learning process. The implementation is only 3 months old at Emory. Before Wimba, faculty and students were either: 1) recording *.wav audio attachments in  Learnlink emails or 2) reserving time in ECIT or Language Center to take analog voice recordings, digitize, compress, encode for Real  streaming, and add html code to Blackboard documents. Implementation date was early summer 2005. We did testing throughout  summer 2005. And full production went into effect beginning of Fall  semester 2005. However, it is important to note that all Blackboard  courses are not enabled for Wimba by default. We have been enabling  courses for Wimba on a case-by-case basis to allow for one-on-one assistance with the new service. I estimate that there are 4 or 5 language courses using Wimba at the  moment and possibly as many in other disciplines. It is too early to tell and you will see below that one of our challenges is metrics. expansion of the service in terms of use, but also in terms of breadth of use throughout disciplines. increase workshops and hands-on sessions for faculty and possibly work directly with a single class on using Wimba Wimba has the potential to become a widespread community-building  tool - its capabilities are similar to Learnlink, but using the recorded voice: single posts, email, threaded discussion, and live chat are all possible in Wimba
  • Transcript

    • 1. IT Briefing September 2006
    • 2. IT Briefing Agenda 9/21/06
      • SWE Updates
      • Manage IT Upgrade
      • Blackboard Overview
      • Web Approach
      • NetCom Q&A
      • Karen Jenkins
      • Karen Jenkins
      • Sandra Butler
      • Karen Jenkins
      • Paul Petersen
      • October 19 Briefing 10:15 – 1:30 – MS to attend:
      • 1 hour for Product Roadmap
      • 1 hour for Vista and Office 2007
      MS to provide lunch. Please RSVP to: sebreana.williams@emory.edu
    • 3. Software Express
      • Microsoft access
        • Student employees no longer given access
      • Sponsored accounts & retirees
        • No longer given access
      • Examining all applications against our contracts and will make adjustments accordingly
      • Any issues?
    • 4. Manage IT Karen Jenkins Andrew Kincaid Al Shelton
    • 5. Remedy Modules Action Request System Change Management Service Desk Service Level Management Asset Management
    • 6. Architecture
    • 7. Remedy Upgrade – Heads up!
      • Major new release v7.0
      • More ITIL compliance
      • Multi-tenancy
      • Additional categorization – from 3 levels to 6/7 (product & operational)
      • Cleaner look – left navigation & top navigation
      • Solutions/knowledgebase – added user flag
      • Definitive Software Library (DSL)
      • CMDB – with new tools to assist the build, graphical view
      • REMOVED the “teaser” apps
    • 8. Service Desk (Help Form)
      • New name for Help Desk module
      • Largest graphical change is top ITIL process bar
      • 2 types of Requests (ITIL compliance)
        • Incident
        • Problem
      • Task management added (use with incidents, problems, or change requests)
      • New canned reports
      • Enhanced problem management, new form
      • Work log renamed to Work Info (table based)
      • Other fields renamed (such as severity to impact)
      • Decision tree and scripts
    • 9.  
    • 10.  
    • 11. Change Management
      • Module now required to create any type of change request
      • More/tighter integration with Configuration Management, DSL, & CMDB
        • Closed loop change
      • Change calendar w/ business events
      • Set varying approval levels – even auto-approve – so process is not bogged down
      • Save high risk changes for CAB
    • 12.  
    • 13. Other Applications
      • Service Level Management
        • Ability to compute overall SLA compliance with multiple weighted targets
        • Performance targets via SNMP interface (SMARTS)
      • Asset Management
        • Better integration with Configuration Management (aka Marimba)
        • DSL contains a product dictionary
        • Software license management
    • 14. Input & Schedule
      • First TechTalk tomorrow 2:00-3:30 NDB 225 Kennesaw
        • 10/13, 11/3, 11/24
      • Will also updates at IT Briefing
      • Target installation => October
      • Go-live => TBD
      • Initial scope = migrate current functionality & data
    • 15. Manage IT ? Questions
    • 16. Blackboard @Emory Sandra Butler Manager, Interactive Technologies Team IT Briefing 09/21/06
    • 17. Interactive Technologies Team
      • Adam Lipkin
      • Marcy Alexander
      • Tricia Goddard
      • Kathy Hayes
      • David Lower
      • Julia Leon
      • Marianne Schneider
      • Open Slot
    • 18. Interactive Technologies
      • LearnLink
      • Blackboard
        • classes.emory.edu
        • [email_address]
      • Insight
      • Wimba
    • 19. What is Blackboard (Bb)?
      • Academic Suite
        • Learning System
        • Community System
        • Content System
      • Building Blocks
        • Add-ins that extend capability and functionality
    • 20. Bb Tools
      • Course and Content Authoring
      • Assessment Engine
      • Assignment Manager
      • Online Gradebook
      • Discussion Board
      • Email Class
      • Virtual Chat
      • Group Management
      • Course Reporting and Statistics
      • Performance Dashboard/Review Status (recent upgrade)
      more available via Building Blocks and Course Cartridges
    • 21. History: Bb at Emory
      • 1999: review Bb CourseInfo versus WebCT
      • teaching & learning at anytime from anywhere
      • 2000: University adopts Bb 5; upgrade to Course & Portal Manager
      • depts, orgs, and clubs; customizable buttons; building blocks announcement (Bb Inc.)
      • 2002: upgrade to Bb 5.5 Enterprise
      • Bb app server & Oracle db server; move to 24/7 data center; custom script for enrollment; Emory’s GenLib developers release e-reserves interface for Bb; branding
      • 2004: upgrade to Bb 6.1
      • LDAP enabled; PS feeds via Bb snapshot utility; dual servers in PROD and DEV
    • 22.
      • 2005: license Content System; SSL & load balanced; upgrade to Bb 6.2
      • file mgmt; content sharing; ePortfolios; passes to entire community and guests; Wimba Building Block trial
      • 2006: Reorganize / AAIT / ATS / Interactive Technologies
      • app system support transition; upgrade to Bb 6.3; RSPH migrates to University Bb servers; add’l training and outreach (ex. JIT sessions, custom training sites, etc.); increased non-academic and training usage; Wimba Building Block added
      • 2007: Enhance integration w/other IT resources
      • review overall structure: enhance processes; improve infrastructure
      History: Bb at Emory
    • 23. Bb at Emory Stats 09/18/06 2:00pm
      • 3,255 courses
        • 1,772 active courses (08/06 – current)
      • 163 organizations
        • 104 active organizations (08/06 – current)
        • includes intranets, student forums and groups, faculty/staff groups and committees
    • 24. Bb at Emory Stats 09/18/06 2:00pm
    • 25. Bb Course Site
    • 26. Building Block: Wimba Voice Tools
    • 27.  
    • 28. Bb & Insight integration made easy
    • 29. https://classes.emory.edu
    • 30. Proposed Web Approach September 2006
    • 31. Agenda
      • Current environment
      • Initial plan
      • Revised plan
      • Architecture goals
      • Draft architecture
      • Estimated timeline
      • Outstanding issues
    • 32. Gecko & Maple
      • Focused on the needs of the hard core developer community
      • Maple Issues:
        • Difficult to support & maintain due to multiple customizations (Apache, “ITD WebDrive”)
        • Security issues
        • Old hardware
    • 33. Initial Plan
      • Update hardware
      • Update software
      • But what are the most common needs of the community
      • Does this hit the mark …
      Stabilize, re-group, gather requirements
    • 34. Stabilize
      • Split SiteMinder / non-SiteMinder sites
        • Solved the performance issues identified in March ‘06
      • Upgrade CF to 7.1 (Maple)
        • Containment capabilities improve stability
        • Majority of code in CF – allowed for early testing prior to new architecture
      • Identify high risk security issues
        • Plan in place to implement changes
    • 35. Community Requirements
      • Developers only need a couple of additional features:
        • MySQL, shell access on Dev, stability
      • Resource and/or skill set constrained users are the majority
        • Analysis indicates there are many static sites and others with basic/common minor dynamic components (~77%)
      • One size does not fit all …
    • 36. Revised Plan
      • Place focus on the majority and the current gaps
      • Build a tiered service offering
        • target different customers/needs
      • Build tool kit for common needs
      • Provide more applications
      • Improve documentation
    • 37. Web Approach
      • Standard Hosting
        • Users with limited resources needing to quickly and easily publish static websites
      • Advanced Hosting
        • Users with advanced developments skills creating dynamic sites and/or web applications
      • Enterprise Hosting
        • Users creating mission critical enterprise websites and/or enterprise web applications
      Tiered service offerings dependant upon user needs
    • 38. FUTURE STATE
    • 39. Hosting Options Web Workshops Service & Support Assigned POC High avail. System admin. Proactive Monitoring Server maint. Backup/Restore Enterprise Advanced Standard
    • 40. Hosting Options (cont.) Features & Tools Virtual servers Error/log files Google search Site statistics Script library Site builder Templates Enterprise Advanced Standard
    • 41. Hosting Options (cont.) sFTP 2 GB 1 GB 500 MB Disk space Features & Tools (continued) Dev-to-prod Dev/QA Env. Cronjobs SSH (dev) File Manager Enterprise Advanced Standard
    • 42. Hosting Options (cont.) Site & Application Development SiteMinder J2EE Python 2.3 Perl 5.8 Cold Fusion 7.1 PHP 4.3.2 HTML Enterprise Advanced Standard
    • 43. Hosting Options (cont.) Database Development RAC JDBC Microsoft SQL MySQL Oracle Cold Fusion Connectors MySQL Oracle Enterprise Advanced Standard
    • 44. Hosting Options (cont.) Applications Portal CMS Message Board Calendar Blog Enterprise Advanced Standard
    • 45. Architecture --DRAFT--
    • 46. Architecture Goals
      • Low entry-barrier
      • Consolidate where possible
      • Improved isolation / management
      • Seamless scalability
      • Highly secure
      • High stability, availability, and performance
    • 47.  
    • 48.  
    • 49. Project Scope Phase 1 and beyond
    • 50. Project Scope
      • Design & implement new robust web infrastructure
      • Create mandatory tools
        • Administration/provisioning
        • File management
        • Necessary scripts for Standard
      • Improve existing documentation
      • Migrate current Maple sites
        • AAIT to move sites and test
        • AAIT to create required documentation
        • Site owners to test & validate
    • 51. Tools
      • Phase 1
      • File Manager
      • Administration / Provisioning
      • Form mailer
      • Phase 2+
      • Site Builder
      • Templates (with DUR)
      • Dev-to-Prod
      • Point & Click provisioning
      • Event list
      • Other tools
    • 52. More Out of Scope (Phase 2+)
      • Migrating Gecko to Enterprise
      • Create policies (in conjunction with DUR)
      • Applications
        • Blog
        • Calendar
        • Message board
        • CMS
        • Portal
      • Policy central store
    • 53. Other related projects
      • Web Statistics (Governance request submitted)
      • Google Search (Governance request submitted)
    • 54. Phase 1 Timeline - DRAFT Finalize architecture Implement Hardware Create tools Migrate sites Test & acceptance Production ready Sept Oct Nov Dec Aug
    • 55. Phase 2 Schedule - DRAFT Site Builder Templates Dev-to-Prod Provisioning Event List Gecko Migration Jan Feb Mar Apr Dec
    • 56. Outstanding issues
      • Finalize architecture
      • Determine hardware
      • Identify costs
      • Present & discuss with community
      • Complete & submit Level 1 CBC
    • 57. Web Services ? Questions
    • 58. NetCom ? Questions