Dear colleagues,

In a custom list; I would like to implement a directory that may have
the following options:
1.) Categories may contain subcategories and so on.
2.) An item may belong to more than one category or sub-category.

For example:

If Microsoft company would be included in the directory and we have
some categories such as:
1. IT
1.1 Software
1.2 Hardware
2. Finance
3. Research
and assuming we would like to add Microsoft web site to the directory
and that it belongs to (1. IT), (1.1 Software), (1.2 Hardware) and (3.
Research), figuring out a suitable approach causes me headache!
The reason is that I'm limited to not using any thing other than
Sharepoint.
I implemented a content type of type folder in order for me to
maintain the hierarchy of categories; should an item belong to a
single category or sub-category, then another content type in the list
of type item would work just fine; however, the intersection of
association as in the Microsoft example doesn't make that approach
suitable.

If would use a webpart, that would be some how ok, but I must leave
the user use the standard default "NewForm" and "EditForm".

Some may wonder, why not using the Site Directory; it's an approach
being studied at the moment, but the current approach is to use a
custom list.

Any suggestions are highly appreciated

Regards

Re: Maintaining hierarchy by Mike

Mike
Mon Jul 14 05:14:40 CDT 2008

This question has been repeated in its entirity in the .portalserver
newsgroup.

You either have WSS 2.0 or WSS 3.0 (this newsgroup) or SPS 2003 or MOSS
2007 (that newsgroup).

It would be much more useful if you would tell us which product you are
asking this question about rather than posting it to both newsgroups and
causing duplicate effort - starting no doubt with people in both
newsgroups asking which product you are asking about.

In future please post any one question only to one newsgroup and if you
aren't running either WSS 2.0 or 3.0 don't post messages here - because
that is all this newsgroup covers.

Mike Walsh
WSS FAQ http://www.wssfaq.com / http://wss.collutions.com
no private questions please

coosa wrote:
> Dear colleagues,
>
> In a custom list; I would like to implement a directory that may have
> the following options:
> 1.) Categories may contain subcategories and so on.
> 2.) An item may belong to more than one category or sub-category.
>
> For example:
>
> If Microsoft company would be included in the directory and we have
> some categories such as:
> 1. IT
> 1.1 Software
> 1.2 Hardware
> 2. Finance
> 3. Research
> and assuming we would like to add Microsoft web site to the directory
> and that it belongs to (1. IT), (1.1 Software), (1.2 Hardware) and (3.
> Research), figuring out a suitable approach causes me headache!
> The reason is that I'm limited to not using any thing other than
> Sharepoint.
> I implemented a content type of type folder in order for me to
> maintain the hierarchy of categories; should an item belong to a
> single category or sub-category, then another content type in the list
> of type item would work just fine; however, the intersection of
> association as in the Microsoft example doesn't make that approach
> suitable.
>
> If would use a webpart, that would be some how ok, but I must leave
> the user use the standard default "NewForm" and "EditForm".
>
> Some may wonder, why not using the Site Directory; it's an approach
> being studied at the moment, but the current approach is to use a
> custom list.
>
> Any suggestions are highly appreciated
>
> Regards

Re: Maintaining hierarchy by coosa

coosa
Mon Jul 14 11:33:50 CDT 2008

On Jul 14, 1:14=A0pm, Mike Walsh <englantilai...@hotmail.com> wrote:
> This question has been repeated in its entirity in the .portalserver
> newsgroup.
>
> You either have WSS 2.0 or WSS 3.0 (this newsgroup) or SPS 2003 or MOSS
> 2007 (that newsgroup).
>
> It would be much more useful if you would tell us which product you are
> asking this question about rather than posting it to both newsgroups and
> causing duplicate effort - starting no doubt with people in both
> newsgroups asking which product you are asking about.
>
> In future please post any one question only to one newsgroup and if you
> aren't running either WSS 2.0 or 3.0 don't post messages here - because
> that is all this newsgroup covers.
>
> Mike Walsh
> WSS FAQhttp://www.wssfaq.com/http://wss.collutions.com
> no private questions please
>
> coosa wrote:
> > Dear colleagues,
>
> > In a custom list; I would like to implement a directory that may have
> > the following options:
> > 1.) Categories may contain subcategories and so on.
> > 2.) An item may belong to more than one category or sub-category.
>
> > For example:
>
> > If Microsoft company would be included in the directory and we have
> > some categories such as:
> > 1. IT
> > 1.1 Software
> > 1.2 Hardware
> > 2. Finance
> > 3. Research
> > and assuming we would like to add Microsoft web site to the directory
> > and that it belongs to (1. IT), (1.1 Software), (1.2 Hardware) and (3.
> > Research), figuring out a suitable approach causes me headache!
> > The reason is that I'm limited to not using any thing other than
> > Sharepoint.
> > I implemented a content type of type folder in order for me to
> > maintain the hierarchy of categories; should an item belong to a
> > single category or sub-category, then another content type in the list
> > of type item would work just fine; however, the intersection of
> > association as in the Microsoft example doesn't make that approach
> > suitable.
>
> > If would use a webpart, that would be some how ok, but I must leave
> > the user use the standard default "NewForm" and "EditForm".
>
> > Some may wonder, why not using the Site Directory; it's an approach
> > being studied at the moment, but the current approach is to use a
> > custom list.
>
> > Any suggestions are highly appreciated
>
> > Regards

My apologies,

I am running WSS 3.0 (MOSS 2007).

regards

Re: Maintaining hierarchy by callahan

callahan
Mon Jul 14 13:58:21 CDT 2008

Then I think the .portalserver newsgroup would be the right one for you. : )

-callahan
"coosa" <coosa76@gmail.com> wrote in message
news:46ae8488-349a-418e-96e0-4118e8f35bc2@34g2000hsh.googlegroups.com...
On Jul 14, 1:14 pm, Mike Walsh <englantilai...@hotmail.com> wrote:
> This question has been repeated in its entirity in the .portalserver
> newsgroup.
>
> You either have WSS 2.0 or WSS 3.0 (this newsgroup) or SPS 2003 or MOSS
> 2007 (that newsgroup).
>
> It would be much more useful if you would tell us which product you are
> asking this question about rather than posting it to both newsgroups and
> causing duplicate effort - starting no doubt with people in both
> newsgroups asking which product you are asking about.
>
> In future please post any one question only to one newsgroup and if you
> aren't running either WSS 2.0 or 3.0 don't post messages here - because
> that is all this newsgroup covers.
>
> Mike Walsh
> WSS FAQhttp://www.wssfaq.com/http://wss.collutions.com
> no private questions please
>
> coosa wrote:
> > Dear colleagues,
>
> > In a custom list; I would like to implement a directory that may have
> > the following options:
> > 1.) Categories may contain subcategories and so on.
> > 2.) An item may belong to more than one category or sub-category.
>
> > For example:
>
> > If Microsoft company would be included in the directory and we have
> > some categories such as:
> > 1. IT
> > 1.1 Software
> > 1.2 Hardware
> > 2. Finance
> > 3. Research
> > and assuming we would like to add Microsoft web site to the directory
> > and that it belongs to (1. IT), (1.1 Software), (1.2 Hardware) and (3.
> > Research), figuring out a suitable approach causes me headache!
> > The reason is that I'm limited to not using any thing other than
> > Sharepoint.
> > I implemented a content type of type folder in order for me to
> > maintain the hierarchy of categories; should an item belong to a
> > single category or sub-category, then another content type in the list
> > of type item would work just fine; however, the intersection of
> > association as in the Microsoft example doesn't make that approach
> > suitable.
>
> > If would use a webpart, that would be some how ok, but I must leave
> > the user use the standard default "NewForm" and "EditForm".
>
> > Some may wonder, why not using the Site Directory; it's an approach
> > being studied at the moment, but the current approach is to use a
> > custom list.
>
> > Any suggestions are highly appreciated
>
> > Regards

My apologies,

I am running WSS 3.0 (MOSS 2007).

regards