Difference between revisions of "Collaboration:MR Wiki"
From NAMIC Wiki
| Line 24: | Line 24: | ||
*Webmaster needed to monitor recent changes pages for suspicious activities | *Webmaster needed to monitor recent changes pages for suspicious activities | ||
*Identify key pages which need to be actively monitored and updated | *Identify key pages which need to be actively monitored and updated | ||
| − | * | + | *What should be the curation process? How much vandalism do we expect, given that write is limited to members and traceable. |
*Public wiki versus members only: | *Public wiki versus members only: | ||
**Ron votes strongly for a public wiki. | **Ron votes strongly for a public wiki. | ||
**It makes a contribution to the public in general and raises the visibility of the organization | **It makes a contribution to the public in general and raises the visibility of the organization | ||
**A public wiki can be indexed by public search engines such as google, which will make the materials on the pages more accessible | **A public wiki can be indexed by public search engines such as google, which will make the materials on the pages more accessible | ||
| + | |||
| + | ===Community Creation=== | ||
| + | *A wiki lowers the barrier for direct participation, empowers contributors, and broadens the base of active members | ||
| + | *Wikis are also messy and do not follow a top-down design | ||
| + | *A good balance needs to be found between freedom and regulation. Both extremes (anarchy and police state) are not functional for a wiki | ||
| + | *The governance should not be paternalistic but participatory. | ||
| + | *Wiki versus website: The wiki is like a lab notebook, the website is like a glossy brochure. | ||
| + | *Educational program needed for the membership: | ||
| + | **what can members use the wiki for | ||
| + | **why should they care | ||
| + | **how to go about it | ||
=Tcon 08-28-2009= | =Tcon 08-28-2009= | ||
Revision as of 18:24, 29 August 2009
Home < Collaboration:MR WikiContents
Additional information and links
Technologies
- Wiki:
- NA-MIC wiki: Manage events, working meetings, tcon notes, projects informal presentation
- Slicer documentation
- Wiki2Web system
- Publications Database
Issues for MR wiki
Content creation
- Need an editorial board: Leverage the existing one as much as possible, minimize duplication
- Public announcement to solicit contributions
- Description of the project (20.000 foot view)
- Template pages
- Style guidelines
- Need to tie into existing DB for membership and rights managment:
- Every member has automatically read/write and link insertion privileges
- Policies need for loss of privileges if abused (define abuse in this context)
- Policy needed about presentation of commercial products
Content management/Processes and procedures
- Webmaster needed to monitor recent changes pages for suspicious activities
- Identify key pages which need to be actively monitored and updated
- What should be the curation process? How much vandalism do we expect, given that write is limited to members and traceable.
- Public wiki versus members only:
- Ron votes strongly for a public wiki.
- It makes a contribution to the public in general and raises the visibility of the organization
- A public wiki can be indexed by public search engines such as google, which will make the materials on the pages more accessible
Community Creation
- A wiki lowers the barrier for direct participation, empowers contributors, and broadens the base of active members
- Wikis are also messy and do not follow a top-down design
- A good balance needs to be found between freedom and regulation. Both extremes (anarchy and police state) are not functional for a wiki
- The governance should not be paternalistic but participatory.
- Wiki versus website: The wiki is like a lab notebook, the website is like a glossy brochure.
- Educational program needed for the membership:
- what can members use the wiki for
- why should they care
- how to go about it
Tcon 08-28-2009
Attending: David, David, Ron
- Ron should have a tcon next week with Roberta and Sally to discuss the technical issues around the creation of a wiki server and the software to be used. It would probably be sensible to ask Peter Seres to participate in that as well.
- Ron would use this information to develop with the Central Office an action plan for the development and implementation of an MR wikipedia - including some of the options (and an idea of related resource and costs) he suggested for future expansion - a publication database and more complex media display - - based on his experience with his slicer development (Ron will send some links on this)./
- The issues of governance probably to be addressed by an editorial board - engaging members with responsibility for particular areas - this could be put together with help from the publications cttee - and also by direct invitation to the membership themselves. Controversy is to be expected, anticipated and planned for.
- There is a good case for making the wiki open to the public early on - and Ron will make these points in the Action Plan as the Board and Exec will no doubt want to understand these issues before applying the brand name.
- The action plan could be circulated past the web services committee in the next few weeks for comments and suggestions and then we could hopefully start to implement something.
