Daren Welsh
What began as paper folders of typed documents ...
Grew to gigabytes of electronic folders
Directory trees are difficult to search
Multiple copies and versions of documents
Files are easily moved or deleted
a website that allows collaborative editing of its content and structure by its users.
The wiki makes info easier to access, edit, and share
Why would you not want your community knowledge to be
To get management buy-in, we had to demonstrate
value
in 2011 we began with
one wiki
for a group of ~70 people
building critical mass
but unlike Sharepoint this is
not just static text
Missions have many associated details
These can be stored as semantic properties
{{#set: Commander = Peggy Whitson}}
We created a page for each ISS and Shuttle mission
with semantic properties
We can then query for data ...
{{#ask: [[Category:Expedition]]
|? Commander
|sort = Mission start date
|order = asc
}}
... and we can elegantly display this data on any page
{{#ask: [[Category:EV Tool]] [[Primary image::+]]
| ?Primary image
}}
or ...
Email is necessary but abused
Email is good for conversations but a terrible way of storing data
We can't completely get rid of email
but maybe we can reduce it
We can do better with one additional property:
Related article [[Has type::Page]]
Add any relevant wiki page as a related article
These show up in the Meeting Minutes output as links
It gets better ...
This is the Retractable Equipment Tether page
In the footer of every page, we list related Meeting Minutes
This is done programmatically, not manually
We use this same technique for hardware manifested on flights
We can link hardware to EVAs
We can link rules to hardware
We can run compound queries
We find rules we might have otherwise missed
This seems important
Should anyone really be allowed to edit it?
Without continuous contributions and qualified reviews from everyone in your community,
a wiki is just another dumpster
of outdated and unreliable information.
One user with a long review time
blocks other users from further edits
What does this edit-alert-review loop look like in the wiki?
How can we make sure data isn't lost?
We started handing out wikis to every group
but we didn't have a
Wait ... I thought we were trying to reduce the data silos
Restructure based on vehicles/programs
(which should be our natural user group division)
Yes, fewer wikis is better!
|
|
"Lessons learned databases and corporate knowledge information exist, but are not always easily accessible, often incomplete and are not being fully utilized."
"Unfortunately, departure of contractor and civil servant experts occurs faster than information is collected and passed on."
"The Space Shuttle Program ha[d] a wealth of data tucked away in multiple databases without a convenient way to integrate and use the data for management, engineering, or safety decisions"