THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700


S U M M A R Y


DIARY: November 4, 1990 07:48 AM Sunday; Rod Welch

Develop demo version of SDS, review directory structure for SDS.

1...Summary/Objective
....Contacts Broken Down
....SDS Records - Method #1
....Records - Method #2


..............
Click here to comment!

CONTACTS 

SUBJECTS
SDS Marketing, Distribution
Schedule/Status (admin
for this general account)

0505 -    ..
0506 - Summary/Objective
0507 -
050701 - Need diskett packaging and written instructions.
050702 -
050703 - Prepare batch file to assemble program onto a single diskett.
050704 - Need front end for Demonstration, explaining they can make 100
050705 - activities.
050706 -
050707 - Files to include in 01 03 directory.
050708 -
050709 - Made CNS so if summary is empty, it will tell Users how to begin
050710 - making CNS records.
050711 -
050712 -
0508 -
0509 -

SUBJECTS
SDS Marketing, Distribution
Dir Structure and Filenames
Directory Structure

0706 - Objectives
0707 -
070701 -  ..
070702 -
070703 - Configure SDS so entire thing sits under a single directory.  Finally
070704 - adopted method #1. ref SDS 0 VL6F
070705 -
070706 -      [On 930717 reviewed ideas on directory structure. ref SDS 5 0001
070707 -
070708 -
070709 -
070710 -
070711 -  ..
0708 -
0709 - Dir design
0710 -
071001 - Let the name of the program be "SDS"
071002 -
071003 -   We would like to have three char to ensure uniqueness, but maybe
071004 -   we can get by with two, where it is a dir level.
071005 -
071006 -   Will try to set this up on g:
071007 -
071008 - ...then
071009 - ..
071010 - Drive Letter
071011 -
071012 -   Decided for now not to eliminate the drive letter so that network
071013 -   users can access the data base on different drives.
071014 -
071015 -   Maybe we need a network version, and a single user program, where
071016 -   the latter would not specify the drive.
071017 -   ..
071018 -   For now will continue to specify the drives.  But this will
071019 -   not let User's put the thing on different drives.
071020 -
071021 -   Entire program will have to be on a single drive, of course, it is
071022 -   not too difficult to revise this, as we have been doing with macro
071023 -   0802.
071024 -   ..
071025 -   The hard part is changing all of the macros to address the
071026 -   data base on different drives.
071027 -
071028 -        [On 910307 worked on drive assignments. ref SDS 4 0001
071029 -
071030 -     C: SD 01 = Program files
071031 -     H: SD 02 = Fonts for printing reports
071032 -     C: SD 03 = Macros and development files for compiled e.exe
071033 -     H: SD 04 = Menus
071034 -     H: SD 05 = Help
071035 -     H: SD 06 = Subj Index
071036 -     H: SD 07 = Reminders
071037 -     D: SD 08 = Data base (see detail below, ref SDS 0 VL6F)
071038 -     H: SD 09 = Contacts (see detail below)
071039 -     C: SD 10 = Null (always empty for temp storage)
071040 -
071041 -
071042 -     ..
071043 -    Contacts Broken Down
071044 -
071045 -    SD 09
071046 -    SD 09 01 = Record nums, and Summaries
071047 -    SD 09 02 = Organizations contact records
071048 -    SD 09 03 = Individuals contact records
071049 -
071050 -
071051 -     ..
071052 -    SDS Records - Method #1
071053 -
071054 -    SD 08
071055 -
071056 -    SD 08 UUUUU                        = User ID 5 character field
071057 -
071058 -    SD 08 UUUUU 00                     = Current Schedule directory
071059 -                                         where all tasks originate
071060 -
071061 -             All SDS records begin as scheduled tasks to plan the work.
071062 -             When work is performed, a scheduled task is converted into
071063 -             an SDS diary record to guide performance and report on
071064 -             what was done, like this record.
071065 -
071066 -  ..
071067 -    SD 08 UUUUU 01                     = Control Field subjects
071068 -                                         for organic structure
071069 -
071070 -                These are pointers for assembling reports.
071071 -
071072 -    SD 08 UUUUU 02                     = Records of SDS diaries
071073 -
071074 -                    Diary records are where work is performed and
071075 -                    reported.
071076 -
071077 -    SD 08 UUUUU 02 YY                  = Year directory
071078 -
071079 -  ..
071080 -    SD 08 UUUUU 02 YY MM               = Month directory
071081 -
071082 -    SD 08 UUUUU 02 YY MM DD            = Day directory 7J
071083 -
071084 -  ..
071085 -    SD 08 UUUUU 02 YY MM DD HHMMSS     = Diary files constructed by
071086 -                                         program for hour, minutes and
071087 -                                         seconds
071088 -
071089 -    SD 08 UUUUU 03                     = References to formal documents
071090 -                                         these are 03 lines
071091 -
071092 -                     Documents issued and received and other files for
071093 -                     formal publications, like a book, article, or a
071094 -                     software programming file, a spreadsheet.
071095 -
071096 -                     This directory merely stores pointers for looking
071097 -                     up records where a particular document was used.
071098 -
071099 -  ..
071100 -    SD 08 UUUUU 04                     = Diary descriptions 01 lines
071101 -
071102 -                     Stored for quickly making summary reports
071103 -
071104 -    SD 08 UUUUU 05                     = Contact pointers 02 lines
071105 -
071106 -                     Stored for quickly making reports where particular
071107 -                     people and organizations are listed
071108 - ..
071109 - Is it better to backup by all users, or by all dates.  Probably
071110 - one day soon, we can put globals in dir levels in the backup routine,
071111 - and this matter will be moot.
071112 - ..
071113 - Another consideration is to facilitate transferring records and
071114 - archiving.  Would it be helpful to organize the dir structure so each
071115 - user's records can be transferred by year?  Under method #1, we will
071116 - have to make 5 passes, one for each data type.  As well, when records
071117 - are organized by year, then as new records are added, fewer files have
071118 - to be moved during disk maintenance (i.e. compression).
071119 -
071120 -     ..
071121 -    Records - Method #2
071122 -
071123 -    SD 08                                = Data Base
071124 -    SD 08 UUUUU                          = User
071125 -    SD 08 UUUUU 00                       = Schedule Records
071126 -    SD 08 UUUUU YY                       = year
071127 -    SD 08 UUUUU YY 01                    = Control Field
071128 -    SD 08 UUUUU YY 02 MM DD HHMMSS       = Records, month, day filename
071129 -    SD 08 UUUUU YY 03                    = Ref
071130 -    SD 08 UUUUU YY 04                    = Record Descriptions
071131 -    SD 08 UUUUU YY 05                    = Contacts
071132 -
071133 -    I don't have a good feel for advantages and problems that might
071134 -    arise from this structure relative to the one above.  My tendancy
071135 -    is to not disrupt the natural date order by injecting the data
071136 -    type, as shown above.  To handle data by year, we will have to
071137 -    make 5 passes, but this may not be a big time consuming effort.
071138 - ..
071139 - Decided to use method #1, per above. ref SDS 0 VL6F
071140 -
071141 -        [On 930717 reconsidered trying method #2. ref SDS 5 597I
071142 -
071143 - Did the work in another record today. ref SDS 3 0001
071144 -
071145 -
071146 -
071147 -
071148 -
071149 -
071150 -
071151 -
0712 -
0713 -