N I S D Moodle 411 Final 4

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    1 Favorite

    N I S D Moodle 411 Final 4 - Presentation Transcript

    1. Moodle Administrator’s 411 System design and requirements, administration tasks, challenges and strategies for success! Northside ISD, San Antonio Amanda Hefner , Academic Technology Analyst Lisa Gerlich , Technical Manager Jenny Yim , eClasses Project Manager, Online Staff Development Aldine ISD, Houston, Texas Raylene Truxton , District Coordinator for On-line Learning
    2. Presenter Profiles
    3. District Profiles
      • NORTHSIDE ISD
      • Large school district
      • Over 12,000 Employees
      • Over 88,000 Students
      • ALDINE ISD
      • Large school district
      • 8,000 Employees
      • 60,000 Students
      • 82% At Risk
      • Primary Moodling:
        • Staff Development
        • Virtual School
        • Credit Recovery
    4. NISD Moodles 2109 Users/Mostly Students Will have 700 Students 10,222 Users/All Staff 11540 Users/All Staff
    5. Moodle Instances & Admins
      • NORTHSIDE ISD (Internal)
      eCLASSROOM Hybrid & Online HS Courses eLEARN Professional Tech . Development eCLASSES Professional Development eCOMM Public Courses & Outreach NTSC New Teacher Training SANDBOXES (7+) 1 x Each Instance + New Version Tests 2 SYSTEMS ADMINS 40% 1 SITE ADMIN 70% 1 SITE ADMIN 70% Just Launched http://Parent411.nisd.net
    6. Aldine ISD Moodles
    7. Moodle Instances & Admins ALDINE ISD (Hosted) AISD ONLINE Hybrid & Online HS Courses VIRTUAL SCHOOL Online HS Courses SANDBOX Hybrid & Online HS Courses 2 SITE ADMIN 70% 3 rd PARTY SYSTEM ADMIN (Remote Learner)
    8. Recommended Reading Moodle Administration By Alex Büchner An administrator's guide to configuring, securing, customizing, and extending Moodle http://www.packtpub.com                              
    9. What’s IN the Book? > What’s NOT In The Book??
      • Admininstrator Skills & Tasks Getting Started Tasks
      • Administrator Tasks & Recommended Skillset
      • Getting Started Tasks: Installation, Planning Updates, Backups, etc.
    10. Administrator Role & Responsibilities
      • Work closely with Admins of IT systems, databases, & networks
      • Provide access & permissions to users
      • Provide facilities for effective online instruction and communication.
    11. Main Admin Tasks
      • User Account Management
      • Course/Category Management
      • Module Management
      • Interface & Theme Design
      • Year-start & -end Maintenance
      • Network Instances
      • User Support (staff & learners)
      • System Security, Performance, & Stability
      • Site & Course Backups
      • Monitoring & Reports
      • System Maintenance & Upgrades
    12. Recommended Skill Set:
      • a Technical background
      • some system or database administration knowledge
      • working knowledge of operating system , underlying DATABASE , network , and other components
      • PHP, HTML, and CSS programming knowledge
      • It is not necessary to be an expert in these areas. However, a general understanding, ability to search online sources for solutions, modify existing code, and write query statements will be most beneficial.
      • There’s plenty of books to get started!
    13. New Hire Test Questions MySQL Statements PHP Code
    14. Getting Started…
    15. Installation & Setup
      • Installation Considerations
      • Flexibility - How much control do you want/need?
      • Scalability - How many concurrent users?
      • Cost - Do you have infrastructure, people, and resources for in-house?
      • In-house expertise
      • Compatibility with legacy systems
      • Existing resources
    16. Version Level Updates
      • Backups
        • Make System Level copies of:
          • Moodle software directory – code and config files
            • Set in php.ini
          • Data directories – course & site content files
        • Mysql Database – mysql dump
        • Be sure to do all Individual Course Backup before upgrading
    17. Version Level Updates
      • Test Updates in a Sandbox Environment
      • Take your time!
        • Have a sandbox instance of the new version so people can test migration of critical courses and fix problems before the update
      • Expect the Unexpected
        • Problems may still arise due to:
          • How a certain module is used differently by various teachers
          • Add-on modules may be written for different core versions
    18. Version Level Update Methods
      • Decent Method
        • Rename old core folder
        • Install new core – not over the old core!
        • Copy any customized files such as config.php, customized themes, and local language packs
        • Install add-on modules
        • Deal with any customizations you have done to the moodle code
    19. Version Level Update Methods
      • Better
        • Use CVS
        • PLAN AHEAD! Must initialize existing core version with CVS before new version can utilize CVS to upgrade
        • During the install the CVS method will detect any changes you have made to the code and save the file as .# filename.version
    20. Version Level Update Methods
      • Best
        • Utilize Moodle-Net
        • Have the old instance and the new instance in the same moodle-net
          • This will allow a gradual migration of courses to the new version (1 at a time for verification)
        • Delete the old instance once all the courses have been migrated
    21. Category & Course Mgmt.
      • Set views for Guest & Authenticated users
      • Hide Guest Access button if authentication required
      • Set permissions for Category creation
        • only Admins manage top-level categories; Creators & Teachers manage sub-categories
      • Metacourses as "libraries" for shared resources
      • “ Sandbox” courses for each new teacher/creator
        • Issue: Many Sandboxes abandoned, but still backed up on server for months...
      • Enforce Course Enrollment Key requirement
    22. User Management
    23. User Management & Profiles
      • Profile Management
        • Pre-populate fields with external DB, such as LDAP
        • Lock fields
        • Bulk Upload data & photos
          • Caution – when linking to external systems with varied data structures
      • SITE Authentication vs. COURSE Enrollment
        • Be aware of Site Users that are NOT Enrolled !
    24. Forms of SITE Authentication
      • Manual Authentication (by Admin)
        • Add Individual Users (fake or guest accts.)
        • Bulk-Upload Users & Photos
        • Self-Registration by Email Confirmation
      • LDAP Server Authentication
      • External Moodle or Database Authentication
      • Internal Moodle Authentication
        • No Login  -  to suspend user accounts
        • No Authentication  -  anyone can enter the site
        • MoodleNet  -  user auth. is passed from one instance to another
    25. Forms of COURSE Enrollment
      • Internal (by Teacher)
        • Manual role assignment in a course
        • Course Enrollment Key (1 per course)
        • Group enrollment keys (many per course)
      • Database-driven Enrollment
        • LDAP
        • External DB source
        • Flat File
        • IMS Enterprise File
      • Paid Enrollment (PayPal, etc.)
    26. Enrollment Keys : 1 Course Single Course Key Separate Group Keys in Same Course (Recommended)
    27. Look & Feel
    28. Look & Feel
      • Front Page Customization
        • Guest User View vs. Authenticated User View
        • Assign a Front Page designer
        • Force My Moodle entry page
      • Moodle Themes
        • Set Themes by Site, Category, Course, User, Session (preview)
        • Skills for Modification:  HTML, PHP, CSS
        • Recommendation: Stick to "standard-based" themes for compatibility
      • Course Design / Organization
        • Provide course design templates (empty course backup) for teachers
          • Teachers simply restore as a new course
        • Publish a design guide to include tips on:
          • Avoid DIRTY CODE caused by copy/pasting from Microsoft apps  >:(
          • Improve File Size & Optimization
          • Methods for Adding Media - size, conversions, link/embed/insert...
          • Copyright / TOU Policy - institution v. individual's copyrights
    29. DIRTY CODE!
    30. Security
    31. Security Beyond The Moodle Instance
      • HTTPS Logins
      • IP Based Firewalls
      • Rule Based Appliances that watch the network for attacks
      • ModSecurity: an open source web application firewall that detects and prevents attacks before they reach web applications
        • Installed as an Apache plugin on individual servers
        • Standalone Appliance for larger installations
      is an open source web application firewall
    32. Site Configuration
      • Accessibility
        • Code in Standard
        • Theme Screen readers
      • Localization
        • Languages, Time Zones, etc.
      • Module Configuration
        • Activities, Blocks, Filters
        • Test with Debugging
        • Check compatibility with core version
      • Filters
        • Applied top-down – bad sequence can cause issues
        • Test filters on Everything!
      • Grades & Gradebook settings
      • Language Packs
        • Editing strings
        • Tracking editing strings for upgrades (save “en_local” files)
    33. Test the Filters on Everything! EXAMPLE: Word Censorship Filter scanned 3 of 4 modules correctly….Oops!
    34. Need to Know: Communication Paths EXAMPLE: Which modules use the mail server?
    35. Who can email/chat/IM who…? Need to Know: Communication Paths
    36. Need to Know: Communication Paths
    37. Monitoring & Reporting User Activity
    38. Tracking Bugs with Moodle
      • Moodle “Tracker” Module
      • Allow users to post support requests
      • Delegate to System/Site Admins
      • Maintain record of changes/fixes
    39. Tracking Bugs with Moodle
    40. Monitoring User Activity
      • Moodle Activity Reporting
      • Datasets:  Who (user), What (action), When (timestamp), Where (IP address)
      • Activity Logs - by Site, Course, User, Activity (assignment)
      • Statistics - calculated views/posts by Site, Course, Teacher, Students
      • 3rd Party Reporting Tools
      • Google Analytics
      • Navicat for MySQL
    41. Reporting with Moodle
      • Moodle Activity Logs & Statistics
    42. Reporting with Navicat
      • Relational DB Design > Reports
    43. Navicat: The Truth Serum
      • Teacher reports a student's file is missing, but log shows user uploaded
        • Checking the MoodleData folder for the course reveals the file was present, but a data error occurred on upload timestamp...
      • Teacher reports students have lost content on their wiki pages
        • Wiki history is extensive, so SQL export of wiki page content reveals copy/paste from MS Word has dirty HTML code interfering with content presentation.
    44. Navicat: The Truth Serum
      • Teacher notices student work is turned in from IP address other than District's and during class hours.
        • IP Address happens to match Mom's workplace, and timestamps match student's 3rd period History class...
      • Student insists they have read all material and turned in projects
        • Student Profile Log shows student's last access was 13 days ago...Activity Log shows student never accessed the page
      • Student reports they attempted to log in 20 times between 8:00AM and 10:00AM
        • Site Error Log reveals that only 3 unsuccessful logins occurred during that timeframe, only one username matching theirs.
    45. Performance Optimization
    46. Hardware Resources
      • Get as much memory as possible – have as much RAM as your hardware will allow, as your operating system can use and your boss will buy
      • The more RAM your system has, the more processes [and threads] Apache can allocate and use; which directly translates into the amount of concurrent requests/clients Apache can serve
      • Larger installations will want to put the database on a separate server
      • One database server can be used for many moodle instances
    47. Performance Tools
      • ApacheTop
        • http://freshmeat.net/projects/apachetop/
      • MySQLTuner
        • http:// MySQLTuner.com
      • Web Application Stress Testing
        • http://www.webload.org/
    48. Apache Performance
      • The big question:
        • How many child processes should be kept active while waiting for requests?
      • Considerations
        • Each child process consumes a certain amount of memory
        • Each child process only accepts on connection at a time
        • There is overhead when a new child process is spawned
      • MaxClients
        • Limits the number of children Apache spawns to handle requests
        • Set to the number of child processes the servers memory can handle. Be sure to leave enough memory for the operating system and other processses
      • MaxSpareServers
        • How many “extra” httpd processes are allowed to live to be ready to service requests
      • MinSpareServers:
        • What is the minimum number of spare httpd processes
        • Should be a number high enough to satisfy sudden bursts of requests
    49. PHP Acceleration
      • Moodle is written in php
      • A PHP accelerator is an extension designed to boost the performance of software applications written using the PHP programming language
      • PHP Acceleration caches the compiled PHP script in memory instead of parsing and compiling source code on each request
      • There are many PHP accelerators available
      • We use xcache http://xcache.lighttpd.net/
    50. … CONTACT US…… Northside ISD, San Antonio Amanda Hefner , Academic Technology Analyst [email_address] Lisa Gerlich , Systems Administrator [email_address] Jenny Yim , eClasses Project Manager, Online Staff Development Aldine ISD, Houston, TX Raylene Truxton , District Coordinator for On-line Learning [email_address]

    + mguhlinmguhlin, 9 months ago

    custom

    644 views, 1 favs, 1 embeds more stats

    A copy of the slideshow shared by the incomparable more

    More info about this presentation

    © All Rights Reserved

    • Total Views 644
      • 617 on SlideShare
      • 27 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 4
    Most viewed embeds
    • 27 views on http://www.mguhlin.org

    more

    All embeds
    • 27 views on http://www.mguhlin.org

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories