Hi All

I seem to be having a problem, but I'm not sure if it's my IK-naivety, or a bug.

We have a number of test KBs. If I'm in KB2 or KB3, when I hit  Queries I usually get sent back to KB1. This sometimes happens with Build and other modes too. I said "usually" because sometimes I can get into, say, Queries in KB3, and create a new query. However, when I run the query it always runs against KB1 and not KB3, which is where I had been until that point.

It seems a little too easy to slip between KBs without the user realising that it's changed. In some modes, the KB name is visible at the top left while at other times it's replaced by the name of the mode. Is this intentional? I can think of possible unintended consequences here.

Any illumination would be welcome. 

Thanks!

Andy

Thinking aloud...

OK, I've worked out a partial answer.

It seems that when you create a query, unless you specify otherwise, it will run against the entire database, and not just the knowledgebase you're currently in. If you're interested only in the current KB, you have to explicitly state that as one of your criteria.

So a tip may be that when you create a new KB, get itno the habit of setting up a query along the lines of "Show All Content Records in [this KB]".

It seems we have to change the way we think about KBs. In v6, KBs were completely separate  entities. They were different databases. In Incite, a KB is really just another grouping of records within the same database. Maybe we need to think of them as super-Categories.

Does this explain why I get sent to another KB when I hit Build? I'll need to think about this some more...

Hi Andy,

Yes, there are a handful of places where the system looks at the first knowledge base with content in it as the starting point.  As we get feedback about that, we're hearing that it ought to be more aware of where you are.  Shouldn't be hard to address, so thanks for pointing out a couple of the places you're bumping into this!

I think your tip is a good idea.  And I think one of the other things to think about is when you want a knowledge base and when you just want another category.  Given that you can now have very deep category structures and data security privileges to them, having another knowledge base may not be necessary in inciteKnowledge, where it may have been the best choice previously.

Yes multiple knowledge bases live in a single database so that they can be searched together and the like.  So in the sense that they're an organization mechanism for content in the database, you're right that they have similarities to categories.  But of course they are more than that, with other properties that categories don't have. 

Thanks for posting!

John

Thanks for the reply. 

I don't think this is a major issue, more like a need to get accustomed to a conceptual change. New users of the Pragmatech/Kadient products would probably not notice, as they never knew it any other way. Existing users migrating to the new platform just need to be aware that switching KB is not such a big deal as it used to be.

Previously, changing KB was useful when you wanted to work on a copy, or test something out with zero risk to your data. On the other hand, it was often inconvenient to have to unload/load databases. So I guess it's swings and roundabouts.

That said, it would be better to be kept in the same KB when the  the user changes mode. In the majority of cases, I suspect the user would want and expect to be in the same place. It's non-intuitive to end up somewhere else without warning.

PS The forum is a good idea, but an Edit function would be useful. Thanks.