CONTACTS 
0201 - Dynamic Alternatives
020101 - Mr. Garold L. Johnson

SUBJECTS
Save, Primary, F2, macro 142, macro 1421, macro 0, macro 207, 0702051
Johnson, Gary Subject Report Retrieving Wrong Records
Subject Report Retrieving Wrong Records
Save F2 Update Archive Pointers

1006 -
1006 -    ..
1007 - Summary/Objective
1008 -
100801 - Follow up ref SDS 29 0000, ref SDS 19 0000.
100802 -
100803 - Received four letters from Gary showing expanding use of SDS that is
100804 - spawning many good ideas for improvements.  Some learning and new user
100805 - orientation issues are presented, ref SDS 0 PY8R, and some possible
100806 - problems with the SDS code have surfaced.  To assess problem areas
100807 - requires Gary's current SDS records that have manifested the problems.
100808 - ref SDS 0 PX6X and ref SDS 0 UO66  Gary suggests using standard format
100809 - templates to tailor SDS for engineering management support on software
100810 - development. ref SDS 0 8N94  A lot of this sounds doable, keeping in
100811 - mind that SDS may do other things that complement traditional methods.
100812 - ref SDS 0 QP5G  Morris seems to indicate caution about using SDS to
100813 - make good management fast and easy, because some people "game" the
100814 - system to avoid accountability for failure to perform. ref SDS 0 PVWS
100815 -
100817 -  ..
100818 - Submitted an email linked to this record and replying to Gary's
100819 - letters....
100820 -
100821 -      1.  Subject report problem..................... ref SDS 0 4O2F
100822 -      2.  Forward link proposal...................... ref SDS 0 PY4Y
100823 -      3.  Scroll edit chain back and forward......... ref SDS 0 U66Q
100824 -          Manage software development................ ref SDS 0 8N94
100825 -          New task in Schedule F1 Shift F1 failing... ref SDS 0 QQ3H
100826 -      4.  Navigate Subject Index with F1 F3 idea..... ref SDS 0 PUTY
100827 -
100829 -  ..
100830 - I need to send Gary an SDS record update so he has access to this
100831 - record; as noted below, using the actual records is much more efficient
100832 - that working off the web.  I have the system up on "blocks" fixing an
100833 - issue with Contacts and the doc log from work on 021019, ref SDS 19
100834 - R59I, but should get this done later today.
100835 -
100836 -     [On 030109 submitted SDS update to Gary. ref SDS 37 0001
100837 -
100838 -
100839 -
100840 -
100841 -
100842 -
100843 -
100845 -  ..
1009 -
1010 -
1011 - Progress
1012 -
101201 - Report Not Finding Specified Subject; Actually Found in 2nd Segment
101202 -
101203 - Follow up ref SDS 29 4O2F.
101204 -
101205 - Received ref DRT 1 0001 from Gary saying.....
101207 -        ..
101208 -   1.  I tried to do a SI search for....
101209 -
101210 -          2001 12 09   2003 01 08     04 00074 10 EC 021101a
101212 -        ..
101213 -       I got a record with only the following subject....
101214 -
101215 -          K101 00.0 0000 00012 0 00040 00000000 00000000 04 00074 AP 021101a
101216 -
101217 -         Cannot Jump To Today's Diary Records
101219 -            ..
101220 -           We need Gary SDS records that he used and got the result
101221 -           that is causing a problem, in order to perform analysis that
101222 -           replicates the problem
101223 -
101224 -              Later in the day, received Gary's SDS records.
101226 -            ..
101227 -           We need to know whose SDS User ID was the target of this
101228 -           op?
101230 -            ..
101231 -           I opened Gary's SDS records and his subject index.
101233 -            ..
101234 -           There does not seem to be an entry for the subject in Gary's
101235 -           SDS records that correlates with the specification he asks
101236 -           about today, per above. ref SDS 0 RV6L  The closest account
101237 -           is....
101238 -
101239 -                           04 00074 10 EC 021102a
101241 -            ..
101242 -           ...which is for...
101243 -
101244 -               New Task in Schedule F1 Shift F1 Failed on Record Dated
101245 -               021022 Possible Format Issue
101247 -            ..
101248 -           I tried a search on the account in the subject index for the
101249 -           same period Gary used in his report specification....
101251 -           ..
101252 -          2001 12 09   2003 01 08     04 00074 10 EC 021102a
101254 -  ..
101255 - This search produced the following results using only Gary's User
101256 - ID....
101257 -
101258 -                       No records found.
101260 -  ..
101261 - I changed the search specification to include my user ID, and did the
101262 - search again, which produced the following results...
101263 -
101264 -                       No records found.
101266 -  ..
101267 - I opened the subject index in my records and found the account for...
101268 -
101269 -                         04 00074 10 EC 021102a
101271 -  ..
101272 - ...and found further that there is no account for ...021101a, showing
101273 - that this part of the subject index is synchronized between Gary's
101274 - records and my records, which is somewhat helpful, but not essential,
101275 - because it is impossible to accomplish over time.  A report on the
101276 - ...021102a account in the subject index for my SDS records produced
101277 - the following list...
101278 -
101279 -           021102  Review HTML conversion for transfer to Internet in 0122 and 070405.
101280 -           021106  Gary reports progress on keyboard, HTML formats and other SDS issues.
101282 -  ..
101283 - This is an expected result, because the subject account is dated
101284 - 021102 and the first record we found is dated 021102.
101286 -  ..
101287 - I changed the search specification from the account shown in the
101288 - subject index to the ...021101a account Gary reports using, per above,
101289 - ref SDS 0 RZ6G, by changing "2" back to "1" at the end of the string,
101290 - and did the search again, which produced the following results...
101291 -
101292 -           021101  Jump To Follow Up Today
101293 -           030108  Bug -- New Record
101295 -  ..
101296 - These results conform generally with expectations.  The subject
101297 - account is dated 021102 which is close to 021101, and the current
101298 - record reflects the fact Gary is working on this matter today.
101300 -  ..
101301 - Opening the first record on 021101, ref SDS 21 0001, showed....
101302 -
101303 -      5.  The first record segment is for....
101304 -
101305 -             04 - K101 00.0 0000 00012..... 04 00074 AP 021101a
101306 -             0401 - Cannot Jump To Today's Diary Records
101308 -           ..
101309 -          This is not the target subject for the search, which matches
101310 -          Gary's report, indicating I have duplicated Gary's
101311 -          experience, per above. ref SDS 0 RV6L
101312 -
101314 -  ..
101315 - Record Segments New Way of Working Manage Context with Multiple Views
101316 -
101317 -
101318 -      6.  The second record segment is for....
101319 -
101320 -             05 - K101 00.0 0000 00012..... 04 00074 10 EC 021101a
101321 -             0501 - Error Creating Schedule Record
101323 -           ..
101324 -          This result matches the search specification and so shows a
101325 -          successful report.
101327 -           ..
101328 -          Gary appears to have not looked for the second record segment,
101329 -          because it is not a familiar part of his work practice.
101330 -
101331 -             [On 030111 discussed beginning to segment records into
101332 -             multiple views using Control Fields to identify context.
101333 -             ref SDS 38 6M6N
101335 -              ..
101336 -             [On 030119 called Gary for orientation and support.
101337 -             ref SDS 42 B1C5
101339 -           ..
101340 -          Doing a full report rather than the default Summary report
101341 -          assembles the particular record segments that pertain to the
101342 -          specified subject.  Report options can be scrolled by
101343 -          clicking on the description field that starts showing...
101344 -
101345 -                         *** Summary Report ***
101346 -
101347 -          ...or press F2 as shown in the menu.  The first option after
101348 -          pressing F2 or clicking on the description field is...
101349 -
101350 -                  *** Full Report Without References ***
101352 -           ..
101353 -          This is the most common full report, because it saves memory.
101354 -          A full report with references has not proven useful, but we
101355 -          keep it available just in case.
101356 -
101357 -
101359 -  ..
101360 - Gary continues...
101361 -
101362 -   2.  A subject search with either the AP or the EC subject retrieves
101363 -       the same list of records. ref DRT 1 FV6K
101365 -        ..
101366 -   3.  The jump to the subject works fine for both subjects, but the
101367 -       search is getting the wrong records. ref DRT 1 EX6O
101368 -
101369 -           We need the stuff Gary used that caused this result, in
101370 -           order to perform analysis that replicates the problem
101371 -
101372 -           Per above, after receiving Gary's records it appears the
101373 -           search he did was successful, and was shown in a record
101374 -           segment that is an advanced feature of SDS, per above.
101375 -           ref SDS 0 GF4G
101376 -
101377 -
101379 -  ..
1014 -
1015 -
1016 - Problem Analysis
1017 -
101701 - Update Data Base in Schedule Using Diary Menu
101702 - F2 Save Refreshes Subject Pointers and Update Data Base in Schedule
101703 -
101704 - I tried running the same subject report by opening Gary's records and
101705 - looking for subject in Gary's records on my computer, since he
101706 - recently submitted his records on 030103, ref SDS 33 544H, per the
101707 - letter on 030103. ref SDS 33 KT5O
101709 -  ..
101710 - I got the standard message saying....
101711 -
101712 -                       NO RECORDS FOUND
101714 -  ..
101715 - Tried adding my User ID to the subject report spec and got same
101716 - result.
101717 -
101718 -           Per above, after receiving Gary's records later in the
101719 -           afternoon, it appears the search he did was successful, and
101720 -           was shown in a record segment that is an advanced feature of
101721 -           SDS, per above. ref SDS 0 GF4G
101723 -  ..
101724 - Tried expanding the search period to a year, and this yielded the
101725 - record under Gary's User ID...
101726 -
101727 -          Jump to follow up today............ 021101, ref SDS 21 0001
101729 -  ..
101730 - Based on my records, this is what I would expect, since the subject
101731 - reflects the date of 021101.
101733 -  ..
101734 - If Gary created a new record today with this same subject, it should
101735 - show up for a current period subject report covering the past 3 or 4
101736 - months (I forget whether it is 3 or 4 months).  Since his search spec
101737 - spans several years, he may need to update the SDS report pointers on
101738 - his computer by opening the "Diary" menu in the Schedule and selecting
101739 - "Update Data Base," because the search spec spans a year, and in that
101740 - case it uses the global pointers on the e drive.
101742 -  ..
101743 - The actual process is to open the record on 021101 and use F2 to make
101744 - sure the pointers are updated, then run the Update Data Base op.
101746 -  ..
101747 - If this does not solve the problem, I need Gary's records to replicate
101748 - the problem, per above. ref SDS 0 PX6X
101749 -
101750 -           Per above, after receiving Gary's records later in the
101751 -           afternoon, it appears the search he did was successful, and
101752 -           was shown in a record segment that is an advanced feature of
101753 -           SDS, per above. ref SDS 0 GF4G
101754 -
101755 -
101756 -
101757 -
101758 -
1018 -

SUBJECTS
Forward Link Failed Using Existing Code
Forward Links Failed
Link SDS records forward, 931220
Forward Links to Scheduled Tasks Not Supported

180601 -  ..
180602 - Forward Links Not Designed into SDS
180603 -
180604 - Received ref DRT 2 0001 from Gary saying...
180605 -
180606 -     [On 030628 followed up. ref SDS 45 0001
180607 -
180608 -   1.  I attempted something strange, so I am not surprised that it
180609 -       didn't work, but the error is strange.
180611 -        ..
180612 -   2.  Objective: Create a new diary record from an existing record and
180613 -       create a forward link to it. ref DRT 2 4W5N
180614 -
180616 -           ..
180617 -          Link Schedule Tasks Not Support Because Nothing Has Happened
180618 -
180619 -          This objective conflicts with SDS design that does not
180620 -          support linking to a Scheduled task, because it does not
180621 -          have a fixed location to the record.
180622 -
180623 -              [On 030627 Gary asked about a varient of this feature,
180624 -              which could save time. ref SDS 44 UP4M
180626 -               ..
180627 -              [On 030628 developed a way to create a generic forward
180628 -              link follow up notice. ref SDS 45 0001
180630 -           ..
180631 -          "Plans" to expand functionality within the existing design
180632 -          per Gary's work today is useful initiative for exploring
180633 -          results that might be possible even though they are not
180634 -          expressly designed into the system.  Running these "plans"
180635 -          with debug, might further disclose small changes that permit
180636 -          objectives to be met.  So, keep up the good work.
180637 -
180638 -              [On 030628 developed a way to create a generic forward
180639 -              link follow up notice. ref SDS 45 0001
180641 -           ..
180642 -          A future improvement would be to use the Schedule file ID
180643 -          with a new linking syntax, and, when, and if, a Schedule
180644 -          record is ultimately converted into a Diary, then all of the
180645 -          pointers would have to be updated.  We might keep a history
180646 -          in a Schedule task of links to the task, and when it is
180647 -          converted, then the associated diary records would be updated
180648 -          with the permanent location, since the prior location no
180649 -          longer exists.
180651 -           ..
180652 -          Issues to resolve are...
180653 -
180654 -             1.  Link syntax to a Schedule task.
180655 -
180656 -             2.  Store forward links for conversion when the scheduled
180657 -                 task is converted into a diary record.
180659 -                  ..
180660 -             3.  Restore the Schedule link format, if a diary record is
180661 -                 converted back to a Schedule task, as occurs when
180662 -                 someone changes their mind.  After converting a
180663 -                 Schedule task to a Diary record, it is converted back
180664 -                 to a Schedule task, because for one reason or another
180665 -                 decided not to do any work on the task.
180667 -                  ..
180668 -             4.  Responsive of system under criteria 2 and 3.
180669 -
180671 -  ..
180672 - Gary continues...
180673 -
180674 -   3.  Plan:
180675 -
180676 -           1.  Enter Follow On <date>
180677 -           2.  F2 to save
180678 -           3.  F5 to turn linking on
180679 -           4.  F1 Shift F1 to create the new record
180680 -           5.  F8 to make it a Diary record
180681 -           6.  <enter> to open the record
180682 -           7.  Position to the initial anchor and <enter> to try to
180683 -               create the link in the last record.
180685 -        ..
180686 -   4.  I get this error...
180688 -        ..
180689 -       You are in a diary record created by ANOTHER User. ref DRT 2
180690 -       4W7Y
180692 -        ..
180693 -       "Save," "delete" and "link" functions are NOT available in this
180694 -       mode.
180696 -        ..
180697 -       You can only EXAMINE another User's diary record for
180698 -       information, and link into them, then ESC to close it.
180700 -        ..
180701 -       If you feel the record is incomplete, inaccurate or not needed
180702 -       any longer, check with the User or that person's supervisor.
180704 -        ..
180705 -   5.  If I create the record and then link, it works fine.
180707 -        ..
180708 -   6.  Again, this was something bizarre I tried, but getting *this*
180709 -       error is surprising.
180710 -
180711 -          Unusual results are expected when testing performance outside
180712 -          the design spec, per above. ref SDS 0 4W5N
180713 -
180714 -              [On 030628 developed a way to create a generic forward
180715 -              follow up notice. ref SDS 45 0001
180716 -
180717 -
180718 -
180719 -
1808 -

SUBJECTS
Ctrl F6 Scrolling Edit Chain Stack Forward and Backward Using Maybe F

190301 -  ..
190302 - Scroll Edit Chain Forward Back with New Function Complement Ctrl F6
190303 - Ctrl F6 Complementary Function to Scroll Edit Chain Forward and Back
190304 -
190305 - Received ref DRT 3 0001 from Gary saying....
190306 -
190307 -   1.  See new records at...
190308 -
190309 -       Suggestion -- Handling Ctrl F6 Record Stack
190310 -
190311 -          http://www.welchco.com/sd/08/GLJDY/02/03/01/08/034213.HTM
190313 -  ..
190314 - Need Gary's SDS records updated for today to work directly with this
190315 - issue in his record on 030108, that says in part on the Internet....
190316 -
190317 -       Going Forward in Record Stack
190319 -        ..
190320 -       Suppose that in addition to using Ctrl F6 to move back in the
190321 -       stack, we had a way to move forward as well.
190322 -
190323 -          http://www.welchco.com/sd/08/GLJDY/02/03/01/08/034213.HTM#CQ6M
190325 -        ..
190326 -       Then if I needed to bounce back and forth between records I
190327 -       would have another way to do it.
190329 -            ..
190330 -           Ctrl F6 Provides Fast Access to Edit Stack
190331 -           Medit Needs Alternate to "e" Command for Scrolling Stack
190332 -
190333 -           Seems like this feature needs revision to Medit for
190334 -           scrolling the edit chain in reverse order.
190336 -            ..
190337 -           Maybe Morris can comment on feasibility.
190339 -            ..
190340 -           The speed of switching between files in Medit may reduce the
190341 -           utility of this feature.  If there are 3 - 5 files in
190342 -           memory, it may be just as fast to use Ctrl F6 as it is to
190343 -           use F1 Ctrl F6, per Gary's suggestion below. ref SDS 0 8N60
190344 -           If there are say 10 files in memory, than an alternate route
190345 -           might save time a little time.  Actually you can hold Ctrl
190346 -           and F6 and it scrolls instantly ahead, probably too fast to
190347 -           be effective for accomplishing Gary's objective.
190349 -            ..
190350 -           We might consider rearranging things to use Alt F6, but it
190351 -           has good symmetry performing join with Alt F5 that does
190352 -           split within margins.   We might find other schemes that
190353 -           work.
190355 -  ..
190356 - Gary's record on 030108 continues at line 060718....
190357 -
190358 -       Key Sequence
190359 -
190360 -          http://www.welchco.com/sd/08/GLJDY/02/03/01/08/034213.HTM#0046
190361 -
190363 -        ..
190364 -       There is a general question of whether to use a different shift
190365 -       function or the F1 prefix key. Both mechanisms have been used.
190366 -
190367 -         •  Alt F8 deletes a line, F1 Alt F8 deletes to the end of
190368 -            file.
190369 -
190370 -         •  Ctrl F4 marks a line to move, Alt F4 marks multiple lines
190371 -            to move.
190373 -        ..
190374 -       This would mean that both F1 Ctrl F6 and Alt F6 are candidates.
190376 -        ..
190377 -       I *think* I prefer F1 Ctrl F6, but I am not certain.
190379 -        ..
190380 -       Think about open record navigation sequence.
190381 -
190382 -
190383 -
190384 -
190385 -
190386 -
1904 -

SUBJECTS
Managing Software Development Application for SDS
Engineering Management
Game System of Action Item Management
Action Item System Fails at Intel 40K Action Items Overwhelm Manageme
Intel Action Items Complex People Game System Report Actions Complete
Action Items SDS New Way Working Good Management Consistent Plan Perf
Game System Action Items Reporting Tasks Complete that are Still Pend
40K Action Items Complexity Overwhelms People Game System Reporting T
Morris Frustrated Feels Microsoft Programs Manage Action Items Better

4511 -
451201 -  ..
451202 - Managing Software Development with SDS
451203 -
451204 - Gary's third letter continues with ideas on using SDS to manage
451205 - software development projects, and citing a link, ref DRT 3 ME6F, to
451206 - another record....
451207 -
451208 -          http://www.welchco.com/sd/08/GLJDY/02/03/01/08/035341.HTM
451209 -
451210 - ...which he prepared today, dated 030108. ref SDS 35 0001
451212 -  ..
451213 - As noted above, Gary's actual SDS records make analysis faster and
451214 - easier, ref SDS 0 ZW3L, on this important idea, as related in Gary's
451215 - record on the Internet which says in part beginning with the
451216 - Summary/Objective at line 040505....
451217 -
451218 -              Later in the afternoon, received Gary's records, and so
451219 -              provide links.
451221 -           ..
451222 -      1.  Software development projects are all managed according to a
451223 -          common process, at least at the level of an individual
451224 -          developer. ref SDS 35 0001
451226 -           ..
451227 -          http://www.welchco.com/sd/08/GLJDY/02/03/01/08/035341.HTM#0001
451229 -           ..
451230 -      2.  The intent is to develop a strategy for managing multiple
451231 -          software development projects using SDS. If we can do this
451232 -          successfully, we can use the techniques to manage the
451233 -          development of SDS.
451235 -           ..
451236 -      3.  There should be a set of template records for creating the
451237 -          base records for a project. The links will be modified for
451238 -          the specific project. ref SDS 35 NM5N
451239 -
451241 -  ..
451242 - Flexible Structure Enables Using SDS for Managing All Projects
451243 -
451244 - Gary's proposal to strengthen SDS for managing software development
451245 - projects, including SDS improvements is a powerful idea, related by
451246 - Morris on 010924. ref SDS 13 NK4J
451248 -  ..
451249 - SDS evolved from the practice management, as related in the record on
451250 - 000723. ref SDS 6 0001  Software development generally falls within
451251 - the field of "project management," which is part of the larger
451252 - practice of management supported by the SDS plan, perform, report
451253 - "intelligence" cycle, explained in POIMS. ref OF 1 6649  Software
451254 - development is a special class of projects that more narrowly fit the
451255 - model of engineering management
451257 -  ..
451258 - On 990524 reviewed application of SDS for engineering management,
451259 - ref SDS 4 0876, which aligns with Gary's proposal today. ref SDS 0
451260 - 8N94 At that time on 9905025 Morris commented on this application.
451261 - ref SDS 5 0966
451262 -
451264 -      ..
451265 -     Action Items Overwhelming on Big Projects; People Game the System
451266 -
451267 -     Possibly Morris can comment on Gary's idea for applying SDS to
451268 -     engineering management, with support for practices peculiar to
451269 -     software development, per below. ref SDS 0 1960  How do Gary's
451270 -     ideas relate to Morris' experience at Intel where management is
451271 -     frustrated and overwhelmed by the magnitude and complexity of
451272 -     projects that have 40K action items.
451274 -      ..
451275 -     Morris seemed to indicate that sometimes work is delayed and goes
451276 -     over budget because people "game the system" by reporting tasks
451277 -     are completed in order to avoid accountability for delay, and then
451278 -     padding the record by opening the same tasks with a new name, in
451279 -     order to get credit for doing more work than is actually taking
451280 -     place.
451281 -
451282 -         This reminds of games contractors play.  In the mid-70s Barney
451283 -         Hedberg at Perini related that during the heady days of the
451284 -         1940s building up for the war effort against Germany and
451285 -         Japan, contractors were paid on the basis of quantities.  Came
451286 -         time to measure for payment, the inspector would insist on
451287 -         reading the dimensions personally, to avoid temptation for the
451288 -         contractor to pad the record.  So, Berney would hold the
451289 -         "idiot" end of the tape, and the inspector would walk off the
451290 -         distance to the end of the structure, then read and note the
451291 -         value shown on the tape.  Barney recalled how 30 years ago
451292 -         these were big structures, sometimes 300 feet long.  While the
451293 -         inspector was concentrating on reading his end, Bareny would
451294 -         grip the tape a foot or so short, all in the spirit of fun and
451295 -         games, as Morris relates today.
451297 -      ..
451298 -     These "games" may have been on the mind of Intel's CEO in a report
451299 -     on 000822 that management dropped the ball causing mistakes that
451300 -     lowered earnings and stock prices. ref SDS 7 019R
451302 -      ..
451303 -     "Gaming" the system can seem like great fun, and so becomes
451304 -     popular until the game collapses, as occurred at Enron, reported
451305 -     on 020204. ref SDS 15 P49F
451307 -      ..
451308 -     Why, though, would an organization close an action item, simply on
451309 -     the say so of someone responsible for the work, without checking
451310 -     to verify the work is satisfactory, regardless of what one person
451311 -     or another might say.  Where is the inspection report? Where is
451312 -     the deliverable?  Does it work?  Who did the test; etc.
451314 -         ..
451315 -        Morris wrote back saying he could not locate Gary's ideas to
451316 -        offer comments, because this required clicking a link.  A lot
451317 -        of people have been frustrated lately about using links,
451318 -        showing systemic resistance to a new way of working, noted by
451319 -        Lynn Conway on 960612. ref SDS 2 1368  Andy Grove, also, at
451320 -        Intel with Morris, notes that people like work on familiar
451321 -        things in familiar ways, reported on 980307. ref SDS 3 3740
451322 -        More recently, on 020922 Morris explained objections to links.
451323 -        ref SDS 17 BQ7N
451324 -
451325 -
451327 -  ..
451328 - Engineering Management for Software Development
451329 - Software Development Particular Requirements for Enginering Management
451330 -
451331 - Gary goes on to list the following template records with specific
451332 - criteria....
451333 -
451334 -     1.  Project Definition Record
451336 -          ..
451337 -     2.  Defect Tracking
451339 -          ..
451340 -     3.  Defect List Record
451342 -          ..
451343 -     4.  Defect Report Record
451345 -          ..
451346 -     5.  Defect Status Subjects
451348 -          ..
451349 -     6.  Defect Work Record
451351 -          ..
451352 -     7.  Defect Resolution Record
451354 -          ..
451355 -     8.  Project Planning Record
451356 -
451358 -  ..
451359 - SDS has been developed using some aspects of the scope Gary sets out
451360 - for each of these criteria, illustrated by the record on 030101.
451361 - ref SDS 30 0001  Since SDS uses a flexible structure, explained in
451362 - POIMS, ref OF 1 M17I, any template can be formulated, and then
451363 - replicated for other projects.  An example is this record which
451364 - develops formats that might be useful for communicating between SDS
451365 - records and other SDS records on the Internet.
451367 -  ..
451368 - Additionally, going forward, we want to look for synergy with existing
451369 - tools and methods rather than replace everything, at least all at
451370 - once.  This requires imagination and focus to find ways for augmenting
451371 - existing methods with complementary support in SDS for communication,
451372 - planning and reporting.
451374 -  ..
451375 - It may turn out we want to software engineer to continue with existing
451376 - and familiar tools, and that management uses SDS for oversight.
451377 -
451378 -
451379 -
451380 -
4514 -

SUBJECTS
F1 Shift F1 Failed to Create a New Record Correctly
Johnson, Gary New Task Using Diary Record for Template Follow Up Form
New Task Using Diary Record for Template Follow Up Format Fails for S

4805 -
480601 -  ..
480602 - Schedule New Task Using Existing Diary Record Failing F1 Shift F1
480603 -
480604 - Gary's third letter continues with a report on a problem using F1
480605 - Shift F1 to create a new task in the Schedule using an existing Diary
480606 - record, ref DRT 3 ME6L, and citing a link, ref DRT 3 ME6L, to another
480607 - record....
480608 -
480609 -     ttp://www.welchco.com/sd/08/GLJDY/02/03/01/08/050315.HTM 480610 -
480611 - ...which he prepared today, dated 030108. ref SDS 36 0001
480613 -  ..
480614 - As noted above, Gary's actual SDS records make analysis faster and
480615 - easier, ref SDS 0 ZW3L, to address this issue.  Gary's record says in
480616 - part beginning with the Summary/Objective at line 040504...
480618 -     ..
480619 -    When I use F1 Shift F1 to create a new schedule record from a
480620 -    Diary record, I encounter several problems.
480621 -
480622 -       1. The follow up is always to SDS 2 even if there is only a
480623 -          single record.
480624 -
480625 -       2. Save tries to add another Follow Up anchor. I have to change
480626 -          the anchor number, save the record, and then delete the
480627 -          extraneous line.
480629 -  ..
480630 - This kind of thing has occurred previously, but I thought it was
480631 - solved.  Need Gary's actual records to emulate the problem.
480632 -
480633 -         Later in the afternoon, received Gary's records.
480635 -      ..
480636 -     I experimented on a few of Gary's records.  In particular I tried
480637 -     using the following to make new tasks in Gary's Schedule....
480638 -
480639 -       1.  Managing software development.... 030108, ref SDS 35 0001
480640 -       2.  Suggestion on Ctrl F6............ 030108, ref SDS 34 0001
480641 -       3.  Bug -- New Record................ 030108, ref SDS 36 0001,
480643 -              ..
480644 -             This is the first one I tried and the problem Gary reports
480645 -             occurs.  The cause is the lack of a citation for the
480646 -             "Follow up" string.
480648 -            ..
480649 -       4.  Extending SDS Using External
480650 -           Programs......................... 030103, ref SDS 32 0001
480651 -       5.  Moore's Law and Value of
480652 -           Computer Power................... 030102, ref SDS 31 0001
480654 -              ..
480655 -             All of these records have the same problem Gary reports,
480656 -             per above, ref SDS 0 QQ3H, and caused by the same common
480657 -             format issue, also, per above. ref SDS 0 EB6L
480659 -                 ..
480660 -                [On 030114 worked on related issues, and fixed this as
480661 -                well. ref SDS 39 L65G and ref SDS 39 8O3I
480663 -                 ..
480664 -                [On 030117 notified Gary of solution and submitted
480665 -                updated code. ref SDS 41 OZ9L
480666 -
480667 -
480668 -
480669 -
480670 -
480671 -
480672 -
480673 -
480674 -
480675 -
480676 -
4807 -

SUBJECTS
Subject Index Navigate Stepping Down a Level Using F1 F3
F1 F3 Navigate Subject Index Stepping Down a Level Using F1 F3
F1 F3, F1 F4 Prior Level

5505 -
550601 -  ..
550602 - Navigate Subject Index with F1 F3 and Other Methods
550603 -
550604 - Gary reports in a fourth (4th) letter, ref DRT 4 0001, received
550605 - today...
550606 -
550607 -    1.  I have reported this one before...
550609 -             ..
550610 -            The record of prior reports provides useful context, and so
550611 -            a link to background makes understanding the current
550612 -            problem a little faster and easier, and may point to prior
550613 -            analysis that expedites consideration of the current issue.
550614 -
550615 -               [On 030116 Gary has been provding links on correction
550616 -               and improvement ideas. ref SDS 40 PUTY
550618 -  ..
550619 - Gary continues...
550620 -
550621 -        ...but it is worth mentioning again...
550622 -
550623 -          1.  From an SDS record, go to a specific subject down in the
550624 -              hierarchy.
550626 -               ..
550627 -          2.  Do F1 F3 to go up a level in the index. ref DRT 4 YV5Y
550629 -         ..
550630 -    2.  Result: You will be at the top of the index. ref DRT 4 YV6G
550632 -         ..
550633 -    3.  It seems that the way to find a parent is to use the top line
550634 -        of the index page and do a find. That way the move up doesn't
550635 -        depend on the navigation history. It then works the same as F1
550636 -        F2 to go down a level. ref DRT 4 YV6K
550637 -
550639 -  ..
550640 - This seems like a good idea to improve navigation in the SI.
550642 -  ..
550643 - Currently, F1 F3 steps back to a prior level based on a stack
550644 - maintained in 03501 that is generated by stepping forward using F1 F2.
550645 - Gary points out that when stepping into an index at a particular level
550646 - from a Control Field or from a Subject report F1 F3 does not have a
550647 - stack in 03501, and so it defaults to the primary Index.
550649 -  ..
550650 - The suggestion for F1 F3 to use the string at the top of the index to
550651 - access that prior level is a good one, except there are a lot of cross
550652 - references between indexes.  So often an index is entered from another
550653 - location that is not shown in the current index.  This history is
550654 - maintained in the 03501 stack.
550656 -  ..
550657 - Maybe something can be done on this one.  For example, F1 F3 to follow
550658 - the process Gary proposes when it finds that the stack in 03501 is
550659 - empty.  That is an attractive approach.
550661 -  ..
550662 - In the meantime there is ability to step into any level of the SI from
550663 - within an SDS record Control Field and from within a Subject Report
550664 - screen, which are the only places where this issues arises.
550666 -  ..
550667 - The procedure is to click on the space between account levels to
550668 - access an intermediate level.
550669 -
550670 -     [On 030531 Gary proposes using outline technologies to supplement
550671 -     SDS procedures for navigating within the SI. ref SDS 43 XO5M
550672 -
550673 -
550674 -
550675 -
550676 -
550677 -
550678 -
550679 -
550680 -
5507 -