2012 Enterprise Wiki Almanac
•Als PPTX, PDF herunterladen•
3 gefällt mir•750 views
A practical guide for the Enterprise Semantic MediaWiki gardener
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Empfohlen
Empfohlen (20)
2012 Enterprise Wiki Almanac
- 1. 2012 Enterprise Wiki Almanac A practical guide for the Enterprise Semantic MediaWiki gardener SMWCon Spring 2012 Laurent Alquier, Janssen Pharmaceutical Companies of Johnson & Johnson
- 2. 12 steps to grow a better Enterprise Semantic MediaWiki
- 4. January - Take a fresh look
- 5. Adapt the skin to your environment
- 6. February - Make it warm and cozy
- 7. Every little details count
- 8. March – Make it fit
- 10. April – Let birds of a feather flock together
- 11. Easier feedback and sharing
- 12. May - Make it grow quickly
- 14. June - Edit, trim and feed
- 16. July - Develop a robust structure
- 17. Plan, review semantic relationships Image – VisLink: Revealing Relationships Amongst Visualizations” by Christopher Collins and Sheelagh Carpendale
- 18. August – Watch your content mature
- 20. September – Harvest time
- 21. Use queries to highlight content
- 22. October - Stay organized
- 24. November – Give thanks
- 26. December - Plan for the next freeze
- 28. Conclusion Questions ? Contact lalquier@its.jnj.com
Hinweis der Redaktion
- This talk is about lessons learned while trying to grow a wiki in an enterprise environment.Caring for a wiki is similar to caring for a garden. An almanac felt like a good choice for a compilation of lessons learned.
- Aesthetic, Flexibility and Structure.Encourage people to come backAdapt to changing situationsPrevent chaos from setting in
- Capture conceptsAnswer questionsWhat Where Who Keep scope generic (table of content of where is what in J&J)See: http://semantic-mediawiki.org/wiki/KnowIt
- Keep only what is necessary and hide the rest.
- Dissect MediaWiki SkinsLearn jQueryDiscover Bootstrap Plan for multiple devicesBrowsers supportResponsive design Mobile skinTwitter Bootstrap: http://twitter.github.com/bootstrap/index.html
- Ease people into using the wikiMake it consistent Make it familiar
- BrandingName / Logo / cardsUse local vocabularies‘Rename’ instead of ‘Move‘‘Alert’ instead of ‘Watch’‘Refresh’ instead of ‘Purge’
- Think about how wiki fits in its surroundings
- From integration issues down to rules and regulations.
- Social aspects are important – remove obstacles to sharing between users
- I Like Favorites ContributionsBetter comments / better page toolbarTwitter icon by Kevin Flahaut - http://weblog.404creative.com/2008/12/20/free-vector-twitter-icons/
- Provide options to import content quickly
- Submit process Bookmarkletspopup formData transfer updatesImport from other sources (forum pages, publications)
- WidgetsWP style shortcodesMarkitup editor
- A semantic wiki is only as strong as the relationships and properties defining it.
- One category per pageEverything else through propertiesStandard properties : Description, Topics, Scope, Image, URL
- Once all these steps are covered, watch content evolve carefully
- Tags in separate namespaceUse reports to detect inconsistencesUse bots to clean things upNeed better queries for related pages
- Time to collect the fruits of all that labor – queries… and hopefully, insights
- Saved queries Semantic search SPARQL and RDF store options for SMW : http://semantic-mediawiki.org/wiki/SPARQL_and_RDF_stores_for_SMWHTTP gateway to contentInline display of resultsExport to XML, JSON, TXT, CSVExtension : http://www.sensordatalab.org/wiki/index.php5/Extensions:Sparql_Query
- No time to rest – provide advanced users with better tools to help you care about next year’s crop.
- Use forms for DisambiguationModeration / ReviewFlag pages / reports
- Get to know your users and give them what they want
- Use Google Analytics,Piwik, OWA to get a view of how people use the wikiWhat are they after ?Run interviews, surveys, collect feedback
- And if all this was not enough, start planning for slowdowns.
- Is your wiki ready for popularity ?Are pages cached ? Are they optimized ?Test it
- The result : 10000 pages, 4000 users, 50 daily visits, 72% of returning visitshttp://www.alquier.org/laurent