In the container for the text of a book, there is a note for each chapter and within chapter containers a note for each section. Sections have footnotes. There are several hundred, distinguished by three prototypes. All footnotes are created as siblings. In Map view, the display is very messy. Cleanup makes it worse with footnote notes showing up far from the sections they’re linked to and the lines impossible to follow. Dance is a little better but still not good. I can resolve the problem by moving each footnote into the section it relates to. I sort the section containers, using their prototype, by the prototypes of the contained notes and then by Name. Not only orderly, but makes it easy to move between the Text pane of a section and the footnotes. Also provides nicely organized Hyperbolic views of the section.
Given the quantity of footnotes, I would like to include a rule in each footnote prototype that would move each instance into its section container. It would be a simple rule: "$Container = Container + the attribute that identifies a link source if I could find that attribute . But the only thing I find in the list of system attributes are the various link counts. BrowseLinks and Roadmap clearly make use of link attributes, but don’t indicate how to identify or designate them. I tried using a relative reference: when a footnote is created the source section shows up as its nextSibling, but that creates a mess when another footnote executes the rule, even with the rule ending with $RuleDisabled=true.