Arkivji tal-Kategorija: SharePoint Fittex

Kif To Speċifika Nies bħala Search Ambitu / Kontenut Sors Bl-użu SharePoint 2013 SERĦAN API

I had reason to work with the SharePoint 2013 Search API via REST for the first time. I wanted to search for people, not documents. The key learning here is that you specify content sources via its GUID (or at least in this case). The following jQuery snippet shows how:

    loadExpertsAsync: funzjoni() {

        jQuery.support.cors = vera;

        $.ajax({
            url: dan.CreateFullApiUrl() +
                "?querytext='portals'&sourceid='b09a7990-05ea-4af9-81ef-edfab16c4e31'" +
                "&selectproperties='LinkedInProfileUrl,GoogleCirclesProfileUrl,BALargeProfilePictureUrls,BAGridPictures,WorkEmail,Skills,AboutMe,Interests,JobTitle,PastProjects,PictureURL,PreferredName,TwitterHandle,LinkedInProfileUrl,PreferredName,GoogleCirclesProfileUrl'" +
                "&rowlimit=99",
            metodu: "GET",
            headers: { "Accept": "application/json; odata=verbose" },
            cache: falza,
            success: funzjoni (result) {

Fil-każ tiegħi, I’m running the API against SharePoint online. To get the GUID, I followed these steps:

  1. Access the SharePoint admin center
  2. Select “search” from the left hand navigation
  3. Select “Manage Result Sources”
  4. Select “Local People Results”
  5. Look at the URL.

My URL looked something like:

https://xyzzy-admin.sharepoint.com/_layouts/15/searchadmin/EditResultSource.aspx?level=tenant&sourceid=b09a7990%2D05ea%2D4af9%2D81ef%2Dedfab16c4e31&view=1

The sourceid parameter is what worked for me.

(I understand that the sourceid may actually be a sort of permanent thing with SP, but I’ll always check anyway 🙂 ).

</aħħar>

undefinedAbbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Wieħed Kawza għal "Il-kreatur ta 'din tort ma speċifikax Raġuni.”

Stajt kont qed tagħmel ħafna xogħol ma 'search SharePoint aħħar u speċifikament l-klassi KeywordQuery, proprjetajiet u l-metodi.

Jekk trid li l-riżultat stabbilit li jirritornaw riżultati fuq u lil hinn mill-suspettati tas-soltu (tara hawn), inti iżżidhiex mal-ġbir SelectedProperties, kif fil-:

myKeywordQuery.SelectProperties.Add("xyzzy");

Many thanks and a tip of the hat to Corey Roth u this enormously helpful blog post (http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2008/02/19/how-to-use-the-moss-enterprise-search-keywordquery-class.aspx)

Fil-każ tiegħi, “xyzzy” isn’t actually a managed property.  When I added it to SelectedProperties anyway, SharePoint threw one of my favorite ever runtime exceptions:

“The creator of this fault did not specify a Reason.”

I especially like the capital “R” in Reason.  This sounds to me like the .NET equivalent of “I have no mouth, and I must scream."

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Handy Referenza: Default Riżultati minn KeywordQuery Fittex

Meta inti jinvokaw il-Teżegwixxi() metodu fuq KeywordQuery, inti tista 'toħloq ResultTable ibbażata fuq ResultType.RelevantResults.  Dan snippet kodiċi juri dak li jfisser I:

ResultsTableCollection ResultTableCollection = myKeywordQuery.Execute();

ResultTable searchResultsTable = resultsTableCollection[ResultType.RelevantResults];

It-tabella li jirriżultaw se jkollhom l-kolonni li ġejjin ta 'informazzjoni: 

WorkId
Rank
Titolu
Awtur
Daqs
Path
Deskrizzjoni
Ikteb
SiteName
CollapsingStatus
HitHighlightedSummary
HitHighlightedProperties
Contentclass
IsDocument
PictureThumbnailURL
ServerRedirectedURL

I derivat din il-lista minn SharePoint 2010 ambjent, intrapriża edizzjoni.  Nisperaw se jkun handy għal xi ħadd fil-futur.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

SharePoint 2010 KeywordQuery u l HiddenConstraints Proprjetà

Stajt kont qed tagħmel daqsxejn ta 'xogħol ma' l- KeywordQuery oġġett fil SharePoint 2010 u jagħmlu użu mill- HiddenConstraints proprjetà.

I ma sabx informazzjoni utli immedjatament fuq il-proprjetà li, hekk ħsibt I d malajr LOGHOME stabbiliti kif stajt ilhom jużawha.

Safejn I peux, din hija restrizzjoni miżjuda mal-mistoqsija sabiex inti tista sort ta 'park hemmhekk u ma tinkwieta dwar dan awtomatiku.  Bħala tali, huwa biss ieħor keyword (jew sett ta 'keywords) u modifikaturi li inti tista tip fil lill-UI meta inti tagħmel tfittxija keyword.  Hawn eżempju:

keywordQuery.HiddenConstraints = "scope:\"Industry\"";

Inti tista 'żżid restrizzjonijiet addizzjonali ma delimetru spazju.

keywordQuery.HiddenConstraints = "scope:\"Industry\" defense";

Dan t'hawn fuq huwa qal bl-Ingliż, "Run mistoqsija keyword infittxu" difiża "u barra minn hekk, jużaw il-"Industrija" ambitu.

Hawn mod ieħor ta 'tħares lejn dan:

image

Stajt ilhom jużawha biex jipprovdu ambitu awtomatiku kuntest dipendenti fuq parti web custom.  When the user clicks on a tab and clicks a search button, the tab dictates a particular search scope.  It’s working well so far.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Raġuni waħda għal "wieħed jew aktar tipi ta 'oqsma ma jiġux installati kif suppost”

I kienet qed tagħmel żgħir tweak bieraħ għal parti web li ma query CAML kontra lista.  I għamlu l-bidla, skjerati dan u ltqajna hit ma żball:

Żball mhux mistennija tkun seħħet fil-Jum Tliet Outlook Weather Forecast WebPart. Jekk jogħġbok ikkuntattja l-amministratur tas-sistema. Wieħed jew aktar tipi ta 'oqsma ma jiġux installati kif suppost. Mur fil-settings lista paġna li jitħassru dawn l-oqsma.

I kienet qed tiffaċċja kwistjoni oħra oddball qabel so I ma immedjatament jgħaqqdu mistoqsija CAML tiegħi mal-iżball li kien SharePoint rappurtar lili.  I għamlet tfittxija ta 'malajr u bing u jinstab dan blog post utli minn Sandeep Nahta  (http://snahta.blogspot.com/2009/01/one-or-more-field-types-are-not.html).

Hawn hu l-mistoqsija ħażina:

query.Query = "<Fejn><U><Neq><FieldRef Isem = "abbr" /><Tip Valur = "Test">SFNY</Valur><FieldRef Isem = "abbr" /><Tip Valur = "Test">SFIS</Valur></Neq></U></Fejn>";

Hawnhekk huwa ffissat:

query.Query = "<Fejn><U><Neq><FieldRef Isem = "abbr" /><Tip Valur = "Test">SFNY</Valur></Neq><Neq><FieldRef Isem = "abbr" /><Tip Valur = "Test">SFIS</Valur></Neq></U></Fejn>";

Allura, l-morali ta 'l-istorja hija: kun żgur CAML tiegħek hija korretta jew tista 'tikseb żball oddball.

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

</aħħar>

Tħabbar l-Intrapriża Fittex User Group Microsoft

Jien eċċitati ħafna li jħabbar li Natalya Voskresenskaya, kollegi tiegħi SharePoint MVP u l-partner (bl ferm inqas għajnuna mill me milli hi jixirqilhom) is launching a new user group devoted to enterprise search based on Microsoft technology. As a practical matter, dan jeħodna għall SP 2010 tfittxija u ħafna diskors dwar FAST, especially in our first session. Natalya and I have written a lot about FAST over the last year on blogs tagħna (Natalya għandha aktar u aħjar minn I Jittieħed!).

Our first meeting is coming up in just a few weeks in New York at Microsoft’s newly renovated offices on 6th near Rock Center. If you’re in New York on 12/9, you have no excuse not to make an appearance. Likewise for you Jersey people. Connecticut people can stay home (biss kidding!).

NY/NJ/CT people should skip this paragraph. We also plan to record the session and run a live web session so if you live outside the tri-state area, you should be able to tune in.

I ser blog dwar dan ftit aktar għaliex dan approċċi jum l-aktar awspiċju iżda jirreġistraw issa. After you register, the long wait begins. During that time, ċara iskeda tiegħek, jiksru l-aħbarijiet lill-familja tiegħek u javża lill-midja għaliex inti ma tridx taqbeż Nate Treloar launch our group to the moon and beyond 🙂

Sir af aktar mis-sit uffiċjali tagħna: http://www.sharepointgroups.org/enterprisesearch/default.aspx.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Governanza u SharePoint Fittex – Huwa Qatt m'hu tard wisq biex Bidu

I kiteb artikolu (http://searchwinit.techtarget.com/tip/0, 289483, sid1_gci1345231_mem1, 00.html #) għal SearchWinIT.com on governance as it relates to SharePoint Search. It’s not in my usual "voice" but that’s editing for you 🙂

Hawnhekk huwa kif jibda:

Għalkemm kważi kull aspett ta 'SharePoint jistgħu jibbenefikaw minn pjan ta' governanza b'saħħitha, MOSS 2007’s enterprise search functionality benefits most of all.

Bħall-partijiet kollha ta 'SharePoint, hemm aħbar tajba u aħbar ħażina dwar il-governanza. Għal ħafna organizzazzjonijiet, l-aħbar ħażina hija li huwa estremament diffiċli li jinkorporaw pjan ta 'governanza fejn jeżisti xejn.

Iżda hawn l-aħbar tajba: Tista 'malajr kkonfigurat u ttejjeb fuq tfittxija intrapriża fi kważi kwalunkwe ħin. U meta inti jimplimentaw pjan ta 'governanza għat-tiftix intrapriża, tista 'tara riżultati immedjati.

Waħda mill-problemi ma SharePoint u governanza hija li l-kumpaniji spiss nikseb irkoppa-fond fil SharePoint bl-ebda pjan governanza u billi allura, there’s no easy path forward to solve it. No so with Search. Read the article to get my thoughts on that subject.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Servizzi fuq Server ma tniżżilx Fittex — Għaliex?

I kien chat illum ma Agnes Molnar (l-unika persuna li naf li jien naf fl-Ungerija) about a strange search configuration problem. Namely, search was missing from the "services on server" wiri (permezz Admin Ċentrali -> Operazzjonijiet -> Servizzi fuq Server).

Kelli ħarsa lejn VM funzjonali fuq magna tiegħi stess u flimkien, we determined that search was not installed on that server. There are probably a few ways to do this, but we did it by confirming that "Office SharePoint Server Search" kienet nieqsa mil-lista ta 'servizzi permezz Start -> Amministrattiv Tools -> Servizzi.

Oddly, l-exe assoċjati. * kien * fuq is-server ("C:\Program Files\Microsoft Office Servers\12.0\Bin\mssearch.exe").

I għamlet tfittxija ta 'malajr u sabet dan blog dħul: http://msmvps.com/blogs/obts/archive/2006/10/19/189466.aspx

C'est katina email dan il-punt ewlieni:

"I solved this problem. Kien żball tiegħi. I choose "Web front end" instead of "Complete" waqt l-installazzjoni."

Dan kien promettenti, but we weren’t sure if the installer had actually picked WFE instead of complete when installing MOSS.

Aħna ċċekkjati għall-ewwel (kmieni) verżjoni tal-PSCDiagnostics * fajl fil- 12 doqqajs log direttorju u fil hemm, sibna li l-installatur kellhom, fil-fatt, configured this server to be a web front end. End of story and it had a happy ending.

(X'imkien matul il-linja, Bob Fox ltqajna involuti, iżda kollha I remember lilu jikkontribwixxu għad-diskussjoni kien kumment dwar Fable 2).

Aġġornament: Blogs Agnes dwar dan is-suġġett hawn: http://dotneteers.net/blogs/aghy/archive/2008/11/06/wfe-vs-complete-installation.aspx

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Tip Quick: Użu “IsDocument:1” biex Trim Riżultati

Aġġornament 11/03/08: Fellow MVP Mike Walsh ġustament li dan huwa WSS 3.0 / MOSS feature. It does not work in WSS 2.0 jew qabel.

Updatte 11/03/08: (It-tieni aġġornament f'ġurnata waħda!): Be sure to read the excellent comment from "nowise" għal aktar info u ieħor link XREF tajba.

Żewġ mistoqsijiet ħarāu f'suċċessjoni rapida din il-ġimgħa fuq il-forums MSDN tistaqsi varjazzjoni ta 'din:

"When I search a keyword, folders minn librerija dokument tiegħi ma 'dak keyword fil-path tagħhom se toħroġ l-ewwel fir-riżultati search tiegħi. Ma rridx biex dan iseħħ. Files with that keyword are more important to me. I don’t want to see folders at all."

This is actually quite easy to do out of the box. Simply add a "IsDocument:1" għall-tfittxija query u tfittxija SharePoint (kemm WSS u MOSS) se tillimita ruħha li turi dokumenti attwali.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Tags:

Has Kumitat Fittex Your Met Dan Xahar?

Hu l-bidu tax-xahar u issa huwa kif tajba ta 'żmien bħal kwalunkwe biex kumitat tfittxija kumpanija tiegħek biex jiltaqgħu flimkien u tanalizza imħatri Best, tfittxijiet suċċess u mhux daqshekk suċċess, eċċ.

Inti ma għandekx kumitat tfittxija? Then form one 🙂

WSS and especially MOSS search benefit from some human oversight. Investing a few hours a month on a consistent monthly basis is not only gost aktar minn barmil ta 'xadini, Kan:

  • Give insight into the information needs of the enterprise. If people are searching left and right for topic "xyzzy," you know that’s an important topic to the enterprise.
  • Identify potential training requirements. If people are searching for topic "xyzzy" but should really be searching for "abcd" sempliċiment kan użu det til jedukaw lin-nies dwar fejn u kif issib l-informazzjoni.
  • Help your organization refine its information architecture.
  • Jidentifikaw muligheder Tittejjeb il-teżawru.
  • Opportunitajiet oħra m'hemmx dubju li se rigal sig.

Min għandu jkun fuq kumitat tfittxija? You would know your people best, iżda jikkunsidraw:

  • Mill-inqas wieħed (u forsi wieħed biss) IT persuna li jifhem (jew jistgħu jitgħallmu) l-modi varji biex tweak tfittxija, inkluż imħatri aħjar, Teżawru, proprjetajiet amministrati, eċċ.
  • Diversi esperti suġġett li tista 'taqra r-rapporti tat-tiftix, jinġerixxu u jikkomunika azzjonijiet negozju sofistikati għal IT sabiex ikun jista 'timbotta l-buttuni, iġbed il-lievi u valvi miftuħa / mill-qrib kemm meħtieġ biex fuq rakkomandazzjonijiet tal-kumitat.
  • Wieħed jew aktar periti informazzjoni li jista 'jivvalidhom, b'xi mod jew ieħor, jekk l-arkitettura ta 'informazzjoni huwa faċli search u jekk huwa xogħol out ukoll għall-intrapriża.
  • A rotating seat on the committee. Bring in one or two people who don’t normally participate in these kinds of efforts. They may bring unusual and valuable insights to the table.

Analiżi Happy!

</aħħar>

Abbona għall-blog tiegħi.

Tags: