THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net
S U M M A R Y
DIARY: August 10, 2000 12:43 PM Thursday;
Rod Welch
Subject Index revise for generic Enterprise Management and "ontology."
1...Summary/Objective
..............
Click here to comment!
CONTACTS
SUBJECTS
Case Study Subject Index Background SDS Development Organic Structur
1603 -
1603 - ..
1604 - Summary/Objective
1605 -
160501 - Follow up ref SDS 27 0000
160502 -
160503 - In another record today, developed code to accomplish the Internet
160504 - data base and transfer on c: under sd rather than on drive e and i as
160505 - initially created for testing purposes. ref SDS 27 1891
160507 - ..
160508 - This record considers alternate subject naming schemes, called
160509 - "ontology" by some authorities, for example on 000623, ref SDS 26
160510 - 9900, also "catagories," for example in the record on 000601.
160511 - ref SDS 25 5933
160513 - ..
160514 - It gets real complicated correlating software program operations from
160515 - work product and balancing individual and organizational objectives,
160516 - per POIMS, in an actual physical structure. Selecting the form of the
160517 - structure using letters or numbers has significant trade-offs. Letters
160518 - are easier to remember because they can abreviate common names that
160519 - are easier to remember. But letters require a lot of work to manage
160520 - upper and lower case because some Unix servers are case sensitive,
160521 - which is avoided by numbers.
160523 - ..
160524 - Following records may have considerations on desiging the baseline
160525 - subject index for SDS that puts everything on the c: drive.
160526 -
160527 - 1. Management is organization............. 890513, ref SDS 1 0007
160528 - 2. Complexity of organic structure........ 890523, ref SDS 2 3F8H
160529 - 3. Relational hierarchial matrix
160530 - organic subject structures............. 890523, ref SDS 2 G14K
160531 - 4. Big picture subject index expands
160532 - command control flexiblity of organic
160533 - structures like DNA.................... 890523, ref SDS 2 XT6O
160534 - 5. Keyword selection inefficient.......... 891117, ref SDS 3 0005
160535 - 6. Byte article subjects complex.......... 910418, ref SDS 4 5584
160536 - 7. Subject Index hard work................ 920720, ref SDS 5 0005
160537 - 8. Organic Subject Structure.............. 930326, ref SDS 6 3345
160538 - 9. Master index flexible structure........ 931002, ref SDS 7 0001
160539 - 10. Find information fast easy self-
160540 - evident benefits subjects, links....... 940327, ref SDS 8 J496
160541 - 11. Organic Subject Structure.............. 940824, ref SDS 9 1411
160542 - 12. Multiple views in subject index........ 940825, ref SDS 10 7835
160543 - 13. Example relational hierarchial
160544 - subject index created for PG&E
160545 - project with CDWR...................... 940827, ref SDS 11 0001
160546 - 14. Use letters instead of numbers......... 941124, ref SDS 12 1624
160547 - 15. Balance Summary and Detail............. 950626, ref SDS 13 2882
160548 - 16. Vannevar Bush 1945 article goals for
160549 - technology aid management construct
160550 - trails of associations that augment
160551 - intelligence finding contextually
160552 - relevant details for performing
160553 - daily work............................. 960304, ref SDS 14 H68K
160554 - 17. Complexity context management organic
160555 - structure balance summary for
160556 - perspective on big picture, with
160557 - understanding details for command
160558 - control of the microcosm............... 960322, ref SDS 15 7749
160559 - 18. Traditional records management using
160560 - keywords controller organizes filing
160561 - system, sets rules, MIT document
160562 - filing system.......................... 960322, ref SDS 15 6544
160563 - 19. Granular division organic structures
160564 - subject index context management of
160565 - document content at paragraph level
160566 - command control of the record yields
160567 - power of knowledge connecting cause
160568 - and effect in the microcosm for
160569 - command and control of the work........ 960322, ref SDS 15 G65K
160570 - 20. Differences between subject index
160571 - and traditional records management
160572 - systems to file documents.............. 960322, ref SDS 15 EN87
160573 - 21. Subject index frustrating meaning
160574 - of "subjects" and "categories" hard
160575 - to remember over time; SDS resovles
160576 - with long descriptions to distinguish
160577 - context................................ 960322, ref SDS 15 B25I
160578 - 22. Poetry originally used to improve
160579 - memory replaced by subject indexing
160580 - unlocks forgotten associations like
160581 - singing songs at Disnyland............. 960322, ref SDS 15 CJ6O
160582 - 23. Procedures subject index multiple
160583 - descriptions for alternate views
160584 - increases memory; cross referencing;
160585 - natural control criteria like
160586 - contracts, policies, laws, standards
160587 - aid constructing useful organic
160588 - structures to manage context........... 960322, ref SDS 15 KR6M
160589 - 24. Keyword methods ineffective............ 960322, ref SDS 15 7456
160590 - 25. Keyword methods ineffective............ 960406, ref SDS 16 5922
160591 - 26. Directory management and SI............ 960629, ref SDS 17 0001
160592 - 27. Fractionalized subjecs complexity
160593 - managing daily details seems
160594 - overwhelming without command and
160595 - control organic structure in
160596 - subject index.......................... 970116, ref SDS 18 1732
160597 - 28. Rules for creating subject index....... 970406, ref SDS 19 0001
160598 - 29. Entropy USAFIT study management
160599 - overwhelmed by complexity need tools
160600 - to maintain order, structure, pattern
160601 - understand associations of cause
160602 - and effect............................. 970707, ref SDS 20 0108
160603 - 30. Building SI............................ 990521, ref SDS 21 9633
160604 - 31. SI solves subject retrieval problem.... 990524, ref SDS 22 4774
160605 - 32. Ontology defined....................... 000221, ref SDS 23 8044
160606 - 33. Context management Pandora's box ...... 000221, ref SDS 23 3248
160607 - 34. Subjects Need Theory, System and
160608 - tools for effective management......... 000331, ref SDS 24 2173
160609 - 35. 10 seconds find contextually
160610 - relevant details to verify accuracy
160611 - and expand span of attention
160612 - beyond reach without
160613 - SDS.................................... 020820, ref SDS 28 O1QQ
160614 - 36. Locality principle irreversibility of
160615 - time under 2nd law thermodynamics
160616 - subject index adds energy to organize
160617 - complexity in microcosm of daily
160618 - details associating cause and effect
160619 - for power of knowledge to control the
160620 - future; failure to connect cause and
160621 - effect complexity management hopeless -
160622 - overwhelmed by rising
160623 - entropy................................ 040312, ref SDS 29 YH4G
160624 - 37. Hopeless people giving up on
160625 - communication cannot manage organic
160626 - subject structures below 1 - 3
160627 - levels................................. 060905, ref SDS 30 DJ9J
160629 - ..
160630 - Seems like User ID is unique location for stuff on the web.
160631 -
160632 - This is what distinguishes records on the Internet.
160634 - ..
160635 - Would like to make User ID longer.
160637 - ..
160638 - Currently it is 5 characters.
160639 -
160640 - UUUUU
160642 - ..
160643 - Yesterday made room in the Group Manager for 19 characters.
160644 -
160645 - This could have a component for country...
160646 -
160647 - 1234567890123456789
160648 - USA56172014400
160650 - ..
160651 - 561720144
160653 - ..
160654 - Files don't belong to anyone nor to any program.
160656 - ..
160657 - We probably need a means to associate files with a person, and this
160658 - can be done by inserting the User ID in the directory structure.
160660 - ..
160661 - Since documents are created within SDS records, the SDS code could
160662 - create the User ID automatically, based on the SDS User ID.
160664 - ..
160665 - We could move the User ID in front of SD, or even eliminate SD and
160666 - simply call the program based on the User ID.
160668 - ..
160669 - Each computer usually has only one user, but that user must be
160670 - integrated onto a server in an Enterprise.
160672 - ..
160673 - People need a way to control what they bring with them to an
160674 - organization, and what they take when they leave. The following
160675 - structure enables people to bring an entire work environment,
160676 - including software.
160677 -
160678 - The software thing does not work real well, because software
160679 - programs have to be installed,
160681 - ..
160682 - So, make User ID the primary key....
160683 -
160684 - User ID
160686 - ..
160687 - c: 0003500000 SOFT W2K
160688 - SOFT Netscape
160689 - SOFT SDS tools 01
160690 - printer 02
160691 - tasks 03
160692 - menus 04
160693 - help 05
160694 - subjs 06
160695 - Dates 07
160696 - Diary 08
160697 - Contacts 09
160699 - ..
160700 - Temp 10
160702 - ..
160703 - Web
160704 - SDS Diary (08)
160705 - Orgz01 02
160706 - Projects 03
160707 - Jobs 04
160708 - Research 07
160709 - Personal 08
160711 - ..
160712 - Transfer
160713 -
160714 - SDS Diary (08)
160715 - Orgz01 02
160716 - Projects 03
160717 - Jobs 04
160718 - Research 07
160719 - Personal 08
160720 -
160721 -
160723 - ..
160724 - Orgz01 02
160726 - ..
160727 - Projects 03
160728 - Jobs 04
160730 - ..
160731 - Research 07
160733 - ..
160734 - Personal 08
160736 - ..
160737 - Still need to figure out correspondence and doc log.
160739 - ..
160740 - This structure is obviated or at least causes redundancy, because
160741 - whatever User ID someone adopts, a different one might be used by the
160742 - organization. If the social security number is used, that might
160743 - create uniformity.
160745 - ..
160746 - Same problem occurs for Internet. Every account gets a unique ID.
160747 -
160748 - Social security number could be used, but people might be
160749 - reluctant to use it for privacy and confidentiality reasons.
160751 - ..
160752 - Another problem is how to include under a single project or other
160753 - account work by different people? If the project is not the main
160754 - level, then when someone leaves, they could theoretically remove
160755 - project information. That is not good. On the other hand, the
160756 - organization backs up everyday, and so has this history.
160758 - ..
160759 - The bigger problem then is how to construct a composite record of work
160760 - by everyone on a particular project.
160762 - ..
160763 - We do this now because User ID is a criteria for SDS, and there is a
160764 - means to report across Users.
160765 -
160766 -
160767 -
160768 -
160769 -
160770 -
160771 -
160772 -
160773 -
160774 -
160775 -
160776 -
1608 -