CommunityLearning CWE/ConferenceCalls 2005 03 25

CommunityLearning_CWE Conference Call    (2PB6)

Friday 2005-03-25 10:30 am ~ 12:00 noon EST    (2P80)

• Call-in Number: 888-913-9973    (2P81)

• PASSCODE: 23654    (2P82)

• Your entry will be toned-in; please announce yourself    (2P83)

• Attendees:    (2P84)
• SusanTurnbull    (2P85)
• BrendaCoblentz    (2P86)
• PeterYim    (2P87)
• BernitaTart    (2PYT)

• Invited / Expecting:    (2P88)
  • DRM WG    (2P89)
  • NASCIO Architecture Working Group    (2P8A)
  • Western BSR teams    (2P8B)
  • SICoP    (2P8C)
  • CAF    (2P8D)
  • NICS    (2P8E)

• Regrets:    (2P8F)

Agenda Ideas and Suggestions    (2P8G)

• Newcomers' orientation for first 45 min.    (2P8H)
• 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)    (2P8I)
• 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.    (2P8J)

Agenda & Proceedings    (2P8K)

• 1. First 45 minutes - Introduction and New User Orientation - SusanTurnbull and PeterYim ("=ppy")    (2P8L)
  • number one page for newcomers is the WikiHomePage for solid background    (2P8M)
  • number two page for newcomers: http://community.cim3.net/wiki/    (2P8N)
    • CWE for CWE users and administrators - our place to add content and help us learn together faster    (2P8O)
  • DougEngelbart pioneered groupware, hypertext and many of the seminal ideas underpinning this space - beginning ~40 years ago    (2P8P)
  • Suite of 4 major work spaces:    (2P8Q)
    • a discussion forum (archived email forum) - to hold our conversations and discussions (virtually and asynchronously - not at the same time)    (2P8R)
      • enables you to focus on content of conversation and not administration    (2P8S)
      • every message becomes an html page that can be sorted by date or conversation thread (linked by replying to an earlier message)    (2P8T)
    • a wiki - to help us collaboratively compose our work    (2P8U)
      • like a web page; read and write web; one person at a time takes notes    (2P8V)
      • platform independent and people can be located anywhere in the world    (2P8W)
    • a file repository - to hold documents, work and resources that we can share, and    (2P8X)
      • 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    (2P8Y)
      • File-Sharing Workspace / Document Repository:    (2P8Z)
        • http://colab.cim3.net/file/resource/    (2P90)
        • http://colab.cim3.net/file/work/    (2P91)
        • http://colab.cim3.net/file/community/ (community member password required to access)    (2P92)
        • http://colab.cim3.net/file/admin/ (administrator password required to access)    (2P93)
        • To access the File Workspace - refer to: http://community.cim3.net/cgi-bin/wiki.pl?FileWorkspaceAccess    (2P94)
      • 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    (2P95)
    • a portal - to provide a convenient single point of entry to the environment and the work of the community - public facing facet    (2P96)
      • first place people go to: http://colab.cim3.net    (2P97)

• 2. Why do we need this?    (2P98)
  • Mission of Company: improve the effectiveness of distributed collaboration for people    (2P99)
  • Ref: DougEngelbart - his seminal work is an inspiration for this space - particularly, his concept on OHS (Open Hyperdocument System) and DKR (Dynamic Knowledge Repository)    (2P9A)
    • see also: "More about Collaborative Work Environments"    (2P9B)
  • Tools segmentation:    (2P9C)
    • personal productivity vs. group productivity    (2P9D)
    • transaction systems vs. groupware    (2P9E)
    • thick client vs. thin client ('utility' software)    (2P9F)
  • Community segmentation:    (2P9G)
    • Affinity networks    (2P9H)
    • Learning communities    (2P9I)
    • Communities of Practice (see: CommunitiesofPractice)    (2P9J)
    • Project teams    (2P9K)
  • it's all about getting work done effectively, especially when we are not in the same place    (2P9L)
  • it takes People, Process and Tools to achieve that (emphasis: People heads the list; and this is definitely not just about technology)    (2P9M)
    • To be able to wrap the right processes around tools with the right people in place to implement    (2P9N)
  • It's a participatory workspace    (2P9O)
  • it's about:    (2P9P)
    • sharing    (2P9Q)
    • distributing the work    (2P9R)
    • getting things done without being in the same place, at the same time    (2P9S)
    • capturing the memory and knowledge over the entire life-cycle of the community    (2P9T)
    • have minimal structure to do work; spur innovation and emergent behavior    (2P9U)
    • perhaps appears very basic, but that's key to its expressive power and flexibility    (2P9V)
  • example of a community to look at: http://ontolog.cim3.net    (2P9W)
    • 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)    (2P9X)

• 3. a mini wiki-tutorial:    (2P9Y)
  • The top two things that makes this wiki site different from an ordinary website are:    (2P9Z)
    • (1) anyone who can read from the site, can also write to the site (so, it is a read-and-write web, not just read-only)    (2PA0)
    • (2) you get automatic hyperlinking, through the use of the WikiWord.    (2PA1)
  • "create account" / "login" (near upper-right corner of the page, right below the logo/icon, any page.)    (2PA2)
    • suggested using your name in WikiWord format as your UserName, and use some password (to avoid being spoofed too easily)    (2PA3)
  • 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.)    (2PA4)
  • write something onto your namesake page    (2PA5)
    • 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.    (2PA6)
    • Summary box - annotates the nature of the change you made    (2PA7)
    • Text formatting rules can be found at the TextFormattingRules page.    (2PA8)
  • take a look at the page index    (2PA9)
    • Site map index - place cursor in search box and hit enter (with a _blank_ search term)    (2PAA)
      • New version available as of March 15, 2005 also provides this index by clicking on the "Page Index" at the top of each page.    (2PAB)
  • Select "Recent Changes" at the top of each page to see which pages are changing    (2PAC)
  • intro to PurpleNumbers    (2PAD)

• 4. How to make comments in the wiki, including creating links (in-wiki: page & paragraph, from forum archives, from document repository, for the web)    (2PAE)
  • How to use "in-line" method for succinct commenting within a small group    (2PAF)
    • edit by putting your suggested change in parentheses under the relevant section followed by your wiki name and date - e.g. (Suggest revising this definition...--SusanTurnbull / 2005.02.09 12:30pm EST)    (2PAG)
  • How to use "forum" method for commenting on the DataReferenceModel_09_2004    (2PAH)
    • large document, large number of contributors representing all interested parties and anticipate contributions that may include large "amounts or chunks of pages")    (2PAI)
    • use purplenumber method to anchor your comments to the relevant paragraph    (2PAJ)
      • Right click on the purplenumber following the section identified for comment, like the "2P50" at the end of this line    (2PAK)
      • Select copy shortcut    (2PAL)
      • Paste into your email message with subject line - Comments    (2PAM)
      • Follow the examples of comments provided below; purplenumber is pasted in after ref: (for reference)    (2PAN)
      • Add your name, date and time in parentheses    (2PAO)
      • Send your message to the public site at: drm-public@colab.cim3.net    (2PAP)
        • DataReferenceModel    (2PAQ)

----    (2PAR)

• Example: Comments    (2PAS)

• ref: http://colab.cim3.net/cgi-bin/wiki.pl?SandBox#nid7VT    (2PAT)
  • suggest changing from: "You can insert a graphic image too:"    (2PAU)
  • changing it to read "You can insert a graphic image (jpg, gif and png formats) too:"    (2PAV)
    • (--SusanTurnbull / 2005.02.09 12:30pm EST)    (2PAW)

• ref: http://colab.cim3.net/cgi-bin/wiki.pl?SandBox#nid7VW    (2PAX)
  • Comments: This is a very important section. (--SusanTurnbull / 2005.02.09 12:45pm EST)    (2PAY)

----    (2PB0)

• 5. Observations and Insights from the Week - All    (2PB1)
  • the new search box at http://colab.cim3.net/    (2PB2)
  • using InterMap    (2PB3)
  • RSS support    (2PB4)

• 6. Date/ Time of next call: Friday, April, 1, 2005, 10:30 am ~ 12:00 noon EST    (2PB5)