<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
There's all sorts of applications where having a deeper than two
dimensional hierarchy would be very nice. <br>
<br>
For example, I'm managing a fledgling downtown association site which
is somewhat crippled by two dimensionalism.<br>
<br>
HealthCare.Dentistry.DrA, HealthCare.MD.DrA and
HealthCare.Dentistry.DrB is not possible under PM wiki. Nor is<br>
Financial.Banks.WellsFargo, Financial.Insurance.JoesInsurance, and
Financial.Mortgage.MikesMortgage. Nor is<br>
YouthSports.Soccer.Girls.Team94 and YouthSports.Soccer.Boys.Team95.
Etc. etc. <br>
<br>
Sure, there are (somewhat clumsy) workarounds. <br>
<br>
HealthCare.DentristryDrA, HealthCare.DentistryDrB. However, neither
of these secondary sites can have their own private 'group site' unless
they go to something like DentistryDrA, BoysSoccerTeam94. This format
also somewhat complicates logical references to parent groups, which in
a hierarchical site would be fairly easy.<br>
<br>
The same thing applies to a couple youth sports team sites I'm working
on. <br>
<br>
Club.Boys.Team90 has to be ClubBoysTeam90 if each player for the team
wants their own personal page for that team. There's workarounds, but
the results are always not entirely logical. <br>
<br>
As for clinical applications (assuming security issues could be
addressed), it might be possible to develop a rather free form clinical
database with proper data structures. <br>
<br>
HOHBobJones/Tommy HOHBobJones/Bob comes to mind (HOH is head of
house). Tommy would have his own pages of data as would Bob.... <br>
<br>
Or schools<br>
<br>
LocalElementary/TeacherJones/StudentBobbySmith <br>
<br>
Exactly how many more examples do you need? <br>
---------------<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:christian.ridderstrom@gmail.com">christian.ridderstrom@gmail.com</a> wrote:
<blockquote
cite="midPine.LNX.4.64.0605282107000.17247@black01.md.kth.se"
type="cite">Is there some wiki page that contains user cases that
illustrates cases where one would like to have some kind of hierarchy?
If not, I think maybe we should start one.
<br>
<br>
The long thread on hierarchical groups was interesting, but I think I'd
like to start with understanding why it is needed. (As an aside, I'm
all for having some kind of hierarchy, but knowing why we want
something will help us see what we want).
<br>
<br>
As for motivation, what I do know is that all the technically savvy
people I've introduced to pmwiki lately have all assumed that some kind
of hiearchy was possible. Several of them felt that some kind of
hierarchy was necessary for technical documentation of a stuff like a
product structure.
<br>
<br>
/Christian
<br>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
pmwiki-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pmwiki-users@pmichaud.com">pmwiki-users@pmichaud.com</a>
<a class="moz-txt-link-freetext" href="http://host.pmichaud.com/mailman/listinfo/pmwiki-users">http://host.pmichaud.com/mailman/listinfo/pmwiki-users</a>
</pre>
<pre wrap="">
<hr size="4" width="90%">
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.7.2/349 - Release Date: 5/26/2006
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Always, Dr Fred Chittenden
</pre>
</body>
</html>