jamii Archives: SharePoint Tafuta

Jinsi ya TAJA Watu kama Tafuta Wigo / Content Kupunguza kutumia SharePoint 2013 Mapumziko 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: kazi() {

        jQuery.support.cors = kweli;

        $.ajax({
            url: hii.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",
            njia: "GET",
            headers: { "Accept": "application/json; odata=verbose" },
            cache: uongo,
            success: kazi (kusababisha) {

Katika kesi yangu, 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, lakini mimi daima utasikia kuangalia anyway 🙂 ).

</mwisho>

undefinedKujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Njia moja kwa ajili ya "Muumba wa kosa hili si bayana Sababu.”

Nimekuwa kufanya mengi ya kazi na tafuta SharePoint siku za hivi karibuni na hasa darasa KeywordQuery, mali na mbinu.

Kama unataka matokeo kuweka kurudi matokeo juu na zaidi ya watuhumiwa wa kawaida (angalia hapa), wewe kuongeza kwa ukusanyaji SelectedProperties, kama katika:

myKeywordQuery.SelectProperties.Add("xyzzy");

Shukrani nyingi na ncha ya kofia Corey Roth na hii inasaidia sana blog post (http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2008/02/19/how-to-use-the-moss-enterprise-search-keywordquery-class.aspx)

Katika kesi yangu, "Xyzzy" ni kweli si mali kusimamiwa.  Wakati mimi aliongeza kwa SelectedProperties anyway, SharePoint kurusha moja ya favorite isipokuwa yangu milele Runtime:

"Muumba wa kosa hili haikubainisha Sababu."

Mimi hasa kama mji mkuu wa "R" katika Sababu.  Hii sauti na mimi kama sawa NET. Ya "Sina kinywa, na mimi lazima kupiga kelele."

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Handy Reference: Default Matokeo ya KeywordQuery Tafuta

Wakati wewe waomba Fanyeni() njia juu ya KeywordQuery, unaweza kuunda ResultTable msingi ResultType.RelevantResults.  Hii snippet kanuni unaeleza nini namaanisha:

ResultTableCollection resultsTableCollection = myKeywordQuery.Execute();

ResultTable searchResultsTable = resultsTableCollection[ResultType.RelevantResults];

meza itakuwa na kusababisha nguzo zifuatazo wa habari: 

WorkId
Cheo
Title
Mwandishi
Ukubwa
Njia
Description
Kuandika
SiteName
CollapsingStatus
HitHighlightedSummary
HitHighlightedProperties
Contentclass
IsDocument
PictureThumbnailURL
ServerRedirectedURL

Mimi inayotokana orodha hii kutoka SharePoint 2010 mazingira, biashara toleo.  Nadhani itakuwa Handy kwa mtu katika siku zijazo.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

SharePoint 2010 KeywordQuery na mali HiddenConstraints

Nimekuwa kufanya kidogo ya kazi na KeywordQuery kitu katika SharePoint 2010 na maamuzi ya matumizi ya HiddenConstraints mali.

Sikuweza kupata habari yoyote mara moja msaada juu ya mali ambayo, hivyo nimeona d haraka nukta chini jinsi nimekuwa kutumia.

Mbali kama naweza kuwaambia, hii ni kikwazo moja kwa moja aliongeza kwa swala ili uweze kutatua wa Hifadhi yake huko na si wasiwasi kuhusu hilo.  Kama vile, ni mwingine tu Keyword (au seti ya maneno) na modifiers kwamba unaweza aina katika UI wakati wa kufanya search keyword.  Hapa ni mfano:

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

Unaweza kuongeza vikwazo ziada na delimiter nafasi.

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

hapo juu ni kusema katika Kiingereza, "Kukimbia swala Keyword kuangalia kwa" ulinzi "na zaidi ya, kutumia "Viwanda" wigo.

Hapa ni njia nyingine ya kuangalia ni:

image

Nimekuwa kutumia kwa kutoa muktadha-tegemezi juu ya sehemu moja kwa moja wigo desturi mtandao.  Wakati Clicks mtumiaji kwenye tab na Clicks kifungo tafuta, tab inaonyesha hasa search upeo.  Ni kazi vizuri hadi sasa.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Sababu moja kwa ajili ya "aina shamba moja au zaidi si imewekwa vizuri”

Mimi nilikuwa kufanya ndogo tweak jana kwa sehemu mtandao kwamba hana hoja CAML dhidi ya orodha.  Mimi alifanya mabadiliko, uliotumika na got hit na makosa:

kosa zisizotarajiwa imetokea katika Tatu Siku Outlook Weather Forecast WebPart. Tafadhali wasiliana na msimamizi wa mfumo. Aina shamba moja au zaidi si imewekwa vizuri. Kwenda kwenye ukurasa orodha mazingira ya kufuta mashamba hayo.

I alikuwa akikabiliwa na suala jingine oddball mapema hivyo mimi si mara moja kuungana hoja yangu CAML na makosa kwamba SharePoint alikuwa taarifa kwangu.  Mimi haraka kimenikamata utafutaji na na wameona hiki kinasaidia blog post na Sandeep Nahta  (http://snahta.blogspot.com/2009/01/one-or-more-field-types-are-not.html).

Hapa ni swala mbaya:

query.Query = "<Ambapo><Na><Neq><FieldRef Jina = 'Abbr' /><Aina ya thamani = 'Nakala'>SFNY</Thamani><FieldRef Jina = 'Abbr' /><Aina ya thamani = 'Nakala'>SFIS</Thamani></Neq></Na></Ambapo>";

Hapa ni fasta:

query.Query = "<Ambapo><Na><Neq><FieldRef Jina = 'Abbr' /><Aina ya thamani = 'Nakala'>SFNY</Thamani></Neq><Neq><FieldRef Jina = 'Abbr' /><Aina ya thamani = 'Nakala'>SFIS</Thamani></Neq></Na></Ambapo>";

Hivyo, maadili ya hadithi ni: kuhakikisha CAML yako ni sahihi au unaweza kupata kosa oddball.

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

</mwisho>

Akitangaza Microsoft Enterprise Tafuta mtumiaji Group

Mimi nina msisimko sana kutangaza kwamba Natalya Voskresenskaya, mwenzangu SharePoint MVP na mpenzi (kwa msaada mbali kidogo kutoka kwangu kuliko yeye alistahili) is launching a new user group devoted to enterprise search based on Microsoft technology. As a practical matter, hii majipu chini SP 2010 utafutaji na mengi ya majadiliano juu FAST, especially in our first session. Natalya and I have written a lot about FAST over the last year on yetu blogs (Natalya ina zaidi na bora zaidi kuliko mimi mambo!).

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 (just 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.

Mimi itabidi blog juu ya hii zaidi baadhi ya watu kama njia hii wengi bora siku lakini kujiandikisha sasa. After you register, the long wait begins. During that time, wazi ratiba yako ya, kuvunja habari kwa familia yako na tahadhari ya vyombo vya habari kwa sababu wewe si unataka miss Nate Treloar launch our group to the moon and beyond 🙂

Kujua zaidi kutoka tovuti yetu rasmi: http://www.sharepointgroups.org/enterprisesearch/default.aspx.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Utawala na SharePoint Tafuta – Ni Kamwe Too Late ya Kuanza

Mimi aliandika makala (http://searchwinit.techtarget.com/tip/0, 289,483, sid1_gci1345231_mem1, 00.html #) kwa SearchWinIT.com on governance as it relates to SharePoint Search. It’s not in my usual "voice" but that’s editing for you 🙂

Hapa ni jinsi ya kuanza:

Ingawa karibu kila nyanja ya SharePoint wanaweza kunufaika na mpango wa nguvu ya utawala, MOSS 2007’s enterprise search functionality benefits most of all.

Kama kila sehemu ya SharePoint, kuna habari njema na habari mbaya kuhusu utawala. Kwa mashirika mengi, habari mbaya ni kwamba ni vigumu sana kuingiza mpango wa utawala ambapo hakuna lolote.

Lakini hapa ni habari njema: Unaweza haraka configure na kuboresha juu ya kutafuta biashara ya saa karibu wakati wowote. Na wakati wewe kutekeleza mpango wa utawala kwa ajili ya kutafuta biashara, unaweza kuona matokeo ya haraka.

Moja ya matatizo na SharePoint na utawala ni kwamba makampuni mara nyingi kupata goti kina katika SharePoint na hakuna mpango wa utawala na kwa wakati huo, there’s no easy path forward to solve it. No so with Search. Read the article to get my thoughts on that subject.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: ,

Huduma kwenye Server Je Si Orodhesha Tafuta — Kwa nini?

Nilikuwa chatting leo na Agnes Molnar (mtu tu najua kwamba mimi kujua katika Hungary) about a strange search configuration problem. Namely, search was missing from the "services on server" kuonyesha (kupitia Kati Admin -> Shughuli -> Huduma juu ya Server).

Mimi nilikuwa na kuangalia VM kazi kwenye mashine yangu mwenyewe na kwa pamoja, 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" iliyopungua orodha ya huduma kupitia Start -> Kiutawala Tools -> Huduma.

Oddly, kuhusishwa. exe * mara * kwenye server ("C:\Program Files\Microsoft Office Servers\12.0\Bin\mssearch.exe").

Mimi kutafuta haraka na kupatikana hii kuingia blog: http://msmvps.com/blogs/obts/archive/2006/10/19/189466.aspx

Hiyo ni mnyororo barua pepe na hatua hii muhimu:

"I solved this problem. Ilikuwa ni makosa yangu. I choose "Web front end" instead of "Complete" wakati wa kufunga."

Hii ilikuwa na kuahidi, but we weren’t sure if the installer had actually picked WFE instead of complete when installing MOSS.

Sisi checked kwa kwanza (mwanzo) toleo la faili PSCDiagnostics * katika 12 mzinga logi directory na huko, tulikuta kwamba kisakinishi alikuwa, kwa kweli, configured this server to be a web front end. End of story and it had a happy ending.

(Mahali fulani kwenye mstari, Bob Fox got kushiriki, lakini wote mimi kukumbuka yake kuchangia mjadala maoni kuhusu Hadithi zilizotungwa 2).

Mwisho: Agnes blogs kuhusu somo hili hapa: http://dotneteers.net/blogs/aghy/archive/2008/11/06/wfe-vs-complete-installation.aspx

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati:

Haraka Tip: Kutumia “IsDocument:1” kwa Chambua Matokeo ya Utafutaji

Mwisho 11/03/08: Wenzake MVP Mike Walsh usahihi anasema kuwa hii ni WSS 3.0 / MOSS feature. It does not work in WSS 2.0 au mapema.

Updatte 11/03/08: (Update ya pili katika siku moja!): Be sure to read the excellent comment from "nowise" kwa maelezo zaidi na mwingine mzuri xref kiungo.

Maswali mawili walifika katika mfululizo wa haraka wiki hii kwenye vikao MSDN kuuliza tofauti ya hii:

"When I search a keyword, folders kutoka hati maktaba yangu na kwamba Keyword katika njia yao watatoka nje ya kwanza katika matokeo yangu ya utafutaji. Mimi sitaki kuwa kutokea. 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" swala tafuta na SharePoint tafuta (wote WSS na MOSS) itakuwa kuzuia yenyewe kwa kuonyesha nyaraka halisi.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati:

Ina Tafuta yako Kamati Met Mwezi huu?

Ni mwanzo wa mwezi na sasa ni wakati mwema kama yoyote kwa ajili ya utafutaji wa kamati ya kampuni yako ya kupata pamoja na kuchambua bets Best, mafanikio na si hivyo mafanikio utafutaji, nk.

Huna kamati ya utafutaji? 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 furaha zaidi kuliko pipa ya nyani, inaweza:

  • 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" basi unaweza kutumia kwamba kuelimisha folks juu ya wapi na jinsi ya kupata taarifa.
  • Help your organization refine its information architecture.
  • Kutambua fursa ya kuimarisha Thesaurus.
  • Fursa nyingine hakuna shaka sasa wenyewe.

Ambao wanapaswa kuwa juu ya utafutaji wa kamati? You would know your people best, lakini fikiria:

  • Angalau moja (na labda moja tu ya) IT mtu ambaye anaelewa (au wanaweza kujifunza) njia mbalimbali tweak tafuta, ikiwa ni pamoja na bets bora, Thesaurus, imeweza mali, nk.
  • Kadhaa somo jambo wataalam kwamba unaweza kusoma ripoti tafuta, ingest yake na kuwasiliana vitendo biashara-savvy kwa IT ili IT wanaweza kushinikiza vifungo, kuvuta levers na valves wazi / karibu kama muhimu juu ya mapendekezo ya kamati.
  • Moja au zaidi habari wasanifu ambao wanaweza kuhalalisha, njia moja au nyingine, kama usanifu habari ni tafuta kirafiki na kama ni kazi nje vizuri kwa ajili ya biashara.
  • 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.

Furaha wakichanganua!

</mwisho>

Kujiunga na blog yangu.

Tags technorati: