[silva-dev] plans for reference management

[Christian Zagrodnick]

On 10.04.2005, at 11:40, Roman Joost wrote:

> On Sun, Apr 10, 2005 at 01:07:31AM +0200, Clemens Klein-Robbenhaar 
> wrote:
>> [...] LMS and CMFLinkChecker
>>
>>>> In order to avoid concurrent development on same features, I'd like 
>>>> to
>>>> discuss this topic on the mailinglist first. So, what are your 
>>>> plans for
>>>> the future of reference management?
>>   Well, my plans are to try to get rid of the current, single point
>> reference checking and more to get into the direction of reference 
>> management.
>>   The first step would be to maintain all references in Silva content 
>> objects,
>> instead of fetching them globally in each reference check.
>>   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...
>
>>   This seems to require to add a hook to the versioning / workflow
>>   machinery, however.  I am not sure what to do with non-versioned
>>   content, especially containers.
> Well, in the Plone world, the CMFLinkChecker retreives the links from
> the document, after it's beeing saved. It passes these to the LMS, 
> which
> checks the links sequential.

Sequential.. well. No. It does parallel checking of links on different 
hosts. One host is only checked once a second.

>>   Roman: If we want to coordinate our work on improving the current
>> SilvaReferenceChecker checker, how do we do that? I do not have the 
>> resources
>> to set up a public CVS server or the like. I thought about an archive 
>> at
>> SorceForge maybe, but the last time I asked on this mailinglist if
>> other developers of Silva add-ons would be interested in having some
>> "Silva common add-ons" repository there I got no response thus I did 
>> not
>> tried that so far.
> Well, such a "collective" sounds nice indeed. I think, I could use the
> CVS server from gocept for such a product. If we have more extensions
> for Silva and it makes sense to collect them in a sourceforge project
> I'll go for it. Btw. we might think of using berlios.de - they offer a
> SVN repository instead of CVS.

You could of course use gocept cvs or anything else – but please avoid 
Sourceforge. I don't really know if the situation improved, but we made 
some very bad experiences.


-- 
Christian Zagrodnick

gocept gmbh & co. kg · schalaunische strasse 6 · 06366 koethen
www.gocept.com · fon. +49 3496 3099112 · fax. +49 3496 3099118


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2355 bytes
Desc: not available
Url : http://lists.infrae.com/pipermail/silva-dev/attachments/20050419/b8815cd3/attachment.bin