CONTACTS 

SUBJECTS
New Task or Link records, Headlines
Recognizing common subject content
Knowledge Space
SDS Improves Alphabet as Knowledge Tool
Writing by Hand, Improved by SDS
Record Segments, 3 x 5 Cards Chunks Emulate
Records, Flexible Size, Segmented
Linking in SDS Headings Link
Links Automatic Headlines in New Task to Original Source Create Audit
Addressability Anchors Add to All Para in SDS record During Save, F2

1612 -
1612 -    ..
1613 - Summary/Objective
1614 -
161401 - Follow up ref SDS 5 5467, ref SDS 3 4523.
161402 -
161403 - Added code to link subjects and headings within record segments so it
161404 - is a little faster to access related information.
161405 -
161406 -     [On 971125 converted linking design to use anchors. ref SDS 6 R65V
161407 -
161408 -
161410 -  ..
1615 -
1616 -
1617 - Concept
1618 -
161801 - SDS records reflect human memory at a point in time.
161802 -
161803 - Links connect mental content at time t1 with content at prior times
161804 - t-n1, t-n2, etc.  SDS automatically links records when a new task is
161805 - created, giving instant access to the entire record.  Experience seems
161806 - to show it might be useful to automatically link record segments and
161807 - headings, as well.  Hopefully this will facilitate crafting language
161808 - for particular elements within a subject by giving the user instant
161809 - access to related history, without having to hunt through a large
161810 - record to find it.
161812 -  ..
161813 - There are two dimensions to this.  One is linking at the subject
161814 - level, and the second is linking at the heading level.  Subjects are
161815 - relatively stable, over time, although even these tend to meld, for
161816 - the reason set out on 960322. ref SDS 4 7749.
161818 -  ..
161819 - Typically, headings are intended to summarize the meaning of larger
161820 - chunks of memory, in the same way that a paragraph summarizes the
161821 - meaning of personal thoughts, and text summarizes related dialog that
161822 - may have occurred over an entire event, such as a meeting or telephone
161823 - call, or discussion.  This normally requires that each heading be
161824 - different, since, by definition, as time passes, interceeding events
161825 - cause new conditions.  So while subjects are relatively constant,
161826 - headings are dynamic and unique.
161828 -  ..
161829 - My sense today is that giving the User additional links at each record
161830 - segment and heading level may wind up making it easier to grasp
161831 - relationships and in turn to construct subjects so they remain
161832 - meaningful.  At the heading level, if one or another link turns out
161833 - not to be needed, it can easily be deleted, whereas to look up the
161834 - stuff, takes more time than to delete it.
161835 -
161837 -  ..
161838 - Design Factors
161839 -
161840 - Scope:
161841 -
161842 -     Lets try to make this routine link every major indented segment of
161843 -     the record.
161844 -     ..
161845 -     Actually, that may not be the best criteria to link.
161847 -      ..
161848 -     It might be better to link underlined headings as well.
161850 -      ..
161851 -     Do we re-use these headings in subsequent records?
161853 -      ..
161854 -     Are we linking subjects, or headings?
161856 -      ..
161857 -     Seems like we should be linking only subjects.
161859 -  ..
161860 - Decided to try linking every heading as well as every subject, execpt
161861 - we will skip the first heading for every new subject.  This latter
161862 - objective seemed to be a little bit awkward, so we will link all of
161863 - them and see how it work out.
161865 -  ..
161866 - There is a little bit of a challenge here to accomodate the variety of
161867 - forms a User might choose to enter the record.  This code lets the
161868 - user place links above the heading, below it, or eliminate them
161869 - altogether, if not needed.  There can be some initial narrative
161870 - without a heading, and that will be given a link when a new record is
161871 - created.  If there are no headings, then the text will at least be
161872 - linked by subject.
161873 -
161874 -
161876 -  ..
1619 -
1620 -
1621 - Progress
162201 -  ..
162202 - 004 - Added Code to Link Headings When New Record Created
162203 -
162204 - Line 890, ref OF 1 0613, -label lnkthm, created this new segment of
162205 - code today, per ref SDS 0 3603
162206 -
162207 -
162208 -
162209 -
162210 -
162211 -
1623 -

SUBJECTS
Load code to SDS record, <Enter>, Mouse

1703 -
1704 -   ..
170401 - Followed up work at ref SDS 1 line 85.
170403 -  ..
170404 - Want the code that enters a function code to evaluate if the field is
170405 - initially blank, and, if so, to make all of the control field lines
170406 - for this segement to be the same function, so we can then simply
170407 - modify any of the others if necessary.
170408 -
170409 -
170410 -
170412 -  ..
1705 -
1706 -
1707 - 044020
1708 -
170801 - Line 210 -label bMfsPEc, about 15 lines below, add code to see if the
170802 - code line is blank, and if so, the new function will be entered into
170803 - all of the function fields.
170804 -
170805 -
170806 -
170807 -
170808 -