CONTACTS 

SUBJECTS
Action Items, 950729
Concepts Action Items
Action Items in Subject Report, 06112
Planning Action Item Review SDS Record for Meetings, 070301, 970505
Purpose Action Item Review SDS Record for Meetings, 070301, 970505
Background Action Item Review SDS Record for Meetings, 070301, 970505

0908 -
0908 -    ..
0909 - Summary/Objective
0910 -
091001 - Follow up ref SDS 5 0000.
091002 -
091003 - Began developing a new routine to create a special SDS record for
091004 - conducting a meeting to review and follow up on pending Action Items,
091005 - as a group.
091007 -  ..
091008 - This mainly uses the Subject report for getting action items for a
091009 - particular subject, such as a project.
091011 -  ..
091012 - The main purpose is to speed up and improve accuracy on ensuring full
091013 - review in a meeting, or other form of macro notification, of all
091014 - pending matters for a paticular subject.  The special record is not
091015 - needed for daily work, because pending matters from the AI report can
091016 - be incorporated into the SDS schedule immediately for follow up.
091017 -
091018 -    [On 970507 evaluated improvements to AI system. ref SDS 7 0001
091020 -     ..
091021 -    [On 000915 reported spending a week making improvements to Action
091022 -    Item system so it would run under improvements in SDS made during
091023 -    July, August and September 2000; reported improvements for Action
091024 -    Item system in this record, so there is a comprehensive explanation
091025 -    of major components and processes. ref SDS 8 0001
091027 -     ..
091028 -    [On 031121 improved process to construct an SDS record for a
091029 -    meeting to review action items; applied Windows Start command to
091030 -    increase memory, which allowed better formatting and a much faster
091031 -    run time. ref SDS 9 JW4J
091032 -
091033 -
091034 -
091035 -
091036 -
091038 -  ..
0911 -
0912 -
0913 - Analysis
0914 -
091401 - We need a better Action Item review format for conducting meetings,
091402 - than was used at the meeting on 961126, ref SDS 5 0000, per letter to
091403 - Tom on 961127. ref SDS 6 4389
091405 -  ..
091406 - The prior report placed status of Action Items adjacent to the
091407 - description of pending action items.  This did not work well
091408 - mechanically.
091410 -  ..
091411 - We should stack the narrative and add a level for Status and one for
091412 - Comments.  Actually, if we stack this stuff, we may not need separate
091413 - headings for status and comments.  It can all be part of narrative
091414 - associated with the Action Item, which is linked back to original
091415 - source for authority and context.
091416 - ..
091417 - Stacking permits segmenting Action Items based on subject, which
091418 - includes responsibility.
091420 -  ..
091421 - Replaced cut and paste with long string char read macros 1188 and
091422 - 1189, to reduce memory problem.
091424 -  ..
091425 - We can use the existing method of identifying action items in the
091426 - ordinary course of work, with Alt F10, and the line numbering function
091427 - will identify these flags and set the Special Control Field status to
091428 - various levels of Action Item status.
091430 -  ..
091431 - The Subject report system under 06112 has a function for creating a
091432 - report specifically formatted for Action Items based on subject
091433 - context.
091435 -  ..
091436 - Will make a new command, or function, to create an Action Item Review
091437 - Meeting SDS record based on every entry in the Action Item report.
091438 - This will greatly reduce the time required to prepare for such meetngs
091439 - per goal above. ref SDS 0 VE8K
091440 - ..
091441 - Another function will add new Action Items to an existing review
091442 - file.
091444 -  ..
091445 - These new options require a special menu for Action Item reports
091446 - produced by the Subject report system.  Currently we are using the
091447 - Subject Report menu.  So we will create a new one.
091448 -
091449 -     Profile flag is 47 = 22.
091450 -
091451 -     Possibly counter 127 can do this per 960815. ref SDS 4 3849
091453 -      ..
091454 -     Looks like 127 = 2 in the Action Item report file.
091455 - ..
091456 - Added two new functions to the new Action Item menu to create
091457 - and maintain (update) a special SDS record that has Action Items
091458 - listed chronologically, segmented by subject, based on Control Fields,
091459 - and linked to original record.
091460 -
091461 -
091462 -
091463 -
0915 -

SUBJECTS
Process for Action Item Review SDS Record for Meetings, 070301, 97050

100301 -  ..
100302 - Process is explained in 0703010
100303 -
100304 - This work is accomplished in macro file 070301. ref OF 7 613M
100305 -
100306 -
100307 -    1.  From AI report produced by Subject system, 06112, open menu and
100308 -        select...
100310 -                           ..
100311 -                          Review Meeting Setup
100312 -
100313 -
100314 -        ...to create a Scheduled SDS task record.
100316 -         ..
100317 -        This initially assign mark 17 to initial AI report. ref SDS 0
100318 -        GH6W
100319 -        ..
100320 -    2.  Open the SDS Schedule and create a new task for Action
100321 -        Item review, such as a meeting. In the new SDS record for
100322 -        action item review...
100323 -
100324 -        a.  Assign markcur 5. ref SDS 0 DG8M
100325 -
100326 -        b.  Number Action Items based on the source record, to provide
100327 -            an easy means of identification for managing the record in
100328 -            communication. ref SDS 0 NT9K
100330 -             ..
100331 -            Count total number, and enter on the Follow up line at the
100332 -            end of the process, so we have an orientation on scope.
100334 -         ..
100335 -    3.  Open orignial SDS record for action item listed in the Action
100336 -        Item report, using macro 98.  In the original SDS record...
100337 -            ..
100338 -        a.  Assign mark 5 to original SDS record. ref SDS 0 RV4G
100340 -             ..
100341 -        b.  Macro 98 automatically finds the line in the original SDS
100342 -            record where the AI is entered, based on the line number in
100343 -            the AI report prepared by the Subject system, 06112 under
100344 -            step 1.
100346 -             ..
100347 -        c.  Post date, time and description of original SDS record to
100348 -            the new Schedule task SDS record, once for all Action Items
100349 -            in the original record. ref SDS 0 IN5J  This provides
100350 -            immediate initial orientation for understanding scope.
100352 -             ..
100353 -        d.  Post purge command to close original SDS record after all
100354 -            action items in the record that are specified in the AI
100355 -            report have been processed. ref SDS 0 TH4J
100356 -            ..
100357 -        e.  After an SDS record is opened with macro 98 from the
100358 -            Action Item report, if there are other action items in the
100359 -            same record, it is opened with ecur 5, and the specific
100360 -            action line is located using code in 070301 instead of usig
100361 -            macro 98, in order to save a little memory of opening a
100362 -            separate search macro file. ref SDS 0 R85L
100364 -         ..
100365 -    4.  Transfer Action Item description from the original SDS record
100366 -        to the new Schedule task SDS record, using the long string
100367 -        macros 1188, 1189. ref SDS 0 UW5G
100369 -         ..
100370 -        Remove any citations in the text of the AI, since they will not
100371 -        be available in the new Scheduled SDS task record, but can be
100372 -        accessed using the link back to the original SDS record.
100373 -        ref SDS 0 1Q6J
100375 -         ..
100376 -    5.  Mark the Action Item just created for linking, with macro 122,
100377 -        and use macro 136 to call macro 985 which in turn calls macro
100378 -        file 01211 for linking the Action Item in the new Scheduled SDS
100379 -        task record back to the original source. ref SDS 0 VR3O
100380 -        ..
100381 -        Will not link every Action Item, but will look for
100382 -        convenient anchor within 10 lines above the Action item, and if
100383 -        none is found, will add anchor to action item.  This prevents
100384 -        creating a lot of extra anchors. ref SDS 0 UY5O
100386 -         ..
100387 -        Adding links is a change to the original record which raises
100388 -        performance and secrecy issues about publication on the web,
100389 -        ref SDS 0 PO5K
100391 -         ..
100392 -        Macro 985 closes (purges) the original SDS record after
100393 -        Creating the link.  We want the original SDS record to remain
100394 -        in memory to process the Control Fields, so modify 985 to exit
100395 -        before saving. ref SDS 0 B18H
100397 -         ..
100398 -        Incorporate macro file 01211 into 070301 to save memory.  This
100399 -        allows reduing the actual size of code required, because there
100400 -        is a lot of standard stuff called in 01211 that is not needed
100401 -        for this specific operation to create the links. ref SDS 0 Y18L
100402 -        ..
100403 -    6.  Justify Action Item descriptions. ref SDS 0 2C7K
100405 -         ..
100406 -    7.  Return to original SDS record, ecur 5, and load the Control
100407 -        Field above the Action Item description. ref SDS 0 7S3M
100409 -         ..
100410 -        To save memory, for now, will only enter a single Control Field
100411 -        line and description. ref SDS 0 QR7F
100413 -         ..
100414 -        This is adequate for non-SDS users to recognize the association
100415 -        of their work with subjects.  Since actual follow up occurs in
100416 -        SDS using the original records, we get the actual Control
100417 -        Fields for doing the actual work.
100418 -
100419 -
100420 -
100421 -
100422 -
1005 -

SUBJECTS
New Task in Schedule, Setup

110301 -  ..
110302 - 070301  Action Item Review, Prepare for Meeting
110303 -
110304 - Line 80, ref OF 7 WS8M, -label 1time create routine.
110305 -
110306 -     This operation is called from the menu anywhere within an Action
110307 -     Item report, created either for one person using Manage menu in
110308 -     the Schedule, calling macro 0612; or, by the Subject report, macro
110309 -     file 06112 from work on 950628. ref SDS 1 5TH2
110311 -      ..
110312 -     Switch to the Schedule, ecur 96.
110314 -      ..
110315 -     Call macro 95 to create an entry for a new scheduled task.  It
110316 -     does not need a time because that is not known yet.  The User can
110317 -     convert it to a performed task when the meeting occurs.
110318 -     ..
110319 -     A temporary task name is created with some dots to indicate
110320 -     User can enter the remainder of the task description. ref OF 7
110321 -     PC7F
110323 -      ..
110324 -     Call macro 972 to open new Schedule SDS record for Action Item
110325 -     meeting preparation. ref OF 7 YO8J
110327 -  ..
110328 - Line 160, ref OF 7 PC7F, -label 1time1 open Schedule and create a
110329 - new task with partial name filled out.
110331 -  ..
110332 - User will have to pre-position the cursor in the Schedule where the
110333 - new task should be entered, or he can move it to the new location,
110334 - after the operation is complete.  User also has to complete the name
110335 - of the Action Item review task.
110336 - ..
110337 - Line 190, ref OF 7 SE9H, -label 1time1 about 30 lines below,
110338 - open the new Schedule task, and set it up for entering the list of
110339 - Action Items, and linking them.
110340 -
110341 -      Assign markcur 45
110342 -
110343 -      Turn linking off, in case it is on elsewhere.
110344 -
110346 -  ..
110347 - Line 220, ref OF 7 B3Q1, -label lpa1 debug routine entered here to
110348 - test system, based on line number in output file.  Need tl 0 here and
110349 - about 50 lines below.
110350 -
110351 -
110352 -
1104 -

SUBJECTS
Number Action Items, Report Total

120301 -  ..
120302 - Number Action Items for Each SDS Record, Report Total
120303 -
120304 - Line 230, ref OF 7 SG5O, -label 1time1 about 60 lines below, begin
120305 - loop to number the Action Item entries in the Schedule task, based on
120306 - the content in the AI report.
120307 -
120308 -      Numbering is based on action items for each SDS record followed
120309 -      up in the record. ref SDS 0 QL4H
120311 -       ..
120312 -      Accumulate number in counter 137, ref OF 7 SG5O, and append
120313 -      total to Follow up line at top of record when the process is
120314 -      completed. ref OF 7 DI7G
120315 -
120316 -
120317 -
1204 -

SUBJECTS
Original SDS Record, Open, Macro 98

130301 -  ..
130302 - Macro 98 Opens Original SDS Record
130303 -
130304 - Line 260, ref OF 7 U4DA, -label lpa1 about 40 lines below, ecur 17
130305 - returns to the AI report; macro 98 opens original SDS record and moves
130306 - to item listed in AI report based on the SDS line number, which is
130307 - shown in the AI report.
130308 -
130309 -     Set 127 888 in original SDS record, so linking using macro 985,
130310 -     called by macro 136, will exit so that the code in macro file
130311 -     01211, which actually creates the link, can be accomplished
130312 -     instead using similar code added today in 070301, per below.
130313 -     ref SDS 0 VR3O  This saves Medit memory by avoiding the overhead
130314 -     of opening another file, see below. ref SDS 0 B18H
130315 -     ..
130316 -     Sets markcur 5.
130318 -      ..
130319 -     Sets 271 1000 for current SDS records, and 271 2000 for archived
130320 -     records.  Transfer these flags to global 269 so we have an easy to
130321 -     figure out how to purge the file later on.
130322 -
130323 -
1304 -

SUBJECTS
Date Description Original SDS Record

140301 -  ..
140302 - Action Items Identify Original Source, Date and Description
140303 -
140304 - Line 300, ref OF 7 MC4F, -label lpa1 about 60 lines below, return to
140305 - the target Schedule task SDS record and enter the date and time to
140306 - provide orientation for when Action Item originally occurred.
140307 -
140308 -     Date is entered in standard format.
140309 -
140310 -         Highlight date, so a summary of the record lists Action Items
140311 -         by date.
140313 -      ..
140314 -     Description of original SDS record is entered below the date, to
140315 -     provide further orientation for the source of the Action Item.
140316 -     Get description from Action Item report, ecur 17, since it is
140317 -     closer than getting it from the original record.
140318 -
140319 -
1404 -

SUBJECTS
Purge Setup for Original SDS record

150301 -  ..
150302 - Setup to Purge Original SDS Record After All AIs Have Been Entered
150303 -
150304 - Line 330, ref OF 7 4131, -label lpa1 about 30 lines below, set up to
150305 - purge original SDS record after all action items in the file have been
150306 - processed based on list in AI report, ecur 17.
150307 -
150308 - See explanation on modifying macro 985, below. ref SDS 0 Y18L
150309 -
150310 -
150311 -
1504 -

SUBJECTS
Open Original SDS Record Ecur 5, Keep in Memory Multiple Passes

160301 -  ..
160302 - Open Original SDS Records After 1st Pass Without Using Macro 98
160303 -
160304 - Line 240, ref OF 7 UK6I, if 227 = 88 it means macro 98 has been used
160305 - to open an SDS record, and there are multiple action items in the same
160306 - record.  Instead of using macro 98 again to open the same record, use
160307 - ecur 5, per below. ref SDS 0 045H
160309 -  ..
160310 - Line 370, ref OF 7 P69M, -label osdsao in the AI report, capture the
160311 - action item line number and use a locate command from within 070301,
160312 - which is already in memory, instead of calling macro 98.  This sames
160313 - Medit memory by avoiding the use of a separate file to create a search
160314 - macro, used by macro 98, to find the Action Item line in the original
160315 - SDS record.
160316 -
160317 -
1604 -

SUBJECTS
Description Action Item Transfer New Schedule Task, Macro 1188, 1189

170301 -  ..
170302 - Enter Action Item Description from Original SDS Record
170303 -
170304 - Line 420, ref OF 7 YP4J, -label aielp do a loop to transfer
170305 - description from original SDS record to new Schedule SDS record task.
170306 -
170307 -     Macro 541 moves cursor to left margin in original SDS record.
170309 -      ..
170310 -     Linecnt 94 saves location for top of para to enter the link, after
170311 -     scrolling up to capture each line of text in the paragraph.
170313 -      ..
170314 -     Macro 1188 reads full length of the line with a single command.
170315 -
170316 -         This replaces used cut and paste, which tended to run Medit
170317 -         out of memory with repeated use, which is required for this
170318 -         operation.
170319 - ..
170320 - Line 430, ref OF 7 H85N, -label aielp about 30 lines below, use
170321 - ecur 45 to return to the Schedule task SDS record, to enter the task
170322 - description line with macro 1189.
170323 -
170324 -     See below for completing loop on entering action item description
170325 -     lines. ref SDS 0 KB4I
170326 -
170327 -
170328 -
1704 -

SUBJECTS
Links Removed Original Description After Transfer to New Task

180301 -      ..
180302 -     Remove Citations in Description Transferred from Original Record
180303 -
180304 -     Line 460, ref OF 7 TF4M, -label eaid about 30 lines below, begin
180305 -     operation to remove citations that may be in the description lines
180306 -     transferred from the original SDS record to the new Schedule task
180307 -     SDS record.  These citations have to be removed because the
180308 -     references are in the new SDS record, and so the record cannot be
180309 -     saved, since macro 142 verifies citations, and stops if a citation
180310 -     in the narrative does not have a corresponding entry in the
180311 -     Reference field.
180312 -     ..
180313 -     Line 470, ref OF 7 FW8F, -label eaid about 40 lines below,
180314 -     initially check flag 88 = 999 which indicates on the prior line, a
180315 -     citation was at the end of the line, but the anchor is on the
180316 -     current line, and so has to be removed, per below. ref SDS 0 T53K
180318 -      ..
180319 -     Line 490, ref OF 7 KY9K, -label rrefa find citations in the
180320 -     transferred text. Start from the left side and do a fr so, if
180321 -     there are two citations, they can be removed sequentially.
180322 -     ..
180323 -     Capture the reference type in counter 88.  We need to know
180324 -     if this is a 2 position string, or a three position string.  Since
180325 -     OF is the only two position string, if it is not an OF citation,
180326 -     then it must be a three position string.   This is used below to
180327 -     set a flag for removing the anchor on the next line, ref SDS 0
180328 -     4B6L,
180330 -      ..
180331 -     Line 500, ref OF 7 T25G, -label rrefa Convert standard citation
180332 -     format to a solid string, so that macro 79 will delete the entire
180333 -     thing with one pass.
180335 -      ..
180336 -     We could just do 4 passes of macro 79, since if the anchor is on
180337 -     the next line, then the rest of the line is blank.  I am trying
180338 -     this hoping to save memory that might leak out using macro 79
180339 -     repeatedly.
180340 -     ..
180341 -     Line 510, ref OF 7 Y56L, -label rrefa about 40 lines below,
180342 -     if a citation is at the beginning of a line, after removing it,
180343 -     there could another space if a sentence starts after the end of
180344 -     the citation, and is separated by 2 spaces.  So, check this
180345 -     position and do macro 79 to collapse the string to the cursor
180346 -     position again.
180348 -      ..
180349 -     Line 520, ref OF 7 6R5L, -label rrefa about 50 lines below,
180350 -     complete loop looking for citations in action item description
180351 -     lines, by returning to look for another citation in the same line.
180352 -     Sometime this can happen, so we need a loop.
180353 -        ..
180354 -        Use citation type OF based on 88 = 79, see above,
180355 -        ref SDS 0 MA4H, to identify the length of the citation string,
180356 -        since there are only two lengths, either 2 or 3.  If it is not
180357 -        an OF, then the length must be 3.  This value is used to
180358 -        determine whether the ref string was long enough to include the
180359 -        anchor, based on where the cursor winds up captured by counter
180360 -        89, after removing the citation string using macro 79.
180361 -        ..
180362 -        If the length is not long enough to include an anchor, then
180363 -        the anchor is on the next line, so set a flag 88 = 999, processed
180364 -        as the first task to remove the anchor, per above. ref SDS 0 O99I
180365 -
180366 -
1804 -

SUBJECTS
Description Action Item Transfer New Schedule Task, Macro 1188, 1189

190301 -  ..
190302 - Look for Another AI Description Line to Transfer from Original SDS
190303 -
190304 - Line 550, ref OF 7 U16F, -label aielp after a task description line
190305 - has been entered in the Schedule task record, and any citations have
190306 - been removed from the line, go back to original SDS record and see if
190307 - there is another description line for this Action Item, per beginning
190308 - of loop, above. ref SDS 0 UW5G
190309 -
190310 -
190311 -
1904 -

SUBJECTS
Link New Task to Original Sources, Macro 122, 136, 985
Context Link Above Action Items in Original SDS Record
Save Original SDS Record When Links Added
Modify Macro 985 Avoid Using Macro 01211, Incorporate in to 070301
Secrecy Confidentiality Privacy When Links Added

240701 -  ..
240702 - Link Action Item in New Task to Original SDS Record, Macro 122, 136
240703 -
240704 - Line 530, ref OF 7 H28O, -label eancr after all description lines
240705 - have been entered, mark the end of the last line for linking, with
240706 - macro 122.
240707 -
240708 - Set up the end of the line so the link does not wrap, by splitting any
240709 - length beyond column 60.
240711 -  ..
240712 - Line 610, ref OF 7 TM5K, -label mfl return to original SDS record,
240713 - using ecur 5, and restore cursor to beginning of action item
240714 - description, using macro 7.
240716 -  ..
240717 - If there is an anchor on the Action Item, then the user has selected
240718 - this location to provide context, so go execute the link.
240719 -
240721 -      ..
240722 -     Provide Context for Action Item Link
240723 -
240724 -     Line 600, ref OF 7 MY9N, -label mfl position original SDS record
240725 -     to give action item context by using or creating an anchor in
240726 -     explanatory text above the action item.  Look for anchor within 15
240727 -     lines of Action item, and if none, then scroll up to the first
240728 -     para above target Action Item and create an anchor on a blank
240729 -     line.
240731 -      ..
240732 -     As users gain experience with the system, they will provide
240733 -     anchors to give Action Items context, and if not, then when an
240734 -     Action Item follow up record is created, they can make any
240735 -     adjustments desired, then run the report again, since it only
240736 -     takes a few seconds.
240738 -  ..
240740 -  ..
240741 - Line 630, ref OF 7 AK4G, -label eancr, about 20 lines below, return
240742 - to origial SDS record and call macro 136 to execute a link back to the
240743 - listing for the Action Item in the new Schedule task.
240744 -
240745 -     Macro 136 figures out if an anchor for a link has been entered,
240746 -     and sets flag for macro 985 to use the anchor or create one, then
240747 -     calls macro 985 to execute the link.
240749 -      ..
240750 -     Macro 985 creates the anchor, if necessary, using macro 987.  If
240751 -     an anchor was created, macro 985 justifies the para, if the anchor
240752 -     was not on a blank line.  If the anchor is created on a blank
240753 -     line, i.e., between paragraphs, the para is not justified, to
240754 -     avoid commingling separate paragraphs.
240756 -      ..
240757 -     If an anchor was added, the revised original SDS record is
240758 -     saved.
240760 -      ..
240761 -     There are two competing issues...
240762 -
240763 -     a.  Saving an SDS record that is revised with new anchors, is an
240764 -         issue for uploading to the web, because if the Action Item
240765 -         record is submitted to others for follow up, they could click
240766 -         on a link and not get the original source.
240768 -          ..
240769 -     b.  If we run 070405 to setup an SDS record for uploading to the
240770 -         web, this would significanly slow the process.
240772 -          ..
240773 -     c.  Security, privacy and confidentiality issues arise from any
240774 -         process that automacitally puts an SDS record in a position to
240775 -         be uploaded for public view.
240777 -          ..
240778 -         Records can be marked for avoiding being moved to the upload
240779 -         transfer directory, and they can be marked to purge sensitive
240780 -         material from publication.  However, whenever an automatic
240781 -         process is used, there is a chance that without direct
240782 -         examination, that a record would be disclosed that is
240783 -         preferred to be witheld.
240784 -
240786 -      ..
240787 -     Code from 01211 Incorporated into 07031 to Save Memory
240788 -
240789 -     Line 1930, ref OF 3 QS4G, -label arcvR2 in 000006 modified today
240790 -     by adding conditional to exit when 127 = 888, set in 070301, per
240791 -     above, ref SDS 0 DG8M, so that it does not call macro 01211 to
240792 -     complete the link in the target SDS record.
240794 -      ..
240796 -      ..
240797 -     Line 460, ref OF 7 4131, -label 2ndpas, about 50 lines below, the
240798 -     code in macro file 01211 (called by macro 985) is incorporated
240799 -     directly into 070301 today, to save memory overhead of loading
240800 -     another macro file.
240801 -
240802 -        The 01211 code initially loads purge command to close the file
240803 -        after all action items in the report that are in the original
240804 -        SDS record have been transferred.
240806 -         ..
240807 -        This revision enables the 070301 process to avoid opening and
240808 -        closing the same record repeatedly for every action item in a
240809 -        particular SDS record, by setting up when an original SDS
240810 -        record is first opened to purge the record, per above,
240811 -        ref SDS 0 TH4J,  and executing it only after all action items
240812 -        in the record have been transferred to the new Schedule task
240813 -        SDS record.  This may help solve a memory problem that has
240814 -        prevent us from processing more than 10 or records, before the
240815 -        operation crashes.
240816 -
240817 -
2409 -

SUBJECTS
Justify Description Action Item

250301 -  ..
250302 - Justify Action Item Description in New Schedule Task SDS Record
250303 -
250304 - Line 830, ref OF 7 8KF3, -label lp2s4 after the link has been
250305 - entered, if there is not a link on the top line of the action item
250306 - description, justify the description in new Schedule task SDS record,
250307 - and reset char read flags for next operation to read in control
250308 - fields.
250309 -
250310 -    In early testing using standard justify macro 49, coded in 000001,
250311 -    there were a lot of system crashes.
250313 -     ..
250314 -    Therefore, instead of using macro 49, decided to incorporate code
250315 -    from macro 49 in file 000001, into this macro file 070301 because
250316 -    experience using macro 49 shows it seems to cause Medit to run out
250317 -    of memory and crash when used repeatedly.
250318 -    ..
250319 -    We can streamline and customise the generic operation of
250320 -    macro 49, so hopefully, it will be more stable in this operation
250321 -    which requires a lot of repeated use.
250323 -     ..
250324 -    This change, along with changes for opening links, ref SDS 0 R85L,
250325 -    and incorporating linking code into 070301, ref SDS 0 B18H, now
250326 -    seems to be working.  It is a little slower than using the compiled
250327 -    macro, but it is 1000 times faster than doing this work manually.
250329 -  ..
250330 - Line 860, ref OF 7 JG7G, -label lp2s4 about 60 lines below, split
250331 - citations, if the first 3 params do not all fit on the same line.
250332 -
250333 -
250335 -  ..
250336 - Link Avoid on Headings to Maintain Record Formatting
250337 -
250338 - Line 920, ref OF 7 AL6I, -label mtl about 170 lines below, after a
250339 - link is entered from the new action item to the original source, check
250340 - for the link being on the top line of the para, and if it is there,
250341 - split it to the next line, and jump justify, because that could put
250342 - the link back on the top line.
250343 -
250344 -      We don't want a link on the top line of an action item
250345 -      description because that causes a web browser to display the
250346 -      the heading incorrectly, and it messes up fonts, bold and all
250347 -      other formatting for the rest of the file.
250348 -
250349 -
250350 -
250351 -
250352 -
250353 -
250354 -
2504 -

SUBJECTS
Control Field Transfer from Original SDS Record

260301 -  ..
260302 - Control Field Transfer from Original SDS Record to New Schedule Task
260303 -
260304 - Line 920, ref OF 7 9K6M, -label mac23z about 20 lines below, after
260305 - action item description is justified, set up to enter control field
260306 - above the description of the action item, if it is different from the
260307 - prior action item.
260308 -
260309 -    Reset flags for macros 1188 and 1189.
260311 -     ..
260312 -    Return to original SDS record, ecur 5.
260314 -     ..
260315 -    Capture Control Fields to track an Action Item in the original SDS
260316 -    record where it is flagged. We will get the entire thing because
260317 -    that is the only practical means to perform this step.  User will
260318 -    in most cases have to edit the Schedule Task Action Item review
260319 -    record so that each each Control Field contains only the subjects
260320 -    that identify it.
260321 - ..
260322 - Line 830, ref OF 7 RQ3I, find top of Control Field.
260323 -
260324 -    This is only needed on the first pass, because if there are
260325 -    multiple action items to process in the same original SDS record,
260326 -    they are located and placed at the top of the screen.  Only the
260327 -    first one that is positioned by macro 98 is in the middle, but
260328 -    using immed / is only a single command, and so the redundancy does
260329 -    not affect performance.
260331 -  ..
260332 - Line 860, ref OF 7 IM4K, -if @10 = @11 -goto samRed gets a Control
260333 - Field once for all Action Items that it identifies in the Action Item
260334 - report.
260336 -  ..
260337 - Line 900, ref OF 7 5N3H, -label stupov after the first pass entering
260338 - a Control Field, insert the Control Field above the date and
260339 - descripton for the SDS record that identifies the Action Item in the
260340 - new Schedule task SDS record.
260341 - ..
260342 - Line 930, ref OF 7 EU9K, -label stupov use macro 1189 to enter
260343 - Control Field into new Schedule SDS record task; when the double
260344 - underline is encountered, or a blank line, the Control Field operation
260345 - ends.
260347 -  ..
260348 - Setcnt 86 1 to make sure 1189 starts with 1, then run run macro 1189
260349 - to enter the Control Field string in the new Schedule task file.
260351 -  ..
260352 - After entering the string, check for a 0 in counter 7 and a double
260353 - line char in counter 8, since either of these can signifiy the end of
260354 - the Control Field operation.
260355 -
260356 -
260357 -
2604 -

SUBJECTS
Control Field Only 1 Subject Transfer to Save Memroy, 970505

270301 -  ..
270302 - Control Field Transfer Only One Subject to Save Memory
270303 -
270304 - Line 940, ref OF 7 GW8G, -label stupov about 30 lines below, had to
270305 - use a "fudge" to improve Medit memory management.  The code is wired
270306 - to capture all control field lines and descriptions, but to reduce the
270307 - memory load, will only get a single control field line and
270308 - description.  If we ever solve the memory problem, we can unplug this
270309 - work around, and do the program correclty.
270311 -  ..
270312 - Line 990, ref OF 7 5Y6J, -label lpcfo at the end of the Control
270313 - Field, if a double line was not encountered, enter one to underline
270314 - the description field.
270316 -  ..
270317 - Line 1020, ref OF 7 G34I, -label upagn after entering the Control
270318 - Field in the new Schedule task SDS record, locate the bottom of the
270319 - Action Item description just created.  If the Action Item is below
270320 - the same Control Field, as the prior Action Item, then the Action
270321 - Item is at the top of the screen, and so it is not necessary to look
270322 - for it.
270323 - ..
270324 - Line 1020, ref OF 7 T45M, -label samRed, below the Action Item
270325 - add 7 blank lines, scroll up and enter a Status line to create a
270326 - clearly marked area to report.
270328 -  ..
270329 - Line 1050, ref OF 7 566N, -label samRed, about 15 lines below, use
270330 - ecur 17 to return to the Action Item report file to see if there is
270331 - another AI for this record to process.
270333 -  ..
270334 - After entering the Status field in the new Schedule task, return to AI
270335 - list report and do an up.  Check length of the line.  If it is less
270336 - than 10, it is blank, so all of the Action Items for this record have
270337 - been processed.
270339 -  ..
270340 - Line 950, ref OF 7 GW8G, -label stupov about 40 lines below, we are
270341 - crashing on big files.  Part of the reason is we are getting the full
270342 - depth of the Control Fields, with descriptions, which is what should
270343 - be done; however, this at least doubles the size of the file, and so
270344 - memory use.  Since the thing is crashing on long Action Item reports,
270345 - will try here to get just the top Control Field and top description.
270346 -     ..
270347 -     The extra code is identified by *******  Two small sections.
270349 -  ..
270350 - Enter immed dd to begin deleting this section of AI report file, then
270351 - jump to top and read the record ID to purge it.
270353 -  ..
270354 - Line 1070, ref OF 7 H24J, -label jmp1 immed dd completes removing
270355 - this segment from AI report and position cursor to process next
270356 - segment.
270358 -  ..
270360 -  ..
270361 - Line 1120, ref OF 7 P44J, -label aaif set flag 227 88 if there is
270362 - another AI in the original SDS record being processed, so we can avoid
270363 - using macro 98 that requires a separate processor, per above.
270364 - ref SDS 0 R85L
270366 -  ..
270367 - Line 2000, ref OF 7 716F, -label jmp1 about 30 lines below, complete
270368 - purge operation of SDS record processed, and if all of the records
270369 - have been processed in the Action Item report, then end this
270370 - operation.
270372 -  ..
270374 -  ..
270375 - Line 1080, ref OF 7 KP9G, -label sRed about 80 lines below, reset
270376 - counter 112, each pass in new Schedule task SDS record, ecur 45, so
270377 - Action Items are counted for each record included in the report, per
270378 - above. ref SDS 0 NT9K
270380 -  ..
270381 - Line 1100, ref OF 7 P44J, -label aaif if there is another Action
270382 - Item in the same SDS record to process, set flag 227 88
270383 -
270384 -
270386 -  ..
2704 -
2705 -
2706 - 000006
2707 -   ..
270701 - Line 50 -entry 972, this is where a record is opened from the
270702 - Schedule Summary.
270704 -  ..
270705 - Line 625 - trying debug 100 here.
270707 -  ..
270708 - Line 650 -label prGSm, about 30 lines below, this is where the code
270709 - loads file:
270710 -
270711 -                      h: sd 05 02 0203051
270712 -
270713 -     ...to use for a blank new record.
270715 -  ..
270716 - Trying debug here to see why the code is stopping after opening a new
270717 - record.
270718 -
270719 -    ..
270720 - Line 2440 -label jmp90, about 35 lines below, added flag for
270721 - macro 101 to stop before it updates line numbers and gets to the error
270722 - message that stops processing.  We use counter 46, per the code in
270723 - file 070301, described above, and at ref OF 7 line 75.
270724 -
270725 -
270726 -
270727 -
270728 -
2708 -

SUBJECTS
Close Menu, 910731
Opening/Closing Menus, 920612

2904 -
2905 - 000003
2906 - ==============================
2907 -   ..
290701 - Line 830 -label ActnItm, added this new menu choice so we can
290702 - have some new menu options for Action Item reports that are different
290703 - from standard subject reports.
290705 -  ..
290706 - Menu is crashing on the second pass for Action Item reports called
290707 - from the Schedule menu.  It is working correctly when called from the
290708 - Subject report menu, but the automatic Action Item list from the
290709 - Schedule menu purges the subject report menu and so the code cannot
290710 - get back to it to reset the profile.
290712 -  ..
290713 - Line 180 -entry 80 is main menu code.
290715 -  ..
290716 - Line 215 -entry 80, about 35 lines below, added setcnt 80 0, per
290717 - explanation below for -label r30t.  Unplugged setcnt 83 0 to save
290718 - memory.  It does not seem to impact anything.
290719 - ..
290720 - Line 1635 -label DLogmu, about 40 lines below, this is where the
290721 - menu crash problem is occurring.  We are not resetting the profile
290722 - because Q1 has been purged for Action Item reports called from the
290723 - schedule.
290725 -  ..
290726 - Line 350 -label onej, about 45 lines below, unplugged pf7 pfe and
290727 - pf11 to save memory because we are running out of compiler space
290728 - again.  These are never used.
290730 -  ..
290731 - Line 880 -entry 810, we are getting another crash when we execute
290732 - 070301 from the menu in the Action Item report after having first
290733 - opened a record with macro 98.
290735 -  ..
290736 - Line 1170 -label r30t, actually it appears that the code is crashing
290737 - when it executes the character read string macro 1182.  The cursor is
290738 - jumping several lines.
290739 - ..
290740 - After that problem occurs then macro 804 causes the file to
290741 - jump.
290742 -
290743 -     Trying setcnt 80 0, at ref OF 1 line 216, to avoid the condition
290744 -     in macro 118 which is part of 000007, per below.
290746 -  ..
290747 - Line 1215 -label r30t, about 55 lines below, we call macro 804 and
290748 - this jumps the file.
290749 -
290750 -
290751 -
290752 -
290754 -  ..
2908 -
2909 -
2910 - 000007
2911 -   ..
291101 - Line 585 -entry 118, trying debug here.
291103 -  ..
291104 - Looks like the problem might be that this code uses counter 80 1000
291105 - as a flag for reading a string length and counter 81 is the string
291106 - length and it is set to 186, so the cursor keeps going and wraps.
291108 -  ..
291109 - Will try setting counter 80 0 in the menu execute operation of macro
291110 - 810, per above.
291111 -
291112 -     That solved the problem.
291113 -
291115 -  ..
2912 -
2913 -
2914 - 000008
2915 -   ..
291501 - Line 1890 -entry 1572, created new macro to assign function keys
291502 - and mouse buttons after leaving a menu screen.  It is used in 06112,
291503 - 0703 and in 000003 at Line 1635 -label DLogmu, about 40 lines below,
291504 - the the explanation above and below.
291505 -
291506 -
2916 -

SUBJECTS
Subject Report, 06112
Action Items, 950729
Menu Top Subject Report Screen
Action Items in Subject Report, 06112

320601 -  ..
320602 - 06112  Action Item Added to Subject Report
320603 -
320604 - Follow up ref SDS 3 0002, ref SDS 2 0006.
320605 -
320606 - Menu at top of screen has an Action Item entry.
320607 -
320608 -     Default shows:
320610 -      ..
320611 -     F1  Action Items, Pending (A,C)
320612 -
320613 -        User needs to change the "P" to either a or c to designate
320614 -        either All action items, or only Completed action items.
320615 -
320617 -  ..
320618 - Line 100, ref OF 5 4690, -label cOProf_1, changed F1 to call
320619 - only Action Items in Subject reports.
320621 -  ..
320622 - Line 190, ref OF 5 4556, -label F1ai, sets following flags for
320623 - selecting SDS record segments that have action item status set...
320624 -
320625 -          127 = 1  Pending action items
320626 -          127 = 2  All action items, pending and completed
320627 -          127 = 3  Completed action items
320628 -
320630 -  ..
320631 - Line 1080, ref OF 5 8855, -label curDr about 20 lines below, evaluate
320632 - current control field line number to determine if it is the same
320633 - record segment.
320635 -  ..
320636 - Line 1550, ref OF 5 2067, -label cOstp_00 about 60 lines below, we are
320637 - using charcnt command to evaluate if a control field line is part of a
320638 - common record segment, so it can be deleted.
320639 -
320641 -  ..
320642 - Line 1850, ref OF 5 T56F, -label cOEND in 06112
320643 -
320644 -    -if @127 > 0 -gosub AItms
320645 -
320646 -        If action item flag is on, go do a loop. ref SDS 0 3Y5L
320647 -
320648 -
320649 -
320651 -  ..
320652 - Line 2010, ref OF 5 386M, -label AItms in 06112
320653 -
320654 -    -label AItms
320655 -    line @10
320656 -    setcnt 0 0
320657 -    l/02/
320658 -
320659 -        Main action item loop that removes everything but action
320660 -        items.
320661 -
320662 -
320663 -
320665 -  ..
320666 - Line 1705, ref OF 5 5386 -label Prof, resets profile for subject
320667 - reports.
320668 -
320669 -               macro 1531
320670 -               macro 1571
320671 -               pf1 errormsg User <Enter> key
320672 -               pfent macro 98
320674 -     ..
320675 -    Changed this code by calling a new macro 1572 created in 000008
320676 -    that does these four steps so the code in 000003 for existing menus
320677 -    can reset the subject and action item report profiles.
320678 -
320679 -
320680 -
320681 -
320682 -
3207 -

SUBJECTS
Action Items, macro 0703, 950701

3303 -
3304 - 07030
3305 - ==============================
330601 -  ..
330602 - Line 210 -label prof, this is the profile for a single Action Item
330603 - report.
330604 -
330605 -               macro 1531
330606 -               macro 1571
330607 -               pf1 errormsg User <Enter> key
330608 -               pfent macro 98
330610 -     ..
330611 -    Changed this code by calling a new macro 1572 created in 000008
330612 -    that does these four steps so the code in 000003 for existing from
330613 -    menus can reset the subject and action item report profiles.
330614 -
330615 -
330616 -
3307 -

SUBJECTS
Assignments
Action Item Reports

3604 -
3605 - 050416
3606 - ==============================
3607 -    ..
360701 - Line 30 - ref OF 9 3260 created this new macro file for action items.
360702 - Will add call to create an Action Item Review record, and another
360703 - function using the same macro file (070301 #2) at a different position
360704 - to append the current Action Item to the current Action Item Review
360705 - record.
360706 -
360707 -
360708 -
3608 -