[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: External Site Mirroring & Indexing - Delegation Conditionally Accepted (fwd)
> > I do whole heartedly agree with everything else on the requirments
> > document, including the complete web based maintenance, support for
> > CmdSchedule, etc. We need to discuss the ability to "differentiate"
> > and how that will happen more though I presume.
> So with that in mind, I suggest a new Object Type and a new table called
> OffSiteLinks to hold these non-mirrored external docs. The only real
> issue is should these off-site links be in the main index or only linked
> off other inhouse/mirrored documents. I prefer the second.
No. They maintain the same information. It'll stay in the same table. We'll just add a flag to
the "ExternalLink" object type called "Remote", and if it's set, the rendering script will do a
redirect, if it's not, it'll get displayed inline.
> > Internal/External Documentation. Eventually we'll maintain the
> > knowledge of wether it's a KB Support Article, a User's Manual, an
> > INstallation HOWTO, etc. So we want to keep this future in mind as we
> > design the current system...
> Sounds like a Xref table that the different article tables
> (internal/external) can reference. I Think this would be a great
> feature. Imagine each article having a "type" associated with it telling
> the user if it's a Short HowTo, Long HowTo, Manual, Man Page, etc.
Actually... there'll be an easier way to do it with the DB, but we can discuss those details
later... but yes, the whole type thing will be VERY nice. Yet another way to quickly tell what the
links are in a search result page, or to narrow down quicker... for example, select I want to search
only "Installation HOWTO's", and then enter "Apache" on the search line, or select it in the App
list and leave the search line blank... or... You leave it set to "All Doc Types" and enter sumthin,
and once the result page comes back, have the ability to sort by, and filter on Doc types... alot
of power there.
I started thinking about it when reviewing the spec's to LinuxDOC, which had support for such
things... I'm hoping DocBook does/will as well.
>
> > ______________________________________________ End of comments as seen
> > on PS
> >
> >
> > On Mon, Nov 29, 1999 at 08:49:49AM -0500, Daniel E. Markle wrote:
> > > On Sat, Nov 27, 1999 at 03:19:54PM -0800, Aaron Turner wrote:
> > > > The KB is a place for direct answers (such as the Microsoft KB is), not for
> > > > docs.
> > >
> > > I agree with this and disagree, I believe the knowledge base needs to consist
> > > of direct answers, but I also believe that external docs are often the best
> > > source to answer some questions. In other words, we need both, not just one
> > > or the other IMHO.
> > >
> > > --
> > > -------------------
> > > Daniel E. Markle
> > > syntax@ashtech.net
> > > http://www.ashtech.net/syntax
> > > -------------------
> >
> > --
> > Jason
> > http://vodka.linuxkb.org/~chardros
> >
>
> --
> Aaron Turner, Core Developer http://vodka.linuxkb.org/~aturner/
> Linux Knowledge Base Organization http://linuxkb.org/
> Because world domination requires quality open documentation.
> aka: aturner@vicinity.com, aturner@pobox.com, ion_beam_head@ashtech.net
>
>
--
Jason
http://vodka.linuxkb.org/~chardros