Fairhaven, The River

Dell U2711 and getting full resolution

The documentation from Dell and others is utterly atrocious, so people like me write posts like this to help others with their setup.  First, although Dell never documents this, these are the limits for various kinds of input:

• DisplayPort can do the full 2560x2048
• DVI-I Dual Link can do the full 2560x2048
• VGA can only do up to 2048x1152.  (Interpolation makes text a bit fuzzy.)
• DVI Single Link can do up to 2048x1152
• HDMI I can't test properly.

Then there are the variations of support by various systems.  Vendors do not document their hardware well enough to know what will work without trying it.  I have found:

• MacBook Pro with MacOS, DVI-I Dual Link is supported at full resolution
• Intel D94GZIS with Windows 7, DVI-single link at 1600x1200, DVI-VGA Adapter at 2048x1152
• Intel DH67CL with Linux and Intel Driver 2011Q3, VGA adapter to DVI works at 2048x1152, DVI only up to 1600x1200
• Dell Latitude 630 in Docking Station: DisplayPort at full resolution

The documentation and connector for the DH67CL claim dual link capability but after various experiments I've found no way to configure the driver to use it properly.  Documentation of the Intel driver provides no information about dual link setup.  The default configuration did not set it up automatically. 

Good podcast video from MIT Libraries

This video (1.5hr) stood out from the crowd that I usuallyscan.  It's got good insights into the learning processes of high-end digital native kids (MIT undergrads), the needs of a modern library, what MIT's educational life is like, and where MIT libraries are heading.  Some of it's obvious and some was surprising.  For example, the changing role of books on paper was not what I expected.

Org-mode, documents, and XDS

I've created an org-mode date-tree for organizing my various documents. This leads to some thoughts on XDS, etc.

Org-mode stuff (skip this if you don't care much about org-mode)

• I've created a date-tree for these documents. 
• Each set of documents gets a headline, with whatever description, tags, and metadata I feel like adding.  This date-tree lives in my regular org files.  So I can now search for tags, concepts, dates, etc. to find headlines.  Then I can read the headlines, their descriptions, and their metadata in order to decide which documents I want to read.
• The attachments are in their own git archive.  I can make this work by having a different attachment directory in each of the .emacs files on each machine.  My first thought of using links in the file system failed because Windows XP does not support links.
• I still need to do extra manual work, but it's now tolerable.  I've created a temporary save area.  I detach the documents from an email into that save area.  I create a headline in the date-tree. The headline text includes key aspects from the email, if any, and a short description of the documents.  I then attach the documents from the temporary save area (which copies them into the org attachment directory) to the headline.  Finally, from time to time I empty the save area.
• The org attachments directory is outside the org tree so that my git sharing of org files doesn't pick up all the attachments too.  Those are managed separately, also by git sharing.  This lets me do things like put the attachments directory on a removable drive.  (This makes the org file vaguely like the XDS Registry, and the attachments kind of like an XDS Repository.)
• Attachments management is adjustable by machine.  On the Mac the nicest way to deal with them is to open the attachments directory for an entry, and then use Mac tools.  On the Linux and Windows, the easiest is to do directory management within emacs and open files from there.  (XDS folks can think of the attachments for a headline as being like a submission set.)
• I had to fix the ~/.mailcap on my Linux system to point the PDF relationship at "evince".  Emacs was opening the PDF files within an emacs buffer.  This works, but it's slow and has a lot fewer features.  It works by converting the PDF into a PNG and displaying that with image display tools.  That's not as good as a full function PDF viewer.  The Mac and PC already have PDFs pointed to the appropriate viewer.

Resulting thoughts on organizers and XDS

This raises some thoughts on the state of information organizers.  Most people still use something like Sharepoint with all of it's preconfiguration restrictions and rules.  Some use wikis, which don't have the tags, properties, and other metadata facilities of org.  (Most wikis also have a lot more problems with editing the content.  The good content editors are platform specific.)  There are various more sophisticated metadata management tools that do a better job with document management.

Org still has too many manual operations.  Properties, tags, etc. are good, but don't integrate well with ontology tools.  (On the other hand, org has no problems with multiple ontologies.)  Tags, etc. are at the level of headlines, so there can be inheritence and the like.  But this is all stuff that you need to set up for yourself.  So it's a tool for tool builders, not a tool for general users.

The potential is there to do all kinds of things since this is build upon a structurally aware lisp engine.  I think I could make this into an integrated XDS Registry/Repository if I felt like it.  The really hard part would be implementing all the SOAP crap and enforcing metadata rules.  Org's attitude toward metadata is "do whatever you want." Org tries to adapt as best it can.

My org approach doesn't have the XDS single registry viewpoint.  But that's because I'm accustomed to systems  and system designs that are normally "broken".  They are inconsistent in contents, etc. in that each different viewpoint may reflect a different set of updates and changes.  The processes exist to reconcile the changes, but there is no requirement to present a consistent or "accurate" viewpoint.

This kind of "it depends on where and when you look" is an inherent necessity for many operational environments.  Presenting a single view requires 100% connectivity, 100% functional, error free network and systems.  In some enterprise environments it is practical to achieve this, or close enough that people don't notice the failures. 

In telecoms management this is impossible.  Networks will have failures that partition the network.  The various parts must continue to operate and be managed based on what information is still available, and they must adapt to mergers, including reconciliation of conflicting information when merging.  In the largest of the networks that I was involved with we never had fully functional networks.  There was always a portion of the network that had failed.  There were always a few islands operating on their own while problems were being fixed.

Healthcare IT folks (like those involved with XDS) are still having real problems coming to grips with accepting a system design that is always "broken".  They don't realize that in healthcare  everything is always "broken" in that sense.  Patients don't provide full or consistent  information, so patient information is "broken".  Measurements are incomplete.  Diagnoses are really just working hypotheses to be tested.  Disease and health are constantly changing, so the recorded state is never correct.  It's like large networks.  You must proceed with incomplete, inconsistent, changing information.

With time they should come to grips with this.

 

A new definition for privacy

Discussion with Gila and a podcast have led me to a new definition for privacy.

Privacy is the control over information to ensure that

• No physical harm results for the person, their family, loved ones, friends, or property.
• No financial, emotional or other harm is done to the person, their family, loved ones, or friends.
• No harm is done to any social relationships of the person, their family, loved ones, or friends.

My new definition is driven partially be a story from a Google security expert at an LSE panel session.  This was during one of the publicity bursts for computer security.  The press was putting about stories about how the public behavior showed that they didn't really care.  She had gone to a morning focus session with some members of the public, and then attended a computer security conference.  The public was actually very concerned about the potential for the use of private information by stalkers.  When she mentioned this to the computer security experts, they laughed, said this shows how little the public understands, and continued on their chosen path.

I think the public was right, although they got some of the details wrong.  So I've rephrased this as a harm prevention goal.  That's the root requirement. 

Gila argued that the requirement includes personal consent and control.  I still disagree.  I consider personal consent and control to be part of the mitigation strategy.

Consider an imaginary world where there is magic pixie dust that can be sprinkled on information.  The magic pixie dust can read minds, understand social relationships, and predict the future.  It ensures that the information is never revealed or used for anything that will cause any of the harms listed above.  In that imaginary world I do not think that any person would complain that they were not controlling or consenting to data releases.  The magic pixie dust will do a much better job, and with much less burden on the person.  People have no ability to read minds, very limited ability to predict and future, and even find much simpler tasks like understanding the complex implications of consenting to a particular policy to be very difficult.

But there is no magic pixie dust.  Current technology is unable to meet most these goals.  Centrally designed policies are a very limited mitigation.  Personal consent and control are another mitigation to deal with the many details that a centrally designed policy will not have.  Considering consent and control as a technology, the inability to read minds, predict the future, etc. still leave many potentials for harm.  Further mitigations are needed, e.g., audit controls and process feedback loops.

By considering consent and control to be a technology for mitigation we have the established framework for recognizing that more mitigations are needed.  Considering consent and control to be the driving requirements closes this path, since the system will have fulfilled its requirements.

There are other social requirements.  The right of personhood is a requirement that every person be able to make the decisions that affect the future path of their life.  In the absence of the magic pixie dust and the inadequacy of privacy mitigations, this right of personhood means that the person should have the control to decide what risks of harm they are willing to accept.

The privacy requirements are also subject to societal restrictions.  I will add the statement:

• Society may choose to inflict harm on a person rather than suffer societal harm.  For example, the privacy of criminals will be reduced rather than accept unrestricted social harm from crime.  There are also more positive motivations, such as the infliction of privacy harm by public health organizations so that other people will have less harm from disease.

 

A good ftp proxy software

I've been using "jwftp" as an ftp proxy for about six months now, and it works very well.  I recommend it.  FTP is a very stable protocol, so "jwftp" is also stable.  It just gets a very occasional tweak to reflect changing operating system environmentts.

This is a bit of a niche interest, but as a security guru I inflict my recommendations onto myself.  Therefore, my home network lives behind some application proxies.  I've had issues getting a good ftp proxy that supports all the various ftp clients and not just the browsers.  This proxy has worked well with not just the browsers.  It's also happy with ftp, sftp, wget, and lftp.  (I personally use "lftp" as a method for intelligent mirroring of ftp sites up and down.  Wget is fine for mirroring downloads, but doesn't do intelligent mirroring uploads.  "lftp" does.)

The audit logs are reasonable to parse, and so far just confirm that the only ftp traffic is authorized traffic that I have initiated.

 

Transition to org - Part 7 of n

(In late March 2010 I installed the latest and greatest version of git.  It has some new rules about configuration, use of bare git repositories, warnings and errors, etc.  The intent is to avoid mistaken destruction of working code by forcing the master repository to be in a different directory than the working copies.  So, I needed to create a bare git repository on my master Linux system.  Then all the machines would have working "org" directories that push and pull to the master.

[2010-03-30 Tue 11:04] Git rebasing

I created an "org-master" that contains the master.  I made sure everything was checked in, then renamed "org" to "org-master".  I then deleted the org directories and recreated them by cloning.  Also, updated the .emacs on the master machine to point back to org as the working directory.  Only git knows that there is an org-master.

The git commands built into emacs have some sort of bug.  The update to latest generated an error rather than updating a file.  I should investigate this at some point.  Right now, emacs automation does not matter.

[2010-03-31 Wed 09:23] Git rebasing

I did the rebasing of org onto a new directory.  It went reasonably well.  The process was:

• I made sure that all the computers were fully synched and consistent with old git archive.
• I renamed the master directory to be "org-master"
• I deleted the old org directories and cloned them from org-master.  Nice thing about git is that the whole history survives just fine.

Everything was still there just fine.

[2010-04-05 Mon 10:56] Org - spreadsheet mode (emacs calc)

I tried this today.  It reminded me of the old supercalc and other predecessors to the modern spreadsheets.  It's not as easy to use as a modern sheet, but it integrates rather well into emacs and org.  So I created a little table of computations rather easily.  I did make one mistake by using "=" rather than ":=" for the formulas.  "=" is a column formula that applies to the entire column.  I didn't notice until later when I went to edit something.  The error was minor and now I'll remember.

[2010-04-20 Tue 07:52] Journal Conversion

(I discovered the "date-tree" facility while looking for something in the new manual.  It's a rather nice addition that organizes notes by date into a hierarchy.  I modified the .emacs to make it easier to gather notes.  My .emacs now has remember config lines of:

(setq org-remember-templates
      '((?t "* TODO %?\n  %i\n  %a" "~/org/TODO.org")
        (?j "* %U %?\n\n  %i\n  %a" "~/org/JOURNAL.org" date-tree)
        (?i "* %U %?\n\n  %i\n  %a" "~/org/ihe.org" date-tree)
        (?d "* %U %?\n\n  %i\n  %a" "~/org/dicom.org" date-tree)
        (?n "* %U %^{Title}\n %?%i\n  %a" "~/org/idea.org" date-tree)))

It would be nice if I could have multiple date trees in one file.  I would like to have a file for one organization, e.g., DICOM, and then have a date tree for my meeting and tcon notes for each working group.  For now, it's one tree for all of DICOM.  I looked at the code and it's moderately complex modifications to have another level of hierarchy like that.  I don't have time to make that kind of changes.)

The date tree stuff seems to be working OK.  Converting from the old form to the new form by hand is not that bad.  The writing of lisp to do it is more work than doing it by hand.  This manual re-organizing is also a good review of past ideas.

Transition to org - Part 6 of N

(Later:  At this point I started using C-c C-! to tag entries with a date.  This now turns into a more sporadic discovery of features and changes to how I use org.  By this point I was comfortably using org as a replacement for planner.  So here's the rest of 2009.)

[2009-03-30 Mon 10:12] Use of remind

I took a quick look at org2remind.  It seems to just move the scheduled and deadline tasks into the remind file with the proper format.  It does not appear to get the other calendar items.

This is not what I am after.  I want something closer to the agenda view.  Remind's interesting scheduling flex would have been nice, but it's not worth the problems.

[2009-04-21 Tue 09:55] Experiment with recipes

I tried making up a test recipe.  Two possible approaches for ingredients:

• I can use a Properties drawer.  This has some search advantages because I can limit searches to properties.  By default the drawer will be closed.  I have to open it manually.  There is a minor disadvantage that an ingredient could only occur once.
• I can use a table.  This is easy to edit, nicely visible.  There is not a search restricted to tables that I noticed.
• I could use a table, and then a property that lists the ingredients.  That would be more data entry, but get both the property search advantage and the nice table.  I could even use tags for this rather than invent a property.  Just tag each recipe with ingredients.  I had originally thought to tag with main dish, dessert, etc.

All look pretty easy.  It's just time and energy doing data entry. A later step is to try to integrate the links with the Firefox scrapbook.  Make a file of recipes and let it be synchronized as part of org.

[2009-04-29 Wed 08:40] Org (outline) search

I just noticed that the org mode incremental search selectively opens and closes outline view as appropriate.  It's probably been doing this all along without my noticing.  I must have been doing searches, although I may have done a bulk outline open first just to see things.

[2009-04-29 Wed 08:46] Recipes

I put in a few recipes.  Right now the process is mostly manual. I've got them in a scrapbook.  As I finish, I move a recipe from one folder to another.  So far it's easier to retype than to use cut and paste.  This could change for more complex instructions.

Next thing to consider is how to organize the linkages back to the originals.  I could continue to use a scrapbook form.  Or I could just use the HTML pages with a file link.  The scrapbook form has more opaque file names.  Pages are tagged by date and time.  It also has the metadata contents, although I've found it to be a little quirky.  The HTML export form uses readable names and has no metadata.

[2009-05-28 Thu 09:28] Search stuff

I finally set up a TAGS file.  Now I have a choice:

• use M-x grep to search for a pattern, and remember to limit it to searching *.org.  This gives the list of all occurrences.
• use tags-search to incrementally search through the files in the order that they occur in the TAGS file.

The etags program makes semi-random guesses when used on org files. I then edited that TAGS file to just list the filenames and have no tags.   

[2009-06-08 Mon 09:17] Categorization

I'm finding it hard to get categorization right at first.  Also, tagging continues to be tricky.  I don't have a good mental categorization of work yet.

[2009-06-08 Mon 09:19] More Recipes

I'm getting recipes slowly converted over.  The manual process of conversion adapts well to the highly variable format of recipes. I've not dealt with setting up a proper storage area for the HTML form.  It needs to be somewhere reasonably stable that I can refer to.  I think it should be HTML format.  The surrounding file structure and naming makes HTML export format more sensible than scrapbook format.

[2009-07-20 Mon 07:58] Parallel editing

I've found that I'm not worrying as much about maintaining proper synchronization.  I'll let the org files get more substantially out of sync.  Repairing the collisions is not that hard.

The typical situation I find is this:

1. I do a "push" or "commit" and git reports a conflict that cannot be resolved automatically.
2. I use "pull" or "git gui" plus commit to get a simple local conflict collision.
3. The conflicts are marked in the conflicting files.  I just edit as necessary to fix.  The biggest early problem was realizing that this cannot be done in org-mode.  I need to switch the buffer manually to text-mode.  The fixes are generally just a matter of deleting or moving lines.  I rarely edit the exact same text.  It is usually a matter of deciding which lines to keep.
4. "commit" and distribute the fixed up version.

Sometimes the changes look complex.  In those cases I'll branch, work on the branch, and merge it back in.  Most of the time it makes more sense to just treat each different computer as if it were a different branch, but without the actual branch tagging.   

[2009-08-16 Sun 14:57] Emacs 23.1 on Mac  

Seems to work just fine.  One keyboard glitch noted so far is with the mapping of the ALT key.  The Carbon port of Emacs 22 remapped this to the Apple-Clover key, which made it much more consistent with other Apple applications.  I actually prefer the new mode of mapping ALT to ALT, since I switch back and forth between Linux, Mac, and Windows regularly.  Cross OS consistency helps me more than within MacOS consistency.

Transition to org - Part 5 of n

Todo Templates

I've found that making a template for various common tasks is easy and useful.  I've created three checklist templates: International travel; long domestic travel (3+ days); and short domestic travel.  It's easy to make a copy and insert it along with the trip specifics whenever I schedule a trip.

This isn't a template for remember to use as a todo.  It's more a pre-packaged mini project plan.

Unicode

I did a cut and paste from a Nature article into Emacs.  It worked fine, but included some non-ASCII characters.  Emacs gave me the option of editing the file or converting the characterset when I went to save it.  I picked convert characterset.  As far as GIT is concerned, I just did a complete file replacement.  This may prove a nuisance later.  I need to check how Mac and Linux respond to this.  The oddball characters are the degree symbol, the plus/minus symbol, and one other.

Checking with Notepad it looks the same.  Checking with Wordpad it looks like there is an extra character in there.  (Wordpad seems to have chosen the angstrom character.)

Scheduled vs not

I figured out that the org set up for dates is a bit different than my usual interpretation.  I had been making appointments scheduled to get them in the Agenda., and then marking them done. But this introduced notification entries a few days early.

Sometimes I want this reminder, sometimes not.  It depends upon whether I need to think about the appointment or do something to get ready.  If it's just the reminder whether this is the recycling week or not, I don't want the reminder.

That is resolved by just putting in a date tag with no scheduled, deadline, closed, etc.  If the date tag has angle brackets it shows up in the agenda.  If it has square brackets it does not.

You see scheduled means "plan to start work on a project" not "this activity is scheduled to take place."  So now I have to remember "C-c ." for appointments that need no prep work.  "C-cC-s" for appointments that I must think about.

Attaching files

I noticed the ability to attach files to tasks.  I need to dig into this more.  My first thought issue is dealing with GUI vs keyboard.  Does this have a reasonable GUI process for finding the file to attach?  It's a pain to have to remember the relationship between the directory structure as seen by the GUI and as seen by the keyboard.

As I read into it, there is a relationship with git, existing git repositories, and existing directories.  This has potential.  I need to read it over carefully.

A new kind of task/note

I find myself more often creating a journal entry describing something and embedding a task within it.  Then I put the journal entry into the generic task list for a project.  This reflects realizing that there are things to do because of whatever it is that I am documented.

Merge conflict resolution

I just finished doing some merge conflict resolution because I swapped between two laptops without synchronizing.  The resolution is easy.  Git had it all nicely marked.  But, org-mode interacted poorly with the markup. It concealed a lot of it.

The resolution is simple enough.  I switched to text mode so that I could see the merge markup. But, it is a potential for errors.

(Several weeks of just use later)

It seems to be working out well.  I've abandoned the notion of using the task stuff for shopping lists.  I just have some sections for the different routine grocery and supply stores. Things get put on a list, then when I go shopping it's copied to paper.  That works better.

Transition to org - part 3 of n

Time tags

I played around with tagging appointments and todo items.  It's got all the stuff I want, except maybe for some of the trickier scheduling.  The one  hard one is the trash schedules.  Pickups are "Every other Wednesday, except if Monday, Tuesday, or Wednesday is an official holiday.  Then it will be Thursday."  This means pulling in an official holiday list and then doing some logic.

The trash thing looks like a lot more complexity than it is worth it.  It's good enough to show it on Wednesday.  I can deal with the off by one for holidays.  I need the computer to keep track of whether this week is a recycling week.  I travel enough that I just lose track of which week has recycling and which does not.

Email Trial

I set up work laptop.  Started just be grabbing latest version from mac, and putting that as initial version on it.  Then I did a git init.  Then a checkout to email branch, did some changes, committed, switched back to main, did a merge, created an email delta, and emailed it.

The email was retrieved, applied, and seems to be OK.  There is a whitespace issue to be fixed to eliminate some whitespace warnings.

Warning days

After a while I found the variable that controls when tasks show up in the agenda view.  It's org-deadline-warning-days.  Default is 14 days.

This leads to an interesting approach change.  I think I'll make most of the tasks without deadline or schedule.  Then use tags to find the ones that I'm after.  The many items were cluttering up the agenda view.

PC Fixes

I'm dealing with variations of the Windows PC.  The biggest headache was getting the .emacs file right.  It lives in the Application Data for my profile, which is not the home directory for cygwin.  This leads to lots of mistakes.

Also, getting longlines to be the default is tricky.  Simply adding it to the auto list is not sufficient.  That turned on longlines and turned off longlines.

Git

Git integration is doing OK.  Org is a lot more like code than planner.  The pattern of changes is much better.  Planner modifies the underlying day files and the project files to reflect deadlines, schedules, current date, etc.  Org does not.  It computes delays, lead times, etc. dynamically.  With all this clutter removed it is easy to manage multiple machine updates and reconcile overlapping updates by hand if necessary.

The more code-like pattern also means that git does better at finding the deltas and fixes automatically.

One issue will be long lines.  The longlines minor mode interacts badly with org tagging.  So I have to use auto-fill mode.  This is fine for text I generate in emacs.  But it's a nuisance when I need to cut and paste into other programs, e.g., blog editors.  For those I would rather have longlines mode.  According to mailing lists there is a mode coming as part of emacs 23 that will deal with this.  Meanwhile, I have a nuisance to deal with when I copy notes into other programs.  (I wonder if the easiest path is to write an "unfill" lisp action.  I could "unfill", cut/paste, then refill.)

(The visual mode in emacs 23 does do what I want.  It just hadn't been written yet.)

Transition to "org" part 2 (of n)

(Continuing, I noted some of the immediately visible differences and annoyances with the change.  This is fairly normal.  The changes that annoy you are immediately noticed.  The improvements are more gradually observed.)

Early annoyance

Org puts the agenda description files into the .emacs file.  That interferes with sharing my files using git.  The directory structures on MacOS, Windows, and Linux are different.  I'll preserve the org directory structure and mirror it. If there were a separate file in the org directory that kept all the org stuff it would be much easier for me to synchronize. 

Early file organization

So far I've decided on on a modest list of files: work, blog, home, and three major project categories.  Within these I've got an orthogonal set of tags for specific useful sorting categories.

I've also made two sequences for TODOs: (TODO, STARTED, WAITING, DELEGATED, MAYBE | CANCELLED DONE) (BUY LATER | DONTBUY BOUGHT).

One is for tasks, the other for shopping lists.

(Later, I made some changes, but these held basically for the past year.)

Early stuff

The .emacs issue continues as an annoyance.  The org system for tracking schedules and deadlines is a lot better.  With some more thought I should be able to use git to merge parallel updates on multiple systems.  It's no worse than the usual issues with software development. 

I need to learn how repeating tasks work.  I've got some.  The repeat schedule was easy enough.  But setting one to complete has some issues.  I need to figure out how best to do that.  Time for more manual and code reading.

I also need to see whether they have work underway to move the agenda definition into a separate file so that my multi-system sharing can be easier.  (They never did, but it's been easy enough to adapt.)

Remember problems   

The [f8] was not starting remember.  Instead it complained about an autoload failure for org-remember. 

• I spent a while fussing with .emacs to no effect. 
• I tried changing (org-install) to no effect.
• I tried deleting the distribution org lisp files to no effect.
• I started reading through the details of how autoload and emacs startup work.
• While deciding which computer system to use to tear apart emacs (because it would likely be non-functional for emacs while I did it) I was doing a line by line read of the .emacs.
• I noticed that (require 'org-install) was missing. Doh. (The real problem.)
• I went to machine Duo (where I had made no modifications beyond putting in the latest remember and org) and tried adding the (require ...).  It behaved properly.
• I have just finished undoing all the changes I made on the mac laptop, where I had done most my experiments.  It now works properly.

Remember templates and archival

The surround environment issues are not as tidy as in planner.  In planner I would get prompts for subjects when I finished the notes.  It would then put a cross-linked copy of the note into the journal section of each subject.  Org does not do this.  (Cross links are still not there, but the rest can be done.)

Org puts the note into the file (subject) where I started the note, or into some other file (it asks) depending on how I finish it.  This is not as useful.  If I later go to a different but related subject I will not see the note.  With planner there will be a copy there if I recalled to add that subject to the note.

Org can easily be extended to add semantic tags to the note.  I might be able to build something out of that, but it's not quite what I want.

I want to have a journal section for each subject, and in that section have a copy of each relevant note.  These should be crosslinked to their copies, and preferably edit protected somehow.  Then one subject should also get the note somewhere in the org outline structure.

It ought to be possible to set up the remember templates to do this.  It's something to do.

I just tried it using remember to create a task linked to this.    The task is created and sitting over there.  There is no indication of that relationship in this file.

(Later: I've ended up using tags and accepting that I can't get fine grained references between one note and several related subjects.  It was a nice planner feature.  I can live without it.)