Difference between revisions of "Collaboration:MR Wiki"
From NAMIC Wiki
(→Issues) |
|||
Line 9: | Line 9: | ||
[http://www.spl.harvard.edu/publications/pages/display/?collectionid=1&entriesPerPage=50&page=1&collectionid=1 Publications Database Details view] | [http://www.spl.harvard.edu/publications/pages/display/?collectionid=1&entriesPerPage=50&page=1&collectionid=1 Publications Database Details view] | ||
[http://www.spl.harvard.edu/publications/gallery/ Publications Database Gallery view] | [http://www.spl.harvard.edu/publications/gallery/ Publications Database Gallery view] | ||
− | ==Issues== | + | ==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 | |
− | + | *Curation process? | |
− | + | *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 | ||
=Tcon 08-28-2009= | =Tcon 08-28-2009= |
Revision as of 14:49, 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
Wiki 2 web: content managment system based on wiki
- Publications Database
Publications Database Details view Publications Database Gallery view
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
- Curation process?
- 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
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.