I’m on a project where we need to collect metrics around a function named "Share a Story." The idea is very simple — Ako ste u potrazi na jedan zanimljiv članak na intranetu i želite ga podijeliti s nekim, Kliknite na link s oznakom "podijelite ovu priču" ga na svoju e-mail prijatelja.

Igrali smo se s prilagođenom obliku za tu namjenu, ali na kraju, razum pobijedio dana, a mi samo koristiti upoznati <href = mailto:…> technique. (<href mailto:…> je nevjerojatno robusno malo HTML; kao bonus, koje vode me vraća na mojim starim UNIX man stranica dana; to su bili dani!).

Ova tehnika omogućuje veliku sučelje za krajnje korisnike jer su dobili na korištenje svoj poznati MS Outlook klijenta (ili bilo e-mail klijent su instalirani).

To čini stvari teže na nas jadne developer vrsta jer klijent * i * želi pokrenuti izvješće u budućnosti koji pokazuje koliko često korisnici dijeliti priče, pa čak i priče koje se dijele najčešće.

We whiteboarded a few potential solutions. My favorite is to carbon copy (CC) a SharePoint list. That way, the end user still gets the outlook client while we get to capture the event because we’ll get a copy of the email ourselves. There are some obvious drawbacks. The main problem is that the user could simply blank out or otherwise mangle the CC address. I, we need to manage that event library of emails. We have a scheduled job on the white board responsible for that cleanup.

Ako imate neki pametan pristup rješavanju ovog problema, molimo Vas da učinite.

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u http://www.twitter.com/pagalvin

Kao što je zatražio i obećao, Ja sam učitao moj prezentaciju o tome kako dobiti "veliki" requirements from end users for SharePoint projects and implementations. It’s here: http://cid-1cc1edb3daa9b8aa.skydrive.live.com/self.aspx/SharePoint/Paul 20Galvin%%% 20Great 20Requirements.zip

Predstavio sam to na SharePoint Best Practices konferenciju u veljači 2009 (www.sharepointbestpractices.com). If you attended the conference, također ćete dobiti to na konferenciji za DVD.

The presentation includes a lot of notes with most slides. It’s not just bullet points.

(Vidi ovdje za moju drugu prezentaciju na studiji slučaja upravljanja: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!3099.entry

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u http://www.twitter.com/pagalvin

Poput mnogih vrsta SharePoint konzultantskih, I’ve been exposed to a lot of SharePoint functionality. Neki puta, I dive pretty deep. Other times I just notice it as I’m flying by to another set of menu options. One of those is "self-service site creation." I haven’t had a need for it until this week.

Ovaj tjedan, I need to solve a business problem which I think is going to become more common as companies loosen up and embrace more direct end user control over SharePoint. U tom slučaju, I’ve designed a site template to support a specific end user community. Folks in this community should be able to create their own sites at will using this template whenever the urge strikes them.

I recalled seeing "self-service site creation" before and I’ve always tucked that away in the back of my head thinking that "self service site creation" je SharePoint žargon značenje, očito dovoljno, something like "turn me on if you want end users to be able to create sites when they want to."

Tako, Ja ga uključite, ga isprobati i za mene, it’s not creating sites. It’s creating site zbirke. Pretty big difference. That’s not what I want, nimalo.

It is possible to let end users create new sub sites via a custom permission level. This is exactly where I would have gone in the first place except that the label "self-service site creation" label deceived me. Via twitter, I learn that it’s deceived others as well 🙂

Ja sam još uvijek rade kako bi pružiti malo više moderniji procesa, boraveći čisto iz kutije, but there’s a definite path to follow. Just don’t get distracted by that label.

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u http://www.twitter.com/pagalvin

Ja sam bio jedan od 20 ili 30 (ili možda 100?) panelista sinoć u New York SharePoint grupa korisnika meeting. Instead of the usual presentation format, to je sve o Q&A between the audience and the panel members. Early on, Michael Lotter me upoznao s novom idejom i ja sam htjela podijeliti.

An audience member described how his company had paid a consultant to write an application for his company. The consultant wrote it as a console application using the SharePoint object model. Kao rezultat toga, this meant that the program had to be run on a server in the farm. This meant that anyone that wanted to use the app would have to log onto the server, do the work and log off. Na početku, to nije bio problem, ali ubrzo, sve više i više (netehnički) users needed to use the utility. His question was (parafrazirajući):

"What are my options? I don’t want to keep letting users log directly onto the server, ali im je potrebno da se funkcionalnost."

Michael Lotter sugerirao da je konfigurirati novi virtualni stroj, join it to the farm as a WFE and let users run the application from there.

This is a pretty stunning idea for me. Generalizing this solution brings to mind the notion of essentially temporary, almost disposable WFE’s. I think it’s a pretty neat concept. This temporary WFE can run a console application that uses the SharePoint object model. You could also use it to run stsadm commands. It doesn’t have to be part of regular local balancing. If it goes down or gets wrecked, you can just spin up a new one. I repeat myself, ali moram reći da mislim da je stvarno uredan ideja.

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u http://www.twitter.com/pagalvin

Ovaj prošli tjedan, netko je pitao pitanje o stvaranju SharePoint okoliš koji bi nositi prilično veliku količinu novih dokumenata (10,000 +/- u ovom slučaju). I don’t know much about this, ali hvala na ovom bijelom papiru, Osjećam se puno bolje informirani.

Za mene je, ovaj bijeli papir je prilično jednostavno rezervirati oznaka u ovom trenutku, but I did start reading through it and thought I’d highlight my main take-away. SharePoint can be scaled to handle, u najmanju ruku, ovaj teret:

• 50k novih dokumenata dnevno.
• 10 milijuna dokumenata ukupno.

I write the 50k/10MM figures because they are easy enough to remember. As long as you know they are minimums, you won’t get into trouble. The maximums are at least 10 posto veći nego is ekstremnim tuning, vjerojatno puno veća.

Hvala, Mike Walsh, još jednom za njegov tjedni WSS FAQ ažuriranja i ispravaka Post. If you’re not subscribed to it, trebali ozbiljno razmisliti o tome radi.

</kraj>

Pretplatite se na moj blog.

Tijekom proteklog tjedna, moj kolega and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" radna graditi (za razliku od naših prijenosnih računala). While doing that, mi ran u nekoliko pogrešaka slijedeći ove korake:

• Otvaraju MS Word dokument putem Windows Explorera (koji koristi WebDAV).
• Napravite promjene.
• Spremite.

Došli smo do zaključka da neki puta (obično prvi put) smo spremili dokument, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.

Nismo razumjeli pitanje root u ovom trenutku, but we figured that we should make sure that the latest MS Office service pack had been installed on that work station. The IT folks went and did that. We went through the test again and we discovered a new problem. When we saved it, Sada smo dobili ovu pogrešku:

Ovaj puta, činilo se kao da je svaka promjena, zapravo, spremiti, whether we answered Yes or No to the scripts question.

Na kraju smo imali pogled na stvarne verzije sustava Office, a ispada da je radna trčanje MS Office 2000 sa servisnim paketom 3 koji se prikazuje u pomoć -> About as "Office 2002".

Pouka priče: Ja uvijek koristite Office 2003 kao moje minimalne osnovni uredski verziju kada koristite WebDAV i Moss.

</kraj>

Pretplatite se na moj blog.

(Za tražilice svrhe, ovo pogreške u tekstu):

Linija: 11807

Char: 2

Pogreška: Objekt ne podržava ovo svojstvo ili metodu

Kod; 0

URL: http://sharepoint01/DocumentReview/_vti_bin/owssvr.dll?location=Documents/1210/testworddocument.doc&dialogview=SaveForm

Želite li nastaviti prikazivati ​​skripte na ovoj stranici?

U jednom ili moja Prvi blogu, Sam opisao cjelokupni proces smo zatim preseliti kupca iz SPS-a 2003 to MOSS. A reader left a comment asking for more detail and here it is.

Iz tog migracijskog projekta, morali smo pronaći dobar način da se presele puno SPS-a 2003 documents over to MOSS. The initial load was easy enough. Create a new target document library in MOSS and use windows explorer to move the documents.

Ovo je nova biblioteka dokumenata:

Open up two windows explorers. Point the first at SPS 2003 and the second at the new document library in MOSS. The following screen shot shows this. Note that the top browser is actually pointing at my c:\temp pogon, ali mogu zamisliti što ukazuje na SPS 2003 biblioteka dokumenata:

Nakon toga povuci i ispusti rad, moja ciljana izgleda ovako:

Now it’s time to deal with the metadata. Assume we have just one column of metadata for these documents named "location." We can see from the above "all documents" view that the location is blank. It’s easy enough to use a data sheet view to enter the location, or even go into each document’s properties one by one to add a location. Let’s assume that there is no practical way to assign the location column a value automatically and that end users must do this by hand. Osim toga, pretpostavimo postoje stotine dokumenata (možda i tisuće) and that it will take many many days to update the metadata. As we all know, no one is going to sit down and work for four of five days straight updating meta data for documents. Umjesto toga, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" vidite kako je prikazano:

Sada, kad netko sjeda za provesti svoj dodijeljeni dnevni sat ili dva označiti doselili dokumente, they can use the "untagged documents" vidite da se usredotočite svoje napore:

Dok korisnici tag dokumenata, oni spadati ovaj popis.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. Out of the box, there’s no way to prevent a user from uploading a document to MOSS and then not enter meta data. We can specify that a particular site column is mandatory and the user won’t be allowed to push the save button. Međutim, ako korisnik slike, a zatim zatvara preglednik (ili koristi Windows Explorer za upload dokumenta), ne možemo prisiliti korisnik unijeti meta podataka (opet, iz kutije).

This approach can be used to help with that situation. We can use a "poorly tagged data" view to easily identify these documents and correct them. Couple this with a KPI and you have good visibility to the data with drill-down to manage these exceptional circumstances.

</kraj>

Pretplatite se na moj blog.

Ovaj tjedan, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, Imam veću zahvalnost za vrste problema ljudi prijaviti na MSDN forumima i drugdje.

Završni Farma konfiguracija:

• SQL / Index / Intranet WFE unutar vatrozida.
• WFE u DMZ.
• Neka vrsta firewall između DMZ i unutarnjeg poslužitelja.

Prije nego što smo započeli projekt, we let the client know which ports needed to be open. During the give and take, natrag i naprijed preko toga, mi nikada nije izričito rekao dvije važne stvari:

1. SSL znači da je potrebno uvjerenje.
2. The DMZ server must be part of a domain.

Prvi dan, we showed up to install MOSS and learned that the domain accounts for database and MOSS hadn’t been created. To move things along, we went ahead and installed everything with a local account on the intranet server.

U ovom trenutku, smo otkrili zabunu preko SSL certifikata i, nažalost, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. U međuvremenu, mi rješenje arhitekata nastavila s poslovnim stvarima.

Vikend prolazi, a klijent dobiva certifikat.

Naša infrastruktura tip pokazuje i otkriva da DMZ server nije pridružio na bilo domeni (bilo perimetra domena s ograničenom povjerenja ili intranet domene). We wasted nearly a 1/2 day on that. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….

Još jedan dan prolazi i razne sigurnosne odbori, zainteresiranim stranama i (nije tako) nevini promatrači svi se slažu da je u redu da se pridruže DMZ poslužitelj s intranet domeni (ovo POC, uostalom, Ne proizvodnja rješenje).

Infrastructure guy comes in to wrap things up. This time we successfully pass through the the modern-day gauntlet affectionately known as the "SharePoint Configuration Wizard." We have a peek in central administration and … Yee haw! … DMZ server is listed in the farm. We look a little closer and realize we broke open the Champaign a mite bit early. WSS services is stuck in a "starting" status.

Da ne duljimo, it turns out that we forgot to change the identity of the service account via central administration from the original local account to the new domain account. We did that, re-ran čarobnjaka i voila! We were in business.

</kraj>

Pretplatite se na moj blog.

Iako to nije doslovce točno, kao praktično, internet okrenuto web prednji kraj u DMZ mora biti u domeni (i.e. ne neki samostalni poslužitelj u svojoj maloj radnoj grupi). It doesn’t need to be in the same domain as the internal WFE(s) i drugim poslužiteljima (a vjerojatno ne treba), ali to mora biti domena.

My colleagues and I spent an inordinate amount of time on a proposal which included SharePoint pre-requisites. This included a comprehensive list of firewall configurations that would enable the DMZ server to join the farm and so forth. Nažalost, nismo uspjeli dodati rečenicu negdje da je rekao, na efekt, "Cijela krvava točka ove konfiguracije je kako bi se omogućilo svoj DMZ WFE server, u domeni, da se pridruže unutarnje farmu."

Savršena oluja događaja, gdje smo u osnovi izgledao je napustio kada bismo gledali pravu, urotili sakriti taj problem s nama do relativno kasno u procesu, tako me sprječava zazivajući moje "reći lošu vijest rano" vladati.

Uzdah.

Pretplatite se na moj blog.

Forum Korisnici često kao pitanja kao što je ovaj:

> Bok,
>
> Molim Vas, ako postoje bilo kakve mogućnosti za izgradnju prilagođeni popis s
> gospodar i detalji putovanja (kao i faktura) bez korištenja InfoPath.
>

SharePoint daje neke out of the box značajke koje podržavaju vrste poslovne zahtjeve kao što je to.

Općenito, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Koristite dodatne popise za održavanje kupaca brojeve, Brojevi proizvoda, itd..

Pomoću web-dijela upita sadržaja (samo u MAHOVINA) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) je također dostupna za izvještajno strani je.

Međutim, there are some important limitations that will make it difficult to use pure out-of-the-box features for anything that is even moderately complex. These include:

• Veličina povezanih pretraživanja popisima vs. "Dotjeranost" of the lookup column type. A lookup column type presents itself on the UI differently depending on whether you’ve enabled multi-select or not. In either case, the out-of-the-box control shows all available items from the source list. If the source list has 1,000 predmeti, that’s going to be a problem. The lookup control does not page through those items. Umjesto toga, it pulls all of them into the control. That makes for a very awkward user interface both in terms of data entry and performance.
• Lookups "povući" one column of information. You can never pull back more than one column of information from the source list. Na primjer, ne možete odabrati kupca "12345" and display the number as well as the customer’s name and address at the same time. The lookup only shows the customer number and nothing else. This makes for an awkward and difficult user interface.
• No intra-form communication. Ja sam pisala o tome ovdje. You can’t implement cascading drop-downs, uvjetno uključivanje / isključivanje polja, itd..
• No cascading deletes or built-in referential integrity. SharePoint treats custom lists as independent entities and does not allow you to link them to each other in a traditional ERD sense. Na primjer, SharePoint omogućuje stvaranje dvije prilagođene popise, "Kupac" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Tada, you can delete the customer from the list. Out of the box, there is no way to prevent this. To solve this kind of problem, bi se normalno koristiti događaja vodiče.

On svibanj činiti se pust, but I would still use SharePoint as a starting point for building this kind of functionality. Though there are gaps between what you need in a solution, SharePoint omogućuje nam da ispune one praznine pomoću alata kao što su:

• Događaj rukuju. Use them to enforce referential integrity.
• Prilagođeni stupci: Create custom column types and use them in lieu of the default lookup column. Add paging, poliranje i AJAX značajke kako bi im odgovara.
• BDC. This MOSS-only feature enables us to query other SharePoint lists with a superior user interface to the usual lookup column. BDC can also reach out to a back end server application. Use BDC to avoid replication. Rather than replicating customer information from a back end ERP system, use BDC instead. BDC features provide a nice user interface to pull that information directly from the ERP system where it belongs and avoids the hassle of maintaining a replication solution.

  BDC je MOSS značajka (nisu dostupne u WSS) and is challenging to configure.

• ASP.NET web obrazac: Stvaranje potpuno opremljenog AJAX-enabled obrazac koji koristi model SharePoint objekta i / ili web-usluge u bolje upotrijebiti SharePoint popisima a pruža vrlo osjetljiv korisničko sučelje.

Zadnja opcija svibanj osjećati kao da ste počevši od nule, , ali u obzir činjenicu da SharePoint platforma vas započinje sa sljedećim ključnim značajkama:

• Sigurnosni model s održavanjem.
• Sustav izbornika s održavanjem.
• "Master tablica" (i.e. prilagođeni popisi) sa sigurnošću, izgrađen-in održavanje i reviziju.
• Traži.
• Natrag završiti integraciju alata (BDC).

Ako počnete s novim prazan projekt u Visual Studio, imate puno infrastrukture i vodovod za izgradnju prije nego što dođete blizu onome što nudi SharePoint.

I do believe that Microsoft intends to extend SharePoint in this direction of application development. It seems like a natural extension to the existing SharePoint base. Microsoft’s CRM application provides a great deal of extensibility of the types needed to support header/detail application development. Although those features are in CRM, the technology is obviously available to the SharePoint development team and I expect that it will make its way into the SharePoint product by end of 2008. If anyone has an knowledge or insight into this, molimo vas da ostavite komentar.

</kraj>