Structuring knowledge according to "Every Page is Page One"
•
1 like•179 views
Intro presentation by Sabine Melnicki at EMWCon Spring 2018 in Houston, Texas * Talk: https://www.youtube.com/watch?v=Umz5VwdYCn8&index=1&list=PLQVG_tuf3Q2fdLXpZ2Mwz-IkjHRgdnDsh&t=0s * Conference: https://www.mediawiki.org/wiki/EMWCon_Spring_2018
More Related Content
Similar to Structuring knowledge according to "Every Page is Page One"
Similar to Structuring knowledge according to "Every Page is Page One" (20)
Recently uploaded
Recently uploaded (20)
Structuring knowledge according to "Every Page is Page One"
- 1. EPPO/JSS1 Structuring knowledge according to "Every Page is Page One" EMWCon Spring 2018 | Conference Day 1 Sabine Melnicki | WikiAhoi Lex Sulzer | Dataspects
- 2. + what do users want/need? + what enables knowledge transfer? + how can the wiki support that?
- 3. what do users want?
- 4. > design structure for the independent, autonomous user #1 user wants an intuitive platform
- 5. > design pages for searchers, not browsers #2 user’s time and patience is scarce
- 6. > design for easy structure, but qualified readers #3 users are clever, intelligent and informed – but: dependent on your system
- 7. 1# design structure for autonomous users 2# design for searchers 3# design for qualified readers
- 9. * comprehensible * transferable format(s) * explicit (not tacit)
- 10. How can the Wiki help?
- 11. * motivate to write to be read. * motivate to only use the wiki. * motivate to write down. > by structure
- 13. Every Page is Page One # include it all. filter it afterward. # distributed nature of the web. # bottom-up architecture.
- 14. “IF BOTTOM-UP ORGANIZATION APPEARS MESSIER THAN TOP-DOWN ORGANIZATION, IT IS ONLY BECAUSE IT MORE ACCURATELY REFLECTS THE MESSINESS OF THE REAL WORLD.”
- 15. Examples # Wikipedia # Stack Overflow # WordPress Codex
- 16. # TOPIC # TOPIC TYPE # CONTEXT # CONTENT
- 17. The Topic
- 19. topic = has a limited purpose
- 20. ”a well-designed information set is like a well-designed transportation system, it allows passengers to travel individual itineraries along shared routes.”
- 21. topic = conforms to a type
- 22. topic = stays on one abstraction level
- 26. topics = * self-contained * limited purpose / conform to a type / stay on one level * establish context * assume qualified reader * link richly
- 27. writing topics
- 29. TOPIC. page title, URL, WikiWords PURPOSE summary of the topic topic type > local navigation, repeating structure
- 30. CONTEXT „blurb“ first paragraph – relation to the real world and wiki world * definition of terms – word origin, synonyms, antonyms * subordinates, umbrella terms * categories * scope (thematically, temporal) * describe development, future plans * preambles, requirements > links richly
- 32. Contact *** WikiAhoi | Ahoi e.U. wikiahoi.at @WikiAhoi / @SabineMelnicki ahoi@wikiahoi.at