Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Daisy: CMS or Wiki?


Published on

Peter Dykstra

Published in: Technology
  • ★★ How Long Does She Want You to Last? ★★ A recent study proved that the average man lasts just 2-5 minutes in bed (during intercourse). The study also showed that many women need at least 7-10 minutes of intercourse to reach "The Big O" - and, worse still... 30% of women never get there during intercourse. Clearly, most men are NOT fulfilling there women's needs in bed. Now, as I've said many times - how long you can last is no guarantee of being a GREAT LOVER. But, not being able to last 20, 30 minutes or more, is definitely a sign that you're not going to "set your woman's world on fire" between the sheets. Question is: "What can you do to last longer?" Well, one of the best recommendations I can give you today is to read THIS report. In it, you'll discover a detailed guide to an Ancient Taoist Thrusting Technique that can help any man to last much longer in bed. I can vouch 100% for the technique because my husband has been using it for years :) Here's the link to the report 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Daisy: CMS or Wiki?

  1. 1. Copyright (c) 2007 Peter Dykstra 1Copyright (c) 2007 Peter DykstraDaisy: CMS or Wiki?Open Source Case StudyPeter Dykstrapeter.dykstra@verizon.netSTC-Philadelphia Metro ChapterAnnual ConferenceMarch 17, 2007Copyright (c) 2007 Peter DykstraWhat’s a Wiki?First introduced in 1995Server-based software, allows discussion /collaborationDistinguishWikiBlogForum
  2. 2. Copyright (c) 2007 Peter Dykstra 2Copyright (c) 2007 Peter DykstraOriginal Definition“The simplest online databasethat could possibly work.”- Ward Cunningham(inventor)Source: (c) 2007 Peter DykstraWiki characteristicsAllow users to freely create and edit WebcontentUse any Web browserSimple text syntax (HTML not required)Cross links(source:
  3. 3. Copyright (c) 2007 Peter Dykstra 3Copyright (c) 2007 Peter DykstraEffect of WikisPowerful and subtle effects of Open EditingEveryday users can edit any pageEncourages democratic usePromotes content composition bynontechnical users(source: (c) 2007 Peter DykstraCompare: Wiki vs CMSWikiBottom-up approach to structure andnavigationAbout empowering usersCMS (Content Management System)Top down approval / coordinationAbout managing content efficiently followinga set of rules
  4. 4. Copyright (c) 2007 Peter Dykstra 4Copyright (c) 2007 Peter DykstraSimilaritiesCan use the same technologyWikis require SOME central managementSimilar user needsEdit rightsEase of useCopyright (c) 2007 Peter DykstraDifferencesSocial and governance modelDEGREE of control -- continuumNeed to control / identify the source /speak with one voice?Specialized publishing roles?
  5. 5. Copyright (c) 2007 Peter Dykstra 5Copyright (c) 2007 Peter DykstraOriginal WikisSimple storage, files stored in serverdirectoriesOne copy, no versioningIssues:SprawlHard to navigate random structuresNo process for keeping text updatedNo edit history / trackingCopyright (c) 2007 Peter DykstraNewer WikisThousands of pagesWikipedia English version = 1,688,000+ articles (3/16/07)More formal governance modelsDatabase back endsVersioning, tracking, and rollbackSpecialized administrator rolesStart to look more like a CMS
  6. 6. Copyright (c) 2007 Peter Dykstra 6Copyright (c) 2007 Peter DykstraIntroducing DaisyCMS-based WikiHigh-end featuresOpen Source / Standards-basedFree to use and distribute (“Apache-style”license)Some tech requiredCopyright (c) 2007 Peter DykstraWhere’s it from?OuterthoughtSmall co (3-4 developers) in BelgiumGovernment fundingConnections to Apache Software FoundationTwo levels of supportOpen Source community (free)Outerthought Support contract ($)
  7. 7. Copyright (c) 2007 Peter Dykstra 7Copyright (c) 2007 Peter DykstraApache Software FoundationKnown for Apache Web browserSupported by major software cosSun, IBM, HP, etc.Open licensing modelJava-basedWeb / XML / XSL focusCopyright (c) 2007 Peter DykstraDaisy TechnologyIntegrates Apache componentsCocoon Web publishing frameworkLucene search engineMessagingUses MySQL Open Source databaseAdds a content repository and editor
  8. 8. Copyright (c) 2007 Peter Dykstra 8Copyright (c) 2007 Peter DykstraTwo main parts of DaisyFront end: Daisy WikiXML-based publishingBrowser-based wysiwyg editor for htmlBack-end: CMS repository“Daisy HTML” document formatStore other file as attachmentsExtensible (XSL, CSS, JavaScript, Java)Copyright (c) 2007 Peter DykstraDaisy architectureRepository WikiAPI
  9. 9. Copyright (c) 2007 Peter Dykstra 9Copyright (c) 2007 Peter DykstraDaisy architectureRepository WikiAPIWebsite(s)Copyright (c) 2007 Peter DykstraRepositorySingle ‘big bag’ of documentsVersioned documents / diffsMetadata as document fieldsDefinable document typesAll communication via API
  10. 10. Copyright (c) 2007 Peter Dykstra 10Copyright (c) 2007 Peter DykstraRepository featuresTwo main document formats‘Daisy’ HTML subsetAttachmentsFull-text search (html, doc, xls, pdf, txt)Authorization/RolesQuery languageSubscribe to event notificationCopyright (c) 2007 Peter DykstraDaisy WikiStandalone applicationWysiwyg HTML editorSupports multiple “sites” from one repository,based on metadataVirtual document hierarchies derived frommetadata + rulesBook publishingBuilt using the Cocoon framework
  11. 11. Copyright (c) 2007 Peter Dykstra 11Copyright (c) 2007 Peter DykstraWhat’s Cocoon?Apache projectWeb publishing / application frameworkProvides XML processing on the serverSupports the WikiCan be used to build Web sites using therepositoryCopyright (c) 2007 Peter DykstraSample Cocoon processingSource files(Daisyrepository)SitemapXSL Stylesheetlibrary1. User enters requestfor “sample.html”.2 Sitemap sees“*.html” …Match=“*.html”Sample.xml3. …gets “sample.xml”…4. …transforms it usingxml2html.xsl…5. …and sends“sample.html” back tothe user.A sample pageThis content for this page is in anxml file. The html file doesn’t existuntil someone asks for it.The user never sees the xml.xml2html.xsl
  12. 12. Copyright (c) 2007 Peter Dykstra 12Copyright (c) 2007 Peter DykstraGoal: “Separation of Concerns”Cocoon’s architecture separatesProgram logicContentVisual style / brandingSite managementso they can be managed independentlyCopyright (c) 2007 Peter DykstraOfficial Daisy site (shows the Daisy Wiki)
  13. 13. Copyright (c) 2007 Peter Dykstra 13Copyright (c) 2007 Peter DykstraDaisy Wiki (Modified styles)Copyright (c) 2007 Peter DykstraDaisy Wiki
  14. 14. Copyright (c) 2007 Peter Dykstra 14Copyright (c) 2007 Peter DykstraDaisy WikiCopyright (c) 2007 Peter DykstraDaisy Wiki
  15. 15. Copyright (c) 2007 Peter Dykstra 15Copyright (c) 2007 Peter DykstraDaisy WikiCopyright (c) 2007 Peter DykstraDaisy Wiki
  16. 16. Copyright (c) 2007 Peter Dykstra 16Copyright (c) 2007 Peter DykstraDaisy WikiCopyright (c) 2007 Peter DykstraDaisy Wiki
  17. 17. Copyright (c) 2007 Peter Dykstra 17Copyright (c) 2007 Peter DykstraOur ExperienceCopyright (c) 2007 Peter DykstraOur ExperienceSetupConfigurationInfrastructureAuthor trainingSample projectUser responseOpen issues
  18. 18. Copyright (c) 2007 Peter Dykstra 18Copyright (c) 2007 Peter DykstraSet up (test environment)Install on a standalone PCDownload and install JAVADownload and install MySQLDownload and configure DaisyStart upEstimated time: 1-3 hoursCopyright (c) 2007 Peter DykstraConfigurationModify logo, fonts, colorsDefine desiredDocument typesFields and field values (metadata)Sample documentsSet up “Collection” for each work groupSet up “Site” for each content area
  19. 19. Copyright (c) 2007 Peter Dykstra 19Copyright (c) 2007 Peter DykstraInfrastructureTwo stages (after test install on a PC)Pilot server installation with IT groupProduction server installationLDAP directoryBackupsCopyright (c) 2007 Peter DykstraAuthor trainingAppointed one editor / trainerRequires some understanding of HTMLCreated company-specific document typesOne-on-one training sessions with authorsSupport for problem resolution
  20. 20. Copyright (c) 2007 Peter Dykstra 20Copyright (c) 2007 Peter DykstraSample projectDeveloper’s LibraryArchitecture documentation for developmentgroupWiki style documentsPDF / Word / Visio, etcCopyright (c) 2007 Peter DykstraResultsEnthusiastic sponsorship by technical managersParticipation by content ownersWith editorial support: Full participationAs authors: Limited participation (slowly expanding)Built library of 1500+ documents across 10+ teamsHigh level of awareness/use by ‘consumers’Easy browse/search is key factorRated as successful at building commontechnical understanding
  21. 21. Copyright (c) 2007 Peter Dykstra 21Copyright (c) 2007 Peter DykstraAssessmentOn the one handDocuments are centrally accessibleSite structure is intuitiveTools are accessible, easy-to-useWikis are coolOn the other handDoc creation/editing is still by a limited groupSome HTML knowledge requiredEditorial support is still importantCopyright (c) 2007 Peter DykstraGeneral experienceEasy to train interested authors who havebasic Web/HTML understandingAuthors can manage contentSome editing was neededMain success factor is ability to writeclearly
  22. 22. Copyright (c) 2007 Peter Dykstra 22Copyright (c) 2007 Peter DykstraLessonsCopyright (c) 2007 Peter DykstraOpen Source LessonsOpen Source software can be powerful androbustIt provides a hands-on way to learn aboutCMSUse in the right business context can providesignificant benefitsOrganizational learning curveOne size doesn’t fit all projects
  23. 23. Copyright (c) 2007 Peter Dykstra 23Copyright (c) 2007 Peter DykstraSoftware is not the solutionAn Enterprise CMS system has to beintegrated into the workflow of anorganizationClear goals and requirementsDefined rolesNeeds to present itself differently to differentusersCopyright (c) 2007 Peter DykstraContent issues varyVery different requirements and successcriteria forInternal Wiki / IntranetExternal Web siteOffice document management
  24. 24. Copyright (c) 2007 Peter Dykstra 24Copyright (c) 2007 Peter DykstraConclusionsOpen Source may be the right choice for someRobust core featuresFlexible, extensibleParticipate in the communityNo license feesRough edgesRequires expertiseInformation ArchitectureInfrastructure managementApplication configurationCopyright (c) 2007 Peter DykstraConclusionsNot freeRequires business and technicalSkillsTimeDevelopment and support depend on anexternal communityFeature gaps may require development
  25. 25. Copyright (c) 2007 Peter Dykstra 25Copyright (c) 2007 Peter DykstraVendors offerGuidanceBroad and deep experienceRicher feature setsSupportCopyright (c) 2007 Peter DykstraDaisy StrengthsIntegration of industrial strength componentsVersioned document modelSeparation of concernsvisual designcontent creation/editingsite logicRepository architectureOpen standards-based design
  26. 26. Copyright (c) 2007 Peter Dykstra 26Copyright (c) 2007 Peter DykstraRecommendationsGood learning projectReady for medium-size applicationsGood for managing technical documentsRequires fairly technical orientationCopyright (c) 2007 Peter DykstraLinks / ContactsOuterthought / Daisy