I’m on a project where we need to collect metrics around a function named "Share a Story." The idea is very simple — má tá tú ag lorg ar alt suimiúil ar an inlíon agus ba mhaith liom é a roinnt le duine éigin, click a link labeled "Share this story" sé ríomhphost chuig do chara.

Bhí muid timpeall le foirm saincheaptha chun na críche sin, ach sa deireadh, tuiscint coiteann a bhuaigh an lae agus táimid ag úsáid ach an eolas <a href=mailto:…> technique. (<a mailto href:…> Is le beagán ionadh láidir de HTML; mar bhónas, Tugann an nasc mé ar ais go dtí mo shean UNIX fear leathanaigh laethanta; na daoine a bhí na laethanta!).

Soláthraíonn an teicníc comhéadan iontach do úsáideoirí deiridh ó fhaigheann siad úsáid a bhaint as a n-eolas MS Outlook cliant (nó cibé cliant ríomhphoist tá siad suiteáilte).

Déanann sé rudaí níos deacra ar orainn cineálacha bhforbróir bocht ó chliaint siad freisin * * ba mhaith leis a thuarascáil sa todhchaí a léiríonn cé chomh minic úsáideoirí a roinnt scéalta agus fiú a scéalta atá á roinnt is minic a reáchtáil.

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

Má tá tú roinnt cur chuige cliste a réiteach ar an bhfadhb seo, le do thoil a dhéanamh a insint.

</deireadh>

Liostáil le mo bhlag.

Lean mé ar Twitter ag http://www.twitter.com/pagalvin

Mar a iarradh agus gealladh, 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% 20Galvin%% 20Requirements.zip 20Great

Chuir mé seo ag an gcomhdháil SharePoint Cleachtais is Fearr i Feabhra 2009 (www.sharepointbestpractices.com). If you attended the conference, Feicfidh tú a fháil freisin seo ar an DVD comhdháil.

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

(See here for my other presentation on a governance case study: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!3099.entry

</deireadh>

Liostáil le mo bhlag.

Lean mé ar Twitter ag http://www.twitter.com/pagalvin

Cosúil le cineálacha comhairleoir go leor SharePoint, I’ve been exposed to a lot of SharePoint functionality. Roinnt uaireanta, 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.

An tseachtain seo, 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. Sa chás seo, 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" Tá brí lingo SharePoint, ar ndóigh go leor, something like "turn me on if you want end users to be able to create sites when they want to."

Mar sin,, Cas mé é ar, triail a bhaint amach agus le haghaidh dom, it’s not creating sites. It’s creating site bailiúcháin. Pretty big difference. That’s not what I want, ní ar chor ar bith.

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 🙂

Tá mé fós ag obair amach conas a chur ar fáil le beagán de phróiseas níos sruthlínithe agus ag fanacht amháin amach as an bosca, but there’s a definite path to follow. Just don’t get distracted by that label.

</deireadh>

Liostáil le mo bhlag.

Lean mé ar Twitter ag http://www.twitter.com/pagalvin

Bhí mé ar cheann de 20 nó 30 (nó b'fhéidir 100?) panelists aréir ag an Nua-Eabhrac Grúpa Úsáideoirí SharePoint meeting. Instead of the usual presentation format, Bhí sé seo ar fad faoi Q&A between the audience and the panel members. Early on, Michael Lotter isteach dom smaoineamh nua agus theastaigh uaim a roinnt.

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. Mar thoradh air sin, 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. Ar dtús, Ní raibh sé seo ina fhadhb, ach go luath, níos mó agus níos mó (neamh-theicniúil) 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, ach is gá iad go feidhmiúlacht."

Michael Lotter fios go bhfuil sé chumrú le meaisín fíorúil nua, 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, ach tá mé díreach tar éis a rá go Sílim go bhfuil sé ag smaoineamh i ndáiríre neat.

</deireadh>

Liostáil le mo bhlag.

Lean mé ar Twitter ag http://www.twitter.com/pagalvin

An tseachtain seo caite, d'iarr duine éigin ceist faoi timpeallacht SharePoint a bheadh ​​déileáil le líon ard go leor de na doiciméid nua a chruthú (10,000 +/- sa chás seo). I don’t know much about this, ach thanks to this white paper, Is dóigh liom i bhfad níos eolaí.

Maidir liom féin, 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.

Go raibh maith agat, 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.

</deireadh>

Liostáil le mo bhlag.

I rith na seachtaine seo caite, mo chomhghleacaí and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" stáisiún oibre a thógáil (le hais ár ríomhairí glúine). While doing that, ar siúl againn i roinnt earráidí a leanas ag na céimeanna:

• Oscail cáipéis focal MS via fuinneoga taiscéalaí (a úsáideann WebDAV).
• Dhéanamh ar athrú.
• Sábháil sé.

Tháinig muid a thuiscint go bhfuil roinnt uaireanta (de ghnáth ar an chéad uair) shábháil againn an doiciméad, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.

Ní raibh muid a thuiscint an cheist fréimhe ag an bpointe seo, 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, fuair muid anois an earráid seo:

An uair seo, dhealraigh sé cosúil go raibh gach athrú, i ndáiríre, shábháil, whether we answered Yes or No to the scripts question.

Bhí orainn ar deireadh le breathnú ar an leagan iarbhír na hOifige agus casadh sé amach go raibh an stáisiún oibre rith MS Oifig 2000 le seirbhís pacáiste 3 a léiríonn suas faoi Cabhair -> About as "Office 2002".

An mhorálta an scéal: Beidh mé úsáid i gcónaí Oifig 2003 mar mo leagan oifig bonnlíne íosta nuair a úsáid WebDAV agus CAONAIGH.

</deireadh>

Liostáil le mo bhlag.

(Chun críocha inneall cuardaigh, Tá an téacs seo an earráid a):

Líne: 11807

Ruabhreac: 2

Earráid: Ní Réad tacú leis an maoin nó modh

Cód; 0

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

Ar mhaith leat dul ar aghaidh scripteanna a reáchtáil ar an leathanach seo?

In one or my very first blog posts, Mé cur síos ar an bpróiseas foriomlán lean muid ag dul ar imirce le custaiméir ó SPS 2003 to MOSS. A reader left a comment asking for more detail and here it is.

Ar an ábhar sin tionscadal imirce, bhí againn a fháil ar bhealach maith chun bogadh a lán de na 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. Furthermore, ligean ar glacadh leis go bhfuil na céadta de dhoiciméid (b'fhéidir na mílte) 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. Ina áit sin, 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:

Anois, 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. As an bosca, 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. Mar sin féin, if the user uploads and then closes the browser (or uses windows explorer to upload the document), we can’t force the user to enter meta data (arís, amach as an bhosca).

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.

</deireadh>

Liostáil le mo bhlag.

An tseachtain seo, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, Tá mé tuiscint níos fearr do na cineálacha fadhbanna a thuairisciú daoine ar na fóraim MSDN agus in áiteanna eile.

An chumraíocht feirme deiridh:

• SQL / Innéacs / Inlíon WFE taobh istigh an balla dóiteáin.
• WFE i 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.

Ag an bpointe seo, we discovered the confusion over the SSL certificate and, Faraor, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. Idir an dá linn, we solution architects moved ahead with the business stuff.

A weekend goes by and the client obtains the certificate.

Our infrastructure guy shows up and discovers that the DMZ server is not joined to any domain (either a perimeter domain with limited trust or the intranet domain). 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….

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, tar éis an tsaoil, 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" stádas.

Fada scéal gearr, 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.

</deireadh>

Liostáil le mo bhlag.

Cé nach bhfuil sé fíor literally, mar ábhar praiticiúil, ní mór ceann tosaigh gréasáin idirlín-os i DMZ bheith i bhfearann (i.e. Ní roinnt freastalaí standalone ina grúpa oibre beag féin). It doesn’t need to be in the same domain as the internal WFE(s) agus freastalaithe eile (agus is dócha nár chóir), ach ní mór é a bheith ina fearainn.

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. Faraor, theip orainn a chur le pianbhreith áit éigin a dúirt, a mbeidh an éifeacht, "the whole bloody point of this configuration is to allow your DMZ WFE server, i bhfearann, a bheith ar an bhfeirm inmheánach."

A stoirm foirfe na n-imeachtaí, nuair a d'fhéach muid d'fhág go bunúsach nuair a d'fhéadfadh muid a d'fhéach ceart, conspired a cheilt ar an bhfadhb uainn go dtí go cothrom go déanach sa phróiseas, rud a chosc dom ó mo agairt "insint nuacht olc go luath" riail.

Osna.

Liostáil le mo bhlag.

Fóram úsáideoirí go minic mar ceisteanna mar seo:

> Dia duit,
>
> Do thoil, inis dom má tá aon féidearthachtaí a thógáil liosta saincheaptha le
> máistir agus sonraí cineáil (cosúil le sonraisc) gan úsáid a bhaint as InfoPath.
>

Soláthraíonn SharePoint roinnt amach as na gnéithe bosca a thacaíonn le cineálacha riachtanas gnó mar sin.

Go ginearálta, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Bain úsáid as liostaí breise a choimeád ar bun líon na gcustaiméirí, uimhreacha a táirge, etc.

Bain úsáid as ábhar mar chuid gréasáin cheist (i CAONAIGH amháin) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) Tá fáil freisin ar an taobh tuairisciú air.

Mar sin féin, 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:

• Méid na liostaí chuardaigh bhaineann vs. "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 míreanna, that’s going to be a problem. The lookup control does not page through those items. Ina áit sin, 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. Mar shampla, 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. Tá mé scríofa faoi seo anseo. You can’t implement cascading drop-downs, coinníollach ar chumas / dhíchumasú réimsí, etc.
• 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. Mar shampla, SharePoint féidir leat a chruthú dhá liosta saincheaptha, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Ansin,, you can delete the customer from the list. As an bosca, there is no way to prevent this. To solve this kind of problem, Ba mhaith leat é a úsáid de ghnáth láimhseálaithe imeacht.

Féadfaidh sé cosúil gruama, 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 chuireann ar ár gcumas na bearnaí sin a uirlisí úsáid a bhaint as mar sin do líona:

• Event handlers. Use them to enforce referential integrity.
• Colúin saincheaptha: Create custom column types and use them in lieu of the default lookup column. Add paging, buffering agus gnéithe AJAX a dhéanamh sofhreagrach dóibh.
• 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.

  Is BDC gné CAONAIGH (nach bhfuil ar fáil i SSU) and is challenging to configure.

• Bhfoirm gréasáin ASP.NET: Cruthaigh foirm AJAX-chumasaithe lán-feiceáil go n-úsáideann an tsamhail réad SharePoint agus / nó seirbhísí gréasáin do liostaí SharePoint ghiaráil am céanna ag soláthar comhéadan úsáideora an-sofhreagrach.

Féadfaidh an rogha dheireanach gur mhaith leat go bhfuil tú ag tosú ó scratch, ach smaoineamh ar an bhfíric go dtosaíonn an ardán SharePoint tú amach leis na gnéithe lárnacha seo a leanas:

• Samhail Slándála, le cothabháil.
• Córas Menu le cothabháil.
• "Master table" (i.e. liostaí saincheaptha) le slándáil, tógtha-i cothabháil agus iniúchadh.
• Cuardaigh.
• Ar ais deireadh uirlisí comhtháthú (BDC).

Má tá tú tús le tionscadal nua folamh i stiúideo amhairc, bhfuil tú a lán de bhonneagar agus pluiméireachta a thógáil sula bhfaigheann tú gar do cad a thairgeann 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, fág tagairt le do thoil.

</deireadh>