THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net
S U M M A R Y
DIARY: May 25, 2003 05:14 PM Sunday;
Rod Welch
Consider new SDS report on where SDS record listed as a Reference.
1...Summary/Objective
..............
Click here to comment!
CONTACTS
SUBJECTS
Reference Field Maintain in Sync with Citations and Links
0503 -
0503 - ..
0504 - Summary/Objective
0505 -
050501 - Follow up ref SDS 3 7800, ref SDS 2 3542.
050502 -
050503 - Thinking about expanding References report to create a list where an
050504 - SDS record is listed as a Reference in another SDS record.
050505 -
050506 - [On 040331 Gary asks about this type of report.
050507 - ref SDS 7 1W6O
050509 - ..
050510 - This has marginal utility, since we have been using SDS for 20 years
050511 - and this has never come up.
050513 - ..
050514 - Usefulness is diminished somewhat because once a record is linked to
050515 - another record, it tends to be carried forward even though it may not
050516 - be needed for a citation, and so the correlation or meaning of having
050517 - a record listed in References is not very great. Today, a new need
050518 - seems to come up for finding where someone else's records might be
050519 - linked.
050521 - ..
050522 - There has been consideration of maintaining references to remove
050523 - anything that is not cited in the record. After the new feature was
050524 - developed last month on 030429 to list SDS "foundational documents"
050525 - automatically in References, ref SDS 4 0001, this tends to cause a lot
050526 - documents to be listed that are not actually used in a record.
050527 - Irrelevant references are then carried forward when a new record is
050528 - created.
050530 - ..
050531 - Automatic maintenance could be done once a day when a record is
050532 - archived, in order to permit a user to hold a range of references that
050533 - help construct a record, rather than delete anything not cited when
050534 - the record is saved.
050535 -
050536 - [On 031107 developed this feature. ref SDS 6 6H6K
050538 - ..
050539 - This is largely a new issue.
050541 - ..
050542 - We can use c: 01 04 061110.
050544 - ..
050545 - An efficient system would require extracting the list of References to
050546 - build another big pointer file. This takes up a lot of resources, but
050547 - on the other hand the cost of disk storage is almost 0 in this
050548 - context, that should not be an issue. It would take longer to start
050549 - SDS because another set of pointers would have to be processed. This
050550 - might add 5 - 20 seconds to launch.
050552 - ..
050553 - Adding new code to 04702 will increase the problem of memory
050554 - management on the 640K issue. Not sure this is a big deal.
050556 - ..
050557 - For now I am going to defer this, because it might take 3 or 4 hours
050558 - to do the work, and I want to use that time for getting ready to meet
050559 - with Pat Lincoln on Tuesday. This includes the studying the issue of
050560 - transformation of attitudes about ability of people to use good
050561 - management as a result of gaining experience using SDS according to
050562 - the plan, perform, report design of SDS, which Gary mentioned
050563 - yesterday, and is evident in his work the past few months.
050564 -
050565 -
050566 -
050567 -
050568 -
050569 -
050570 -
050571 -
050572 -
050573 -
0506 -