Tools & tool support
Download as PPT, PDF0 likes312 views
The document summarizes the notes from a team meeting about tools and tool support. It discusses the current LAMP environment and Drupal setup, challenges around server management, and governance around digital backup and monitoring. It also lists various tools currently used or being evaluated, and actions decided around focusing Drupal on content while using specialized third-party tools, expanding the scope of the tools blog, and evaluating specific tools like CRM systems, event management, and lead generation.
Tools & tool support
- 1. Tools & tool support Team meeting April 4, 11h00 – 12h00
- 2. The layers of a dynamic web presence Server 2-3 years LAMP environment 1-2 years Drupal version 1 year Site development 6-9 months Site management daily
- 3. Using a dynamic website Hosted, e.g. wordpress.com, edublugs.org No backup, no FTP, limited customisation, limited statistics Shared Untried, but unsuitable for primary websites Dedicated Full flexibility, but high cost of ownership
- 4. Challenges ‘Crash’ of the server Peak in traffic brings the server down Hack attack Usually on the eve before a long weekend Migration Slipstream of content and applications Who can you call if the site goes down Friday night?
- 5. The IT professionals perspective Everything going well = normal state Anything going wrong = #$%^&*@!?!!!
- 6. Current system Self-management through 2 moderation levels & internal support via tools blog Support by Edarta Tickets through Mantis 1 week response time, except blocking issues Development, server management & site maintenance by Edarta Hardware, backup, firewall, hosting by Combell
- 7. Governance Server monitoring Digital backup – daily weekly monthly Database dump to be set-up
- 8. Tools blog Support requests Discuss tools before adoption (not strategic aspects) E.g. need for CRM: planning blog (or partner blog) CRM tool: tools blog List adopted tools Random tool exploration
- 9. Other tools Email marketing: newsweaver, aweber Webmeetings: Adobe Connect Quiz: Articulate Webcasts: Articulate Bookmarking: diigo Blog promotion: feedburner Blog: Wordpress (edublogs) Project management: blogs, webexone DTP: Publisher, Quark Survey: Zoomerang Video Streaming: YouTube Microblogging: Jaiku Calendar: Google Geomapping: Clustrmaps, GoogleMaps, Platial to be defined CRM: Salesforce or 37signals Minute lectures: Slideshare & Scribd – to be defined Event management: to be defined Lead generation: to be defined Wiki: to be defined (wikimedia, google docs, …)
- 10. Tool proliferation The great thing about standards tools is that there are so may to choose from Each tool has a function and role to play Multiple tools for the same function would be good to avoid
- 11. A glimpse of the future Site-less web presence through Forums Syndication Social media Professional networks … LE Satellite presences may increase in importance (+) Xing, BlogActiv, WordPress.com, … (-) Facebook, GoogleGroups, YahooGroups, … (?) care2, wattwatt, …
- 12. Approach Use drupal for what it does best: content management, i.e. Create & manage content Tagging & RSS Navigation Adopt third party applications for other tasks, and integrate them as seamless as possible Use mainstream specialised tools, that are likely to emerge as the best in their category Avoid generic tools Simplification of tools, modules & content types
- 13. Actions / decisions OK for new approach to focus LE/drupal on content management, use specialised 3 rd party applications for the rest Tools blog (IHH): Extend scope to include interesting tutorials and videos Add links to relevant information sources Geomapping (IHH): Investigate & report possibilities for geomapping through GoogleMaps or Platial Intranets: Evaluate 37signals (Isabelle) Check ftp-upload capability (Hans) CRM: Potential interest from Isabelle, David Report outcome of 37signal/salesforce evaluation on tools blog (Hans)
- 14. Actions / decisions Event management (Hans) Report evaluation on tools blog, and propose tool to be adopted Lead management (Hans) Report result of docmetrics evaluation on tools blog, and set up session to discuss uses Minute lectures: we will use slideshare (Hans) EPQU editorial board: we’ll use a WordPress blog in combination with Scribd (Hans) A booklist of LE recommended books will be developed in Amazon and put on the planning blog (Hans, Isabelle) Animations will be revisited in a future session on e-learning (Hans) We will check modules and systems for user submissions, e.g. images, articles or case studies for a contest (Hans, Isabelle)