Hierarchy
geilhufe - March 13, 2006 - 20:22
| Project: | Liquid Wiki Engine Project |
| Version: | HEAD |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I've found it very useful to be able to structure parent-child relationships among wiki pages. This is particularly useful when you can present that structure to the end user.
I believe there is some broader conversation about relationships on Drupal-dev which may or may not be relevant.
Soren- This is a great contribution. Thanks for taking it on!
You can see an example here:
http://objectledge.org/confluence/pages/listpages-dirview.action?key=CRM
#1
A (perhaps too) simple approach would be to extend the namebinding feature in the following way:
Say you want to create a wiki node called Audi under annother node called Cars. You then insert it with the name "Cars.Audi" (should perhaps use another delimiter than dot, but just as an example). The node should now be accessible under /wiki/Cars/Audi, the title should be Audi (if tie title to wiki ID is enabled) and the breadcrumbs should be Home >> wiki >> Cars.
The best thing about this approach is that it integrates well into the existing code. Pages can be moved from one parrent to another (or to root) using the move feature as is, and so forth.
Do you think this would work?
#2
this is how dokuwiki does it and it seems to work well. they call each level of the hierarchy a 'namespace'. the term namespace will become evident after you read [1]. aso see the links at bottom of [1].
[1] http://lists.edgewall.com/archive/trac/2004-August/000576.html
#3
Namespaces as Taxonomies
It almost seems as if Namespaces are just a special case taxonomy? Maybe I'm missing something here? A namespace enforces a title based UID. So within the Namespace of Car you are allowed to have only one instance of the word Audi. As long as this rule is enforced for a given taxonomy topic, then it may function as a namespace. This will allow some interesting features:
(1) Larger Hierarchies
Example: Cities often have name conflicts, with the same name used in many different locations. Name conflict is a common challenge for large wikis.
(2) Distributed Namespaces
If we wish to maximize sharing of content between drupal Wikis, then management of Taxonomy Clouds may help us handle distributed Namespaces.
You may take a look at the “Taxonomy Cloud” project inside civicactions.net (http://dev.civicactions.net/?q=node/113 - Creation of a service to share taxonomies across Drupal sites)
(3) Leveraging of Taxonomy
Taxonomy is a mature module with strong community support.
Thx - James
#4
#5
Hierarchy support is included in the 5.1 release (but you should probably download the dev version).
I haven't had the time to think trough how taxonomy can be used for wiki's. Will do some day :D
#6
There is also the clipper module, but I like the DokuWiki concept a lot better?
#7
Hm... it would be interesting to see if one could add support for Clipper in the sense that a clipper structure is created and maintained in parallel with the wiki structure. This might be even more useful when linking structures are being supported by the filter module.
I'll look into that.
Thanks for tipping me off!
/S
#8
You bet! Thanks for all the hard work on the module. There's also the Node Relativity project which I just began looking at.
#9
#10
What is the syntax for making hierarchies work per http://drupal.org/node/53793#comment-193655?