CommunityLearning_CWE Conference Call (2R63)
Friday 2005-06-03 10:30 am ~ 12:00 noon EDT (2R64)
- Call-in Number: 800-857-9370 (2R92)
- PASSCODE: 68461 (2R93)
- Your entry will be toned-in; please announce yourself (2R67)
- Attendees: (2R68)
- Invited / Expecting: (2R69)
- Regrets: (2R6A)
Agenda Ideas and Suggestions (2R6B)
- Newcomers' orientation for first 45 min. (2R6C)
- If you've already been introduced to the space, join us at 11:15 am when we discuss how to comment in the wiki, including creating links (in-wiki: page & paragraph, from forum archives, from document repository, for the web) (2R6D)
- people with specific tasks they need done on the CWE are encouraged to bring them to the second half of Friday's session -- we can discuss how best to accomplish these tasks. (2R6E)
- Please add here specific questions/ tasks that you would like addressed in the second half of the session. (2R91)
Agenda & Proceedings (2R6F)
- 1. First 45 minutes - Introduction and New User Orientation - SusanTurnbull and PeterYim ("=ppy") (2R6G)
- number one page for newcomers is the WikiHomePage for solid background (2R6H)
- number two page for newcomers: http://community.cim3.net/wiki/ (2R6I)
- CWE for CWE users and administrators - our place to add content and help us learn together faster (2R6J)
- DougEngelbart pioneered groupware, hypertext and many of the seminal ideas underpinning this space - beginning ~40 years ago (2R6K)
- our Collaborative Work Environment (CWE) is a suite of 4 work spaces for the trusted community: (2R6L)
- a portal - to provide a convenient single point of entry to the environment and the work of the community - public facing facet (2R6M)
- first place people go to: http://colab.cim3.net (2R6N)
- a discussion forum (archived email forum) - to hold our conversations and discussions (virtually and asynchronously - not at the same time) (2R6O)
- a wiki - to help us collaboratively compose our work (2R6R)
- a file repository - to hold documents, work and resources that we can share, and (2R6U)
- like your file space, but remote. Requires one time set-up. Any content is accessible by a browser and the content can be referenced and you can point your audience directly to the link of interest (2R6V)
- File-Sharing Workspace / Document Repository: (2R6W)
- http://colab.cim3.net/file/resource/ (2R6X)
- http://colab.cim3.net/file/work/ (2R6Y)
- http://colab.cim3.net/file/community/ (community member password required to access) (2R6Z)
- http://colab.cim3.net/file/admin/ (administrator password required to access) (2R70)
- To access the File Workspace - refer to: http://community.cim3.net/cgi-bin/wiki.pl?FileWorkspaceAccess (2R71)
- in addition to linking to just the top of the page, linking is more granular -- fine-grained accessibility, linking to any paragraph or bullet point (2R72)
- a portal - to provide a convenient single point of entry to the environment and the work of the community - public facing facet (2R6M)
- 2. Why do we need this? (2R73)
- Mission of Company: improve the effectiveness of distributed collaboration for people (2R74)
- Ref: DougEngelbart - his seminal work is an inspiration for this space - particularly, his concept on OHS (Open Hyperdocument System) and DKR (Dynamic Knowledge Repository) (2R75)
- see also: "More about Collaborative Work Environments" (2R76)
- Tools segmentation: (2R77)
- Community segmentation: (2R7B)
- Affinity networks (2R7C)
- Learning communities (2R7D)
- Communities of Practice (see: CommunitiesofPractice) (2R7E)
- Project teams (2R7F)
- it's all about getting work done effectively, especially when we are not in the same place (2R7G)
- it takes People, Process and Tools to achieve that (emphasis: People heads the list; and this is definitely not just about technology) (2R7H)
- To be able to wrap the right processes around tools with the right people in place to implement (2R7I)
- It's a participatory workspace (2R7J)
- it's about: (2R7K)
- sharing (2R7L)
- distributing the work (2R7M)
- getting things done without being in the same place, at the same time (2R7N)
- capturing the memory and knowledge over the entire life-cycle of the community (2R7O)
- have minimal structure to do work; spur innovation and emergent behavior (2R7P)
- perhaps appears very basic, but that's key to its expressive power and flexibility (2R7Q)
- example of a community to look at: http://ontolog.cim3.net (2R7R)
- testbed global community over the past 3 yr. - over 100 members from 13 countries - you're welcome to visit (join us too if you're interested in ontologies) (2R7S)
- 3. a mini wiki-tutorial: (2R7T)
- The top two things that makes this wiki site different from an ordinary website are: (2R7U)
- "create account" / "login" (near upper-right corner of the page, right below the logo/icon, any page.) (2R7X)
- suggested using your name in WikiWord format as your UserName, and use some password (to avoid being spoofed too easily) (2R7Y)
- pick a page (your namesake page or SandBox would be a good start) and click on "Edit text of this page" (near the lower-left corner of the page, any page.) (2R7Z)
- write something onto your namesake page (2R80)
- click "save" or "preview" - Preview enables you to see what your page will look like on the web after saving - while simultaneously showing the edit box. Its helpful to see how the text formatting rules are rendered on the web by looking at both windows. (2R81)
- Summary box - annotates the nature of the change you made (2R82)
- Text formatting rules can be found at the TextFormattingRules page. (2R83)
- take a look at the page index (2R84)
- Select "Recent Changes" at the top of each page to see which pages are changing (2R87)
- intro to PurpleNumbers (2R88)
- 4. How to make comments in the wiki, including creating links (in-wiki: page & paragraph, from forum archives, from document repository, for the web) (2R89)
- How to use "forum" method for commenting on the DataReferenceModel_09_2004 (2R8C)
- large document, large number of contributors representing all interested parties and anticipate contributions that may include large "amounts or chunks of pages") (2R8D)
- use PurpleNumber method to anchor your comments to the relevant paragraph (2R8E)
- Right click on the PurpleNumber following the section identified for comment, like the "2R8F" at the end of this line (2R8F)
- Select copy shortcut (2R8G)
- Paste into your email message with subject line - Comments (2R8H)
- Follow the examples of comments provided below; PurpleNumber is pasted in after ref: (for reference) (2R8I)
- Add your name, date and time in parentheses (2R8J)
- Send your message to the public site at: drm-public@colab.cim3.net (2R8K)
- How to use "forum" method for commenting on the DataReferenceModel_09_2004 (2R8C)
---- (2R8M)
- Example: Comments (2R8N)
- ref: http://colab.cim3.net/cgi-bin/wiki.pl?SandBox#nid7VT (2R8O)
- suggest changing from: "You can insert a graphic image too:" (2R8P)
- changing it to read "You can insert a graphic image (jpg, gif and png formats) too:" (2R8Q)
- (--SusanTurnbull / 2005.02.09 12:30pm EST) (2R8R)
- ref: http://colab.cim3.net/cgi-bin/wiki.pl?SandBox#nid7VW (2R8S)
- Comments: This is a very important section. (--SusanTurnbull / 2005.02.09 12:45pm EST) (2R8T)
Comments received from the public forum (drm-public@colab.cim3.net) will be added to the bottom of the relevant page with the corresponding "purple number" link. (2R8U)
---- (2R8V)
- 5. Observations and Insights from the Week - All (2R8W)
- the new search box at http://colab.cim3.net/ (2R8X)
- using InterMap (2R8Y)
- RSS support (2R8Z)
- 6. Date/ Time of next call: Friday, June, 10, 2005, 10:30 am ~ 12:00 noon EST (2R90)