WikiMatrix / Hierarchical Links

jfdub · 2008-06-30 17:45:16

Don't know if I'm referring to this correctly but hopefully I can explain what I'm trying to do. I have TWiki up and running on Apache and working wonderfully, but here's my problem. When I think of hierarchy I think in terms of 'folders' or 'directories'. Which would mean, for instance, you could have the following:

-Customer List
--XYZ Customer
---Opportunities
---Projects
--ABC Customer
---Opportunities
---Projects

When I try to create this hierarchy, whatever 'opportunities' link I create first becomes the only 'opportunities' I can ever create. I need each opportunities to be 'linked' to either XYZ customer or ABC customer. Does that make sense?

I just tried creating a Web called 'CustomerList', then sub-webs of 'XYZ', and 'ABC'. That gives me the behavior I'm looking for but then searches are complicated (for the 'regular' user, if they don't check 'search all webs' then they won't see anything. Plus I hear that creating a lot of webs is not recommended.

Anyway, I'm not trying to reinvent the wheel, just wondering if there are any suggestions out there on how to proceed.

Thanks!

eldgie · 2008-08-13 19:07:07

You're right that nested webs in TWiki are a bit problematic. In our TWiki installation, where our policy is to avoid using sub-webs, we make extensive use of filename prefixes, so that, for instance, every topic about XYZ Customer would be named with the XYZ prefix, e.g., XYZOpportunities, XYZProjects. This also makes it easy to run searches on filenames (XYZ*) to gather all the docs with a particular prefix.

Remember that even if the filename is ugly or unreadable, like XYZOpportunities, you can label your link on the page in a more friendly way: [[XYZOpportunities][Opportunities]]

PeterThoeny · 2008-08-21 04:27:19

What you try to achieve can be done with a TWiki application. TWiki is a platform to build web applications. The application logic is done at the page level with the TWiki Markup Language. With a TWiki applications users simply fill out forms and run reports to do their work, e.g. the wiki aspect is of lesser importance.

TWIKI.NET [1] created a Sales Pipeline Tracker (SPT) TWiki application. It consists of three tables: Account table, contact table and SPT table. At the top level you see the list of accounts (companies). A web form is used to add a new account. Each account lists two tables: One listing all contacts linked to that account (with a link to add a new contact), the other one listing the sales opportunities. A workflow is defined for the sales opportunities, with stages Prostect, Eval, Quote, ..., Collected.

Screenshot showing clickable map with workflow:

Please contact me if you are interested in learning more about the Sales Pipeline Tracker.

-- peter.thoeny.public [at] twiki [dot] net - http://www.twiki.net/ - http://twiki.org/

#1 2008-06-30 17:45:16

Hierarchical Links

#2 2008-08-13 19:07:07

Re: Hierarchical Links

#3 2008-08-21 04:27:19

Re: Hierarchical Links

Board footer