Re: plans for reference management

Hi Roman,

sorry for the late reply ...

[...]
>>  Because updating the references each time someone edits a document seems
>>a bit overkill to me I feel the step of approving a document (or some other
>>versioned content) seems to be the right time to fetch the references
>>contained in the approved version.
> 
> But it may be too late after publishing the document that an author is
> informed about broken links. So, he has to alter and
> publish the document again to fix the broken links. That are to steps to
> get a document with correct links in it. But you're right, if the
> document contains a vast amount of links, it'll be overkill...
> 

  Well, I thought here about an additional button "check references" which
triggers a referenced check on the editable version. This would make it possible
to check links before approving th document.
  Currently this does involve patching the Silva core product (via the files in the
"patches" directory -- certainly out of date for the current Silva versions.)


  By the way I figured out that I have left a rather ill documented
feature in the product: the "ReferenceChecker" class has an attribute
"linkchecker_factory", which defaults to returning objects of my little ugly
link checker hack. A little more information is in the APT.txt
(though I think I should have proofread that file before releasing it ...)

  Maybe this is an easy hook to get the LMS in ... still need to look into
LMS en detail.

Cheers,
Clemens