CONTACTS 

SUBJECTS
Communication Management Guide to Running Meetings, Doug Engelbart
Summarize Documents, Eugene Kim
Communication Management Guide to Running Nics, 0004278
Email with Links OHS Architecture
Archive Summarize Email Documents, Eugene Kim
Document Management
Summary Linked to Detail
Summary Documents Archive Abstract, 001123, Eugene Kim
Document Summary Support
Summarize Documents on Project Archive Email, Request Volunteers

1412 -    ..
1413 - Summary/Objective
1414 -
141401 - Follow up ref SDS 4 00VU, ref SDS 3 3995.
141402 -
141403 - Received ref DRT 1 0001 from Eugene Kim saying that doing a regular
141404 - summary of unrev-ii and ohs-dev would be an excellent exercise in
141405 - knowledge management.  They are already used effectively on a number
141406 - of open source mailing lists.
141407 -
141408 - Eugene feels this would be a tremendous way of making our list more
141409 - accessible and meaningfully indexing our archives.  I'd encourage
141410 - people who are looking for ways to contribute to the bootstrap efforts
141411 - to volunteer. ref DRT 1 QX6L
141412 -
141413 -     [On 001126 Eugene suggests document summaries can accomplish KM
141414 -     without using SDS. ref SDS 5 PK4N
141415 -
141416 - This initiative relates to a letter from Jack Park on 001102
141417 - discussing a meeting with Henry van Eykan at SRI, which is attached to
141418 - Eugene's letter. ref DRT 1 YY8F
141419 -
141420 - Henry evidently proposed summarizing the many threads/themes that have
141421 - passed through the Unrev2 mailing list.  It seems that this could be
141422 - handled in several ways, all of which includes necessity of passionate
141423 - editorial volunteers.  If I recall rightly, bootstrap.org has all
141424 - threads archived in hypermail (or words to that effect). ref DRT 1
141425 - P18O
141426 - ..
141427 - Jack was asked to canvas for volunteers to summarize the record.
141428 - ref DRT 1 F29L
141429 -
141430 - Jack's letter on 001102 requests people to take on some aspect of this
141431 - summarization task.
141432 -
141433 -     What are the varous "aspects" to be performed?
141434 -
141435 -        [On 001128 submitted letter to team. ref SDS 6 0001
141436 -     ..
141437 -     Is this part of the procedures for managing communications,
141438 -     e.g., meetings and correspdondence, which Doug requested on
141439 -     000427, as a Guide to Running NICs, ref SDS 2 2867, based on his
141440 -     1972 paper which he cited on 000327? ref SDS 1 3971
141441 -     ..
141442 -     Do the summaries, also, need organization?  Do we need
141443 -     subjects, or topics (catagories) for cross-referencing documents?
141444 -
141445 -     Eugene submits several Internet resources...
141446 -
141447 -         http://www.ddj.com/topics/pythonurl/
141448 -
141449 -         http://www.ddj.com/topics/tclurl/
141450 -
141451 -         http://www.freebsd.org/conspectus/
141452 -
141453 -     Review of these locations does not show how the proposed summary
141454 -     would be used to expedite the work.
141455 -
141456 -     Is the aim to produce an "abstract" of each email, and linked
141457 -     reference, for example web pages?
141458 -
141459 -     SDS records have a section for "Summary/Objective," and records
141460 -     automatically accumulate headings in a summary, including action
141461 -     items. that may accomplish some of this exercise.
141462 -
141463 -     SDS places documents in the chronology of various objectives and
141464 -     action items.  Documents are positioned in the context of other
141465 -     documents and daily work, as called out in Doug's 1972 paper
141466 -     explaining the Knowledge Workshop.
141467 -
141468 -        [On 001128 submitted letter to team with example of SDS doc
141469 -        log. ref SDS 6 0001
141470 -
141471 -
141472 -
141473 -
141474 -
141475 -
141476 -
141477 -
1415 -