Monday, December 22, 2008

Online Conference (Inteview) Summary

Good thing: we did the interview
Learning point: be in a good reception area, segment recordings and make summary notes as you go.

We covered a number of things in the interview. It was conducted through Skype, and recorded, edited and exported with Audacity
( The following is a summary of all points from the interview. There is a powerpoint on the interview here on SlideShare (
The sound files of the interview have been edited for reasons of size, quality and topical accuracy (i.e. we talked about the rugby for some of it)
The links for the sound files are on this site here, on the right hand block and can be clicked to load and play - be patient, as they are between 20 to 56MB!
There are movies of the powerpoints on YouTube here

The Process used by BISAM
  1. Client describes the problem or issue
  2. BISAM seeks client ideas about solutions that would suit their industry
  • CLIENT has; big idea about industry, small ideas about IT solutions
  • BISAM has; small ideas about the industry, big ideas about IT solutions
  1. Provide general advice, book further time for more detailed solutions
  2. Google potential solutions, speak with other experts
  3. Gain clarification, increased understanding from client of issues in the industry
  4. Produce a brief of tools for potential solutions, alternatives from present practice
An example from the Print industry was used, describing the need for online ordering. The client thought they would use
  1. Scan and email solutions was proposed by client
  2. BISAM provided an online option, capturing bookings and provide a ‘proof’ for customers online
The outcome provided greater effectiveness (quality/milestones achieved), efficiency (time/dollars) then expected by the client.

The use of Open Source solutions
We covered:
  1. Open source verses freeware
  2. Open source software can be developed feely
  • Start a community on the new development
  • Grow a base of developers
  • A completely different product may result
The Mambo vs. Jooma was given
It was suggested business models can be built on the strategic vision of company, rather than the commercial boundaries set by non-open source owners
The role of community in developing open source software was highlighted
The CINDEOS CMS vs. site@schools example was given
The real power of open source software is the quality of what can be created and the specialisation it can achieve, and can rival commercial products due to user input being extensive, with precise feedback that is implemented.

The use of Drupal as a CMS
Key Points
  1. Straight forward to install
  2. Easy to use, intuitive to create content and modify
  3. Cost effectiveness of set up and ready to go being $300 to $500 in total Iincludes following)
  • Users set up
  • Themes and modules and plug ins installed and ready to go
  • Ready to use
This was a direct set of questions from a FOC08 member
Drupal installs have organic groups, though do need more precise control levels of page development
Jooma as an alternative was discussed, not as powerful for collaboration as Drupal.
Jooma has attractive templates that look clean, slick, tidy.
The time commitment needed to keep a Drupal website looking good is a factor
Commercial use of Drupal by very large publishing and media organisations (Fast Company)

The Updates Issue
Managing updates – be mindful of...
  1. Compatibility with content
  2. Time consuming compared with initial install
  3. Security updates could be a lower level of priority
  4. Back ups of users and content is highly important – of the server and a local back up
  5. Must-have updates should be done keep things cost effective

The update cost can be reduced by only installing updates that provide both functionality and security revisions

Organic Groups in Drupal
Organic groups with Drupal
  1. Self developing, maintaining, enabling
  2. Set authority levels, authentication
Wikis provide the opportunity for people to:
  1. Contribute ideas, learning, experiences
  2. Add, Modify, Share contributions on a global platform
Wikis may contain a variety of contributions:
  • Subjective thoughts on topics or events, Perceptions or viewpoints, Perspectives and opinions,
  • Facts – verifiable information with dates, times, events, people and contributions that can be substantiated
Wikis can track how the contributions have developed over time:
Versions showing how alterations were made; like an editing track
  • History – showing who, what, when, how and possibly why changes were made
  • The capability to refer back to previous versions to identify the workflow and
  • To understand the development of knowledge as a whole

No comments: