Re: What about non-DB articles?

["Aaron D. Turner" <aturner@pobox.com>]

-----BEGIN PGP SIGNED MESSAGE-----


On Thu, 18 Mar 1999, Jason Pincin wrote:

> > LDP
> > OSS Web Pages on line (Apache SAMBA, etc)
> > man pages (we can use man2html for this)
> > /usr/doc (we can use text2html for this)
> 
> We use related links.  We may want to expand the table, add the capability to
> assign keywords to related_links and so forth.  Then you stick the DNS HOWTO in as
> a related link, give it the keywords... and there ya go... never more than one hit.

Please explain more.  What does htdig index/search against?
 
> Basicly... I created the related links table for any "external" documentation,
> meaning - not an article under the KB's complete control.

Ok, but I don't understand how it works.  Ie:

1) Do "related links" only relate back to other articles, or can they be
"articles" in and of themselves?

2) What gets placed in the drill-down list?  A direct link to the HOWTO or
to a page that references the HOWTO

3) How far down should htdig index?  To the "related link" link in the
drill-down?  To the actual HOWTO index?  To all the pages below the HOWTO
index?

4) Assuming you don't index the entire HOWTO, how do you get all the words
in the HOWTO indexed by htdig?

> > Another thing I desperately want to do is us host all the data ourselves.
> 
> Thats fine.
> 
> > Ideally we'd sync once a week to a holding area and have it report on the
> > pages that have changed/new.  That way we can go over whats changed and
> > weed out broken links etc before migrating it to production.
> 
> Well... without having a firm understanding of what your discussing here... I'd
> say, if we mirror these sites, there not going to radically change there structure
> daily... so we build indexes of the files ourselves as well... then via cron we
> compare those indexes to what is in our RelatedLinks Table, and spit the changes
> out to be reviewed, have keywords modified, or whatever...

Not sure what you're saying either. :-)  At least we don't need to worry
about it this second.  Cross that bridge when we get to it.  My thought
didn't involve the MySQL DB, which yours does, so I say we go with yours
unless we find something seriously wrong with it.

- -Aaron


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNvHEBDM3jpXy1kJtAQEMQQQAlF+aztsb1BWRBV0UqZWo/qQoIZ/12x8O
A6CLQVHusT81xa9G0JGvEJ4R4jqzpZ51CaHi2kWgI9Ga691MdzkQWFWeMGNq8HPa
6nvc5p4QzsaDzSOSLW9iCf0MF0ZVkCHKBB7yl6BiutX/dtdHmkcgZgGA/8Il4aA6
XUeT2U1A57I=
=8Zot
-----END PGP SIGNATURE-----