Windows Server

mark_vogt · Guest

Greetings all,

I'm looking for a way to make the out-of-box "People" search REALLY do
what all my clients think it does:
1. search ONLY the profile information in each employee's MySite (e.g.
Contact Info from AD, About Me text box, answer-to hierarchy.
2. return ONLY people as results - NOT the documents they've authored,
approved, or vaguely heard of...

I've spent 2 days researching what everyone else is doing, and thus far

it seems no one has really "fixed" the way the native People search
works. Instead there are either lots of UNanswered postings, or web
parts to do separate queries... but I'd PREFER to actually FIX this
potentially-powerful feature of Sharepoint.

Here's what I think I know so far:
=============================
1. There is a Search Scope called "People"; THIS is what appears in the

"Search Scope Pulldown Menu" in the upper right hand corner of the main

portal page.

2. The Search Scope "People" points to a Source Group called - you
guessed it - "People" as well; it's understandable that there is
confusion amongst new Sharepoint users...

3. The Source Group is a way of aggregating a number of Content Sources

together for easy administrative manipulation. In THIS case, the Source

Group "People" references only a SINGLE Content Source, name - again
you guessed it - "People" (grrrrrr).

4. The Content Source "People" is a default (out-of-box) content source

whose address is defined as "sps://<sharepoint server
address>/site$$$people"

So what Sharepoint users all over the planet have is what appears to be

a natural, intuitive tool for finding people, but one which more often
than not provides NON-intuitive (read "aggravating") results...And it
all appears to hinge on Point #4, and just what is MEANT by the address

Microsoft provided.

Now for the QUESTIONS I need help from everyone answering:
====================================================
Comment 1: I get that "sps" is a custom protocol, and the Sharepoint
team has written a custom protocol handler for addresses desribed via
this protocol.

Question 1: WHAT is meant by the "site$$$people" portion of the
address?

Question 2: WHAT does "site$$$people" REALLY point at? IS this the
location of all the MySite PUBLIC PROFILE information (which is what
everyone really THINKS is supposed to be happening)?

Question 3: WHAT OTHER "sites" are available via this terminology?

Question 4: HOW can a person run a report/query to get ALL of the OTHER

sites available using this terminology?

Question 5: HOW can a person REDEFINE the address of the People Content

Source, so that - via a more accurate address (and maybe some
includes/excludes), the REAL "People" content is actually being
indexed, so that everything ELSE can be LEFT alone (the People source
group, the People search scope), and the end result is portal users
getting what they actually EXPECT from doing a "People" search?

Question 6: WHAT documentation sources can ANYONE provide me with, so I

can research, fix and report my results back to this group?

Here's hoping a lot of people jump into this thread, as I suspect there

are a LOT of people who would benefit from this improvement...

Cheers,
-Mark Vogt

HELP - trying to REALLY fix Sharepoint "People" search - nee

	Windows Server Forum Index -> Portal Server Development	All times are GMT
Page 1 of 1