CONTACTS 

SUBJECTS
Intranet, HTML Code
Memo Convert SDS Record to HTML for
Update HTML Data Base for SDS
Create Data Base, 06116
HTML Code

0907 -    ..
0908 - Summary/Objective
0909 -
090901 - Follow up ref SDS 19 1539, ref SDS 18 4747.
090902 -
090903 - Changed 06116 and 070405 that convert SDS records to HTML.  Now the
090904 - dose /c command method of processing only 20 records at a time is used
090905 - for both creating and updating the data base.  Added feature to avoid
090906 - trying to convert older SDS records that have format problems.
090907 -
090908 - Added privacy flag processing in 070405 so that records can be marked
090909 - with Alt F10 "f" in the "01" description line to avoid being entered
090910 - in the HTML data base. ref SDS 0 2480
090911 -
090912 -    [On 980324 added code to support blocking access to a particular
090913 -    linked record. ref SDS 22 2386]
090914 -
090915 -
090916 -
090917 -  ..
0910 -
0911 -
0912 - Problem
0913 -
091301 - The HTML data base update program is failing on the following subject:
091302 -
091303 -                        c: 03 00050 01
091304 -
091305 -           ...which is marketing.
091306 -
091307 - I think it is working for the other accounts.
091308 -
091309 - Actually, this is not true.
091310 -
091311 - The record on 971206 says we can update 10 years of data with this
091312 - routine. ref SDS 14 2504
091313 -
091314 - If it worked before, it is not working now.
091315 -
091316 -  ..
091317 - The update stuff was created on 971208, ref SDS 16 0630,
091318 -
091319 - I am not sure what the problem is, but we are getting persistant
091320 - system crashes on the update opearation.  The function to create the
091321 - initial data base seems to be working better.
091322 -
091323 - For most subjects, we can create the initial data base all at once.
091324 - This evening, I found that on several subjects the update data base
091325 - function would fail after processing only several hundred records.
091326 -
091327 - I changed the code in 06116 and in 070405 so that updating processes
091328 - only 20 records at a time, which is the way initial data base
091329 - creation works.
091330 -
091331 - I found after making this change that we continued to get hung up on
091332 - updating.  Investigation indicated that 070405 was crashing on SDS
091333 - records with older formats, which should have impacted creating the
091334 - initial data base, since it uses 070405, as well, so I added code to
091335 - avoid converting these records.  If there is an oder record someone
091336 - wants or I want to have in the data base, then I can convert its
091337 - format.
091338 -
091339 -
091340 -
091341 -
091342 -  ..
0914 -
0915 -
0916 - Progress
0917 -
091701 -  ..
091702 - 061160 - Develop method to Update DB in Increments
091703 -
091704 - Follow up ref SDS 18 0001.
091705 -
091706 - The update code that calls 070405 seems to have been created on
091707 - 971208. ref SDS 16 3665.
091708 -
091709 -      It sets counter 268 1 as a flag for 070405 to exit back. ref OF 2
091710 -      2838
091711 -
091712 - Line 295 -label Intrnt, ref OF 2 3168, about 30 lines below, trying to
091713 - unplug the code that jumps directly to update a data base.  Will try
091714 - to use the code that processes only 20 records at a time.
091715 - ..
091716 - Our problem seems to be the routine that does a dos /c to get a
091717 - dir listing to compare existing HTML files for determining which need
091718 - to be updated.
091719 -
091720 - Line 305 -label Intrnt, ref OF 2 5838, I am going to try saving the
091721 - processor 06116 as Q1 to disk, since that is how the code in 06116 is
091722 - called, and will call Q1 #39 against the 1y list.
091723 -
091724 -     Right now 070405 has code in it that processes the 1y list for the
091725 -     main routine of creating the initial data base,
091726 - ..
091727 - Line 350 -label 1yout, ref OF 2 6014, if we are updating the
091728 - data base, enter a char for a flag in 1y at the top, so when dose op
091729 - runs on file 1y it has a way of distinguising between a new data base
091730 - and an update data base. ref SDS 0 5301
091731 -
091732 - Line 380 -label ovR, ref OF 2 3618, changed the code so if it is an
091733 - update operation, the file 1y is processed by Q1 #39.
091734 -
091735 - Line 420 -label lpInt1a, ref OF 2 2425, this is a new label for the
091736 - update code that begins in 1y.  It will process only the 20 files
091737 - listed in 1y, ref OF 2 2808, then exit back to DOS which will return
091738 - to Q1 and do another 20.
091739 -
091740 -      [On 980325 had to change num of recs to process from 20 to 5. ref
091741 -      SDS 21 1368]
091742 - ..
091743 - Line 450 -label lpInt1a, ref OF 2 6023, added code to evaluate
091744 - 1y file under the dose op to see if there is a char in line 1 col 1
091745 - which indicates it is an update data base function, per ref SDS 0
091746 - 2448.
091747 -
091748 -
0918 -

SUBJECTS
Intranet, HTML Code
Memo Convert SDS Record to HTML for
Create HTML Data Base for SDS, 06116,

1206 -
120601 -  ..
120602 - 070405 - Avoid Processing Old SDS Records, Format Doesn't Work
120603 -
120604 - Follow up ref SDS 19 2932.
120605 -
120606 - This needs to avoid processing a record that uses the old SDS format
120607 - because it gets messed up.
120608 -
120609 - Things like 4 place line numbers, instead of 6, and control field
120610 - descriptions that have a single line underline instead of a double
120611 - line, and has text below the description underline, instead of spaces.
120612 -
120613 - We will test each record for 6 place numbers in the Reference field.
120614 - If they do not exist, we will not convert to HTML.
120615 - ..
120616 - Line 145 -label HupD, ref OF 3 4320, added code to kick out of
120617 - routine adding HTML, if following condition does not exist:
120618 -
120619 -                    030101 -
120620 -
120621 -     ...this is fairly indicative of the old format record.
120622 -
120623 -     Of course there are likely some records that have this format
120624 -     correct and other stuff messed up, but I don't want to test for
120625 -     every conceivable problem.
120626 -
120627 - Line 1965 -label overA, ref OF 3 6419, added error messages when
120628 - 070405 is called to convert a single SDS record into a Web page, and
120629 - the record has the old format.
120630 -
120631 - There is also an error message when an SDS record is marked "private"
120632 - which is a new feature created below. ref SDS 0 2480
120633 -
120634 -
1207 -

SUBJECTS
Intranet, HTML Code
Memo Convert SDS Record to HTML for
Syntax
No Anchor use Standard ref to Diary Date
SDS Records

1708 -
170801 -  ..
170802 - 070405 - Avoid Converting Links that Have No Ending Parameter
170803 -
170804 - The code is crashing on the record for 930324 at ref SDS 3 4449.
170805 -
170806 - Looks like the hang up is on the code that converts SDS links when
170807 - there is no target position specified.  A spec like:
170808 -
170809 -                     xef xxx 3?
170810 -
170811 -      ...or
170812 -
170813 -                xef xxx 4 is a problem.
170814 -
170815 - Actually, the latter is not a problem because the code encounters a
170816 - letter for the parameter and it wants a number.  What is happening is
170817 - that if xef sds 4, or xef dip -- occur at the end of a line, then the
170818 - code puts the cursor on col 1 of the next line and it evaluates as a
170819 - citaion link number, because we are using numbers.
170820 -
170821 - Line 1365 -label lpcn1, ref OF 3 4411, this begins entering code for
170822 - references in the body text.
170823 -
170824 - Line 1410 -label ref2, ref OF 3 4570, this seems to be the code that
170825 - may be failing.
170826 -
170827 -     I added setcur 1 here because if reference string does not have a
170828 -     parameter such as line or cite spec, and if this is the end of the
170829 -     line, then -gosub fccode, causes the cursor to wind up on column 1
170830 -     of the line below.  We have been testing only if the cursor winds
170831 -     up on a number, and since col 1 is the line number, it was passing
170832 -     this test.  Adding setcur improves the test to ensure there is
170833 -     actually a reference parameter, so that if there is not, as was
170834 -     occurring in this particular record, then the reference will not
170835 -     be processed.
170836 -
170837 -     Will I ever understand what this means?
170838 -
170839 -
170840 - The code is crashing on the record for 950223, ref SDS 6 3170.
170841 -
170842 -    I examined the record carefully and find no apparent cause.
170843 -
170844 -    This took a lot of hours.  The only thing I am aware of doing is
170845 -    converting all of the reference for SDS with line params to the new
170846 -    format.  Line param, however, should not cause the report to crash.
170847 -
170848 -      [On 980324 added feature for line params to open new standard
170849 -      anchor at top of record on Diary date field. ref SDS 21 6525]
170850 -
170851 -
170852 -
170853 -
1709 -

SUBJECTS
HTML Suppress from Web Page Publication
Concept Design Objectives
Functions, entering HTML
Suppress Private Records from Diary Report by Another User
Suppress Confidential Records from Others, 940423

2208 -
220801 -  ..
220802 - Private SDS records, Flag 01 Description to Suppress Publication
220803 -
220804 - We need a way to prevent confidential SDS records from being published
220805 - on the web.  We can use the same flag that prevents one user from
220806 - getting records for another user that are confidential, reported on
220807 - 940423. ref SDS 4 2562
220808 -
220809 -      [On 000329 enhanced system. ref SDS 24 0001
220810 -
220811 -      [On 001018 improved system again. ref SDS 25 8910
220812 -
220813 - User enters any character in column 3 between line number 01 and the
220814 - dash of the record description line, for example an x, as shown for
220815 - this record, above, and here...
220816 -
220817 -
220818 -         01x- Improved SDS update data base for HTML.
220819 -
220820 -
220821 - This is applied in two ways...
220822 -
220823 -     1.  Publishing a single SDS record, publication is blocked by
220824 -         macro 1420 in 000008. ref SDS 0 PDW2
220825 -
220826 -     2.  Publishing multple records selected in a subject report and
220827 -         processed by 070405. ref SDS 0 5808
220828 -
220829 -
220830 -    [On 980324 added code to block access to linked records. ref SDS 22
220831 -    2394
220832 -
220833 -    [On 000329 specific parts of a record can be suppressed without
220834 -    marking it confidential and blocking access to the entire record.
220835 -    ref SDS 24 5040
220836 -
220837 -    [On 000821 prepared Help for confidentiality. ref --- 87 E354
220838 -
220839 -
220840 -  ..
220841 - 0000008  Avoid Call 070405 to Convert SDS record, Macro 1420
220842 -
220843 - Line 2390, ref OF 6 5585, -entry 1420 any character in column 3 on
220844 - the 01 record description line will prevent calling 070405 that
220845 - publishes SDS records to the Internet.
220846 -
220847 - Line 2410, ref OF 6 WH6F, -label pubLit after verifying the record is
220848 - not confidential, verify the record belongs to the current User, and
220849 - if not prevent publication on the web.
220850 -
220851 -
220852 -  ..
220853 - 070405 - Avoid Converting Private SDS Records to HTML Data Base
220854 -
220855 - Line 160 -label HupD, ref OF 3 1342, this is just above the code that
220856 - checks the file to see if the old SDS record format, so these records
220857 - are not coverted. ref SDS 0 2300
220858 -
220859 - This code is for the subject report process that assembles a lot of
220860 - records for publication.  It kicks out a record that is flagged
220861 - confidential per explanation for macro 1420 under 000008, above.
220862 -
220863 -
220864 -  ..
220865 - 04702  Avoid Posting SDS Record Suppression Flag as Action Item
220866 -
220867 - Line 2060, ref OF 1 2414, -label bRFol_up this is where lines marked
220868 - with f for follow up are archived, and placed in SAA for follow up.
220869 -
220870 - Want to avoid entering the follow up line marked to support the
220871 - record from publication on the web.
220872 -
220873 - Line 2100, ref OF 1 4560, -label bRFol_up created code to this by
220874 - adding flag to test for first pass looking for f following up flags,
220875 - and on the first pass will evaluate 2 lines above for Summary/Obj, by
220876 - looking for Su, then restoring initial condition; and if Su is
220877 - encountered on the first pass, will look for the next follow up flag.
220878 -
220879 -    Actually, we don't really need this because the flag is entered on
220880 -    the record description line, not Follow up below Summary/Objective,
220881 -    and we are not entering a follow up symbol, "f," but any character,
220882 -    like an x, for example.
220883 -
220884 -     [000329 this work was actually performed. ref SDS 24 8910
220885 -
220886 -
220887 -
220888 -
220889 -
220890 -
220891 -
220892 - 000821 F5 marks for linking combine with target for copy, move.                                                                                                  000821 184346 00101