I’m on a project where we need to collect metrics around a function named "Share a Story." The idea is very simple — në qoftë se ju jeni duke kërkuar në një artikull interesant në intranet dhe duan ta ndajnë atë me dikë, click a link labeled "Share this story" email-it për buddy tuaj.

Ne kemi luajtur rreth me një formë me porosi për këtë qëllim, por në fund, sens të përbashkët fitoi ditë dhe ne vetëm përdorni njohur <a href = mailto:…> technique. (<a href mailto:…> është pak e habitshme të fuqishme pak i HTML; si një bonus, se lidhja më sjell përsëri në ditët e vjetra tim njeriu UNIX pages; ata ishin ditë!).

Kjo teknikë siguron një ndërfaqe të madhe për përdoruesit përfundimtarë që ata marrin për të përdorur klientin e tyre të njohur MS Outlook (ose cilindo klient email që ata kanë instaluar).

Kjo e bën gjëra të vështirë për ne lloje varfër developer pasi ata klienti * gjithashtu * dëshiron për të drejtuar një raport në të ardhmen që tregon se sa shpesh përdoruesit tregime ndajnë dhe madje edhe tregime të cilat ndahen më shpesh.

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. Dhe, we need to manage that event library of emails. We have a scheduled job on the white board responsible for that cleanup.

Nëse ju keni disa qasje të zgjuar për zgjidhjen e këtij problemi, ju lutem tregoni.

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Kërkuar si dhe premtoi, I’ve uploaded my presentation on how to obtain "great" requirements from end users for SharePoint projects and implementations. It’s here: http://cid-1cc1edb3daa9b8aa.skydrive.live.com/self.aspx/SharePoint/Paul 20Great 20Galvin%%% 20Requirements.zip

I paraqitur këtë në konferencë SharePoint Praktikave më të Mira në shkurt 2009 (www.sharepointbestpractices.com). If you attended the conference, ju do të merrni edhe kjo konferencë në DVD.

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

(Shih këtu për prezantimin tim të tjera në një rast studimi qeverisjes: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!3099.entry

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Ashtu si shumë lloje konsulente SharePoint, I’ve been exposed to a lot of SharePoint functionality. Some times, 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.

Këtë javë, 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. Në këtë rast, 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" është kuptimi SharePoint zhargon, padyshim mjaft, something like "turn me on if you want end users to be able to create sites when they want to."

Kështu, I kthejnë atë në, try it out dhe për mua, it’s not creating sites. It’s creating site koleksione. Pretty big difference. That’s not what I want, aspak.

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 🙂

Unë jam ende duke punuar jashtë si për të siguruar një pak e një procesi më të efektshëm ndërsa qëndrojnë thjesht të dalë nga kutia, but there’s a definite path to follow. Just don’t get distracted by that label.

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Pata njëri prej 20 ose 30 (ose ndoshta 100?) panelists last night at the New York SharePoint Users Group meeting. Instead of the usual presentation format, kjo ishte e gjitha në lidhje me Q&A between the audience and the panel members. Early on, Michael Lotter introduced me to a new idea and I wanted to share.

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. Si rezultat, 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. Në fillim, this wasn’t a problem, but soon, more and more (non-technical) users needed to use the utility. His question was (paraphrasing):

"What are my options? I don’t want to keep letting users log directly onto the server, but they need that functionality."

Michael Lotter suggested that he configure a new virtual machine, 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, but I just have to say that I think it’s a really neat idea.

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

This past week, someone asked a question about creating a SharePoint environment that would handle a pretty high volume of new documents (10,000 +/- në këtë rast). I don’t know much about this, por thanks to this white paper, I feel much better informed.

Për mua, this white paper is pretty much just a book mark at the moment, but I did start reading through it and thought I’d highlight my main take-away. SharePoint can be scaled to handle, at a minimum, this load:

• 50k new documents per day.
• 10 million documents total.

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 percent higher than that and with extreme tuning, possibly a lot higher.

Falënderim, Mike Walsh, once again for his weekly WSS FAQ updates and corrections post. If you’re not subscribed to it, you should seriously think about doing it.

</fund>

Abonohen në blogun tim.

Gjatë javës së kaluar, tim koleg and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" workstation build (në krahasim me laptopë tonë). While doing that, ne u përplas me disa gabime duke ndjekur këto hapa:

• Hapni një dokument MS Word përmes Windows explorer (e cila përdor WebDAV).
• Bëni një ndryshim.
• Ruaje atë.

Ne kemi ardhur për të kuptojnë se disa herë (zakonisht hera e parë) ne shpëtuam dokumentin, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.

Ne nuk e ka kuptuar çështjen rrënjë në këtë pikë, 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, ne tani mori këtë gabim:

Këtë herë, ajo dukej si çdo ndryshim ishte, në të vërtetë, ruajtur, whether we answered Yes or No to the scripts question.

Ne fund kishte një vështrim në versionin aktual të Zyrës dhe kjo rezulton se workstation është running MS Office 2000 me pako të shërbimit 3 e cila tregon deri nën ndihmë -> About as "Office 2002".

Morale të tregimit: Unë gjithmonë do të përdorim zyre 2003 si minimum time zyre version bazë kur duke përdorur WebDAV dhe myshk.

</fund>

Abonohen në blogun tim.

(Për qëllime search engine, kjo është teksti gabimi së):

Linjë: 11807

Shkrumb: 2

Gabim: Object nuk e mbështet këtë pronë apo metodë

Kod; 0

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

A doni që të vazhdojë drejtimin Scripts në këtë faqe?

In one or my very first blog posts, I described the overall process we followed to migrate a customer from SPS 2003 to MOSS. A reader left a comment asking for more detail and here it is.

For that migration project, we had to find a good way to move a lot of SPS 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.

This is the new document library:

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 drive, but you can imagine it pointing to an SPS 2003 document library:

After that drag and drop operation, my target looks like this:

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. Veç kësaj, let’s assume there are hundreds of documents (maybe thousands) 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. Në vend të kësaj, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" view as shown:

Tani, when someone sits down to spend their allocated daily hour or two to tag migrated documents, they can use the "untagged documents" view to focus their effort:

As users tag documents, they drop off this list.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. Nga kutia, 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. Megjithatë, në qoftë se përdoruesi Ngarkimet më të dhe pastaj mbyllet shfletuesin (ose përdor Windows Explorer për të ngarkoni dokumentin), ne nuk mund të detyrojnë përdoruesin për të hyrë në të dhënat meta (përsëri, nga kutia).

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.

</fund>

Abonohen në blogun tim.

Këtë javë, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, I have a greater appreciation for the kinds of problems people report on the MSDN forums and elsewhere.

The final farm configuration:

• SQL/Index/Intranet WFE inside the firewall.
• WFE in the DMZ.
• Some kind of firewall between the DMZ and the internal server.

Before we started the project, we let the client know which ports needed to be open. During the give and take, back and forth over that, we never explicitly said two important things:

1. SSL means you need a certificate.
2. The DMZ server must be part of a domain.

Day one, 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.

Në këtë pikë, Ne kemi zbuluar konfuzionin mbi certifikatë SSL dhe, trishtim, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. Në kohë të thotë, ne arkitektë zgjidhje lëvizur përpara me sende të biznesit.

Një fundjavë shkon nga dhe klienti merr certifikatën.

Djalë ynë infrastruktura tregon dhe zbulon se serveri DMZ nuk është i bashkuar për çdo domain (ose një domain rrethues me besim të kufizuar ose domain intranet). We wasted nearly a 1/2 ditë në të cilat. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….

Another day passes and the various security committees, interested parties and (not so) innocent bystanders all agree that it’s OK to join the DMZ server with the intranet domain (this is a POC, në fund të fundit, not a production solution).

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.

Long histori e shkurtër, 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 the configuration wizard and voila! We were in business.

</fund>

Abonohen në blogun tim.

Edhe pse nuk është fjalë për fjalë e vërtetë, si një çështje praktike, një internet-ballafaqohet web front end në një DMZ duhet të jetë në një sferë (i.e. jo disa server standalone në workgroup vet pak). It doesn’t need to be in the same domain as the internal WFE(s) dhe serverat e tjera (dhe ndoshta nuk duhet të), por ajo duhet të jetë një domain.

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. Mjerisht, ne nuk mundëm të shtoni një fjali që thoshte se diku, për efekt, "the whole bloody point of this configuration is to allow your DMZ WFE server, në domenin, për t'u bashkuar me fermë të brendshëm."

Një stuhi e përsosur e ngjarjeve, ku ne thelb dukej i lënë, kur ne mund të ketë shikuar të drejtë, kurdisi një komplot për të fshehur këtë problem nga ne deri mjaft vonë në procesin e, duke parandaluar mua nga herë e betimit mia "them një lajm i keq në fillim" sundojnë.

Psherëtimë.

Abonohen në blogun tim.

Përdoruesit Forum shpesh si pyetje si kjo:

> Përshëndetje,
>
> Ju lutem më thoni nëse ka ndonjë mundësi për të ndërtuar një listë me porosi
> master dhe detaj lloji (si faturave) pa përdorur InfoPath.
>

SharePoint ofron disa nga karakteristikat kuti që mbështesin llojet e kërkesave të biznesit si që.

Në përgjithësi, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Përdorni listat shtesë për të ruajtur numrat e konsumatorëve, Numrat e produktit, etj.

Përdorni një pyetje web content pjesë (në MOSS vetëm) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) është gjithashtu në dispozicion për anën e raportimit të saj.

Megjithatë, 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:

• Madhësia listat vs lookup lidhur. "smartness" 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 artikuj, that’s going to be a problem. The lookup control does not page through those items. Në vend të kësaj, 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 "pull back" one column of information. You can never pull back more than one column of information from the source list. Për shembull, you cannot select a customer "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. Unë kam shkruar në lidhje me këtë këtu. You can’t implement cascading drop-downs, kushtimisht të mundësojë / çaktivizoni fushat, etj.
• 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. Për shembull, SharePoint ju lejon të krijoni dy lista me porosi, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Pastaj, you can delete the customer from the list. Nga kutia, there is no way to prevent this. To solve this kind of problem, ju do të zakonisht përdorin handlers ngjarje.

Kjo mund të duket e zymtë, 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 na mundëson për të mbushur ato boshllëqe duke përdorur mjete të tilla si:

• Handlers Event. Use them to enforce referential integrity.
• Kolonat Custom: Create custom column types and use them in lieu of the default lookup column. Add paging, buffering dhe karakteristika AJAX për t'i bërë ata të përgjegjshëm.
• QZHB. 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 është një tipar MOSS (jo në dispozicion në WSS) and is challenging to configure.

• Forma ASP.NET web: Krijo një të plotë me tipare formularin AJAX-enabled që përdor modelin e objektit SharePoint dhe / ose shërbimeve web për listat e SharePoint levave, duke i siguruar një ndërfaqe të përdoruesit shumë të përgjegjshëm.

Mundësia e fundit mund të ndjeni sikur ju jeni duke filluar nga zeroja, por e konsiderojnë faktin se platforma SharePoint fillon ju off me karakteristikat e mëposhtme kryesore:

• Modeli i Sigurimit me mirëmbajtjen.
• Sistemi Menu me mirëmbajtjen.
• "Master table" (i.e. Listat me porosi) me sigurinë, ndërtuar në mirëmbajtjen dhe auditimit.
• Kërko.
• Mbrapsht në fund mjetet e integrimit (QZHB).

Nëse ju filloni me një projekt të ri bosh në studio vizuale, ju keni një shumë e infrastrukturës dhe pajisje hidraulike për të ndërtuar para se të merrni në afërsi të SharePoint çfarë ofron.

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, ju lutemi të lënë një koment.

</fund>