Loading...
 
Features / Usability

Features / Usability


Creating a knowledgebase with typed relationships

posts: 26

I'd like to create a knowledgebase or data wiki (using trackers if necessary) where each page/item has the following fields:

1. Name (Title)
2. Type
3. Content (wiki parsed)
4. Table of links with these fields:
* title of linked item
* type of linked item (e.g. "excerpt from journal article")
* semantic relationship (e.g. "similar to")
* text note about the link or relationship

I'd like to add rows to the table of links with the benefit of autocomplete and filtering. For example, if I write that the type of linked item is a "journal article", then the autocomplete on the title would only draw from journal articles.

As a prototype, I tried to use a tracker with the following fields:

1. name (text field) the item's title
2. type (dropdown) assign item to a broad source type, like "excerpt from personal journal" or "excerpt from journal article"
3. content (text area) the item's content (wiki parsed)
4a. similar (item link) one-to-many connection with similar items in tracker
4b. different (item link) one-to-many connection with dissimilar items in tracker

I defaulted to fields (4a) and (4b) because I couldn't figure out how to add rows to a table of links where each row is a tuple of dropdown menus or lookups. Instead, I hard code just two semantic relationships (similar and different) and allow multiple selection for each. I do not store the type of the linked item or a note about the link.

Here are my questions:
1. Is there a better approach either via wiki page templates or better use of trackers?
2. How do the "Link Page" and "Add Items" options work exactly in the Options for Item Link fields and what functionality do they make possible?

posts: 8384 Israel
Da'ud Vyd wrote:
I'd like to create a knowledgebase or data wiki (using trackers if necessary) where each page/item has the following fields.../...


I have a similar solution and implemented a few:
https://www.bernardsfez.com/Knowledge-database-management-web-app

I would use:
Trackers to store and record the data.
Wiki page (template and semantic alias) + plugin List and customSearch to display and search
MySQL search engine is good, elasticSearch engine would give more flexibility (like better auto-complete, facets, etc)

Relation between items is doable of course, but (in my point of view) this is already more than just a general answer and your use case should be carefully reviewed.

If this help; The relation fields can do such job but it needs a "value" to match or unmatch.
You can use a field value or "create" a value using the mathematical field.
For exemple, if you have a tracker Orders with several fields (id, date, name, product, price, etc...)
You create a field in tracker that will create a value like : id | date | product | name
Then you use this field with many searchable values to create searches or relations.

Note that I had some issue lately with this for the dates.
Somehow "dashes" are considered like spaces and searching for 2021-04-04 will return anything that contains 2021-x-x (you have to use exact or replace the dash)

Hope this helps


posts: 126746 United Kingdom
Da'ud Vyd wrote:

I'd like to create a knowledgebase or data wiki (using trackers if necessary) where each page/item has the following fields:

1. Name (Title)
2. Type
3. Content (wiki parsed)
4. Table of links with these fields:
* title of linked item
* type of linked item (e.g. "excerpt from journal article")
* semantic relationship (e.g. "similar to")
* text note about the link or relationship


Hi Da'ud Vyd

Everyone knows i'm a huge tracker/list plugin fan but in this case i think i'd try doing this with just wiki pages 😱

Everything you need i think is there in pages, the Type can be a category, and the table of links could either be in a wiki template as you say, and/or in a plugin alias combining a few plugin lists. Semantic links are supported too so i'm not sure what benefit the tracker would all - but as always, there are many different ways to achieve things in tiki, and you often don't find out you picked the wrong one until after the first prototype mrgreen

Good luck!


posts: 26
Thanks Bernard and Jonny. I'm still experimenting with the simple tracker I developed. I'll post here any updates.