I’m on a project where we need to collect metrics around a function named "Share a Story." The idea is very simple — zaren, intranet buruzko artikulu interesgarri bat bada eta bila nahi norbaitekin partekatzen, klik lotura bat etiketadun "Partekatu istorio hau" postari da zure lagunen.

Inguruan jokatu dugu, horretarako Ohiko inprimaki bat, baina azkenean, sen irabazi-eguna, eta erabili besterik ez dugu ezagutzen da <a href = mailto:…> technique. (<href mailto:…> HTML apur harrigarriro bit sendoa da; bonus gisa,, lotura duten ekartzen me back nire zaharrak UNIX man orriak egun; egun horiek izan ziren!).

Teknika hori oso interfaze bat eskaintzen du erabiltzaileek lortu dute ezagutzen MS Outlook bezeroa erabiltzea da noiztik (edo edozein posta-bezeroa instalaturik izan dute).

Gauzak gurekin gogorragoa pobrea developer mota egiten ditu eta bezeroa geroztik * * nahi du, gainera, etorkizuna erakusten du nola maiz, istorioak partekatzeko eta, nahiz eta horrek istorioak konpartitzen gehienetan txosten bat exekutatu.

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

Zuk arazo hau konpontzeko hurbilketa clever batzuk, mesedez egin esango.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Eskatutako eta agindutako, 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% 20Great% 20Requirements.zip

Hau aurkezten dut ren SharePoint Praktika Onenen Konferentzian 2009 (www.sharepointbestpractices.com). If you attended the conference, Halaber, kongresu honetan lortu DVDan.

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

(Ikusi hemen nire aurkezpena beste gobernu kasu an: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!3099.entry

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

SharePoint aholkulari mota asko bezala, I’ve been exposed to a lot of SharePoint functionality. Batzuetan, 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.

Aste honetan, 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. Kasu honetan, 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" SharePoint Lingo esanahia, jakina, nahikoa, something like "turn me on if you want end users to be able to create sites when they want to."

Beraz,, Da piztu dut, proba ezazu eta niretzat, it’s not creating sites. It’s creating site Bildumak. Pretty big difference. That’s not what I want, ez da.

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, Besteak ere engainatu dituela ikasten dut 🙂

Jarraitzen dut lan bat nola gehiago, streamlined prozesua apur bat emateko, berriz, ostatu hutsa koadroan kanpo, but there’s a definite path to follow. Just don’t get distracted by that label.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Bat izan nuen, 20 edo 30 (edo agian 100?) panelists azken gau hartan New York SharePoint erabiltzaileak Taldeak meeting. Instead of the usual presentation format, Q honi buruz izan zen&A between the audience and the panel members. Early on, Michael Lotter sartu me to ideia berri bat eta partekatu nahi izan dut.

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. Baten ondorioz, 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. Lehen begiratuan, hau ez zen arazo bat, baina laster, Gero eta gehiago (ez teknikoa) users needed to use the utility. His question was (parafraseatuz):

"What are my options? I don’t want to keep letting users log directly onto the server, baina funtzionalitate behar dute."

Michael Lotter konfiguratzeko iradoki zuen makina birtual berria, 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, baina besterik ez dut uste dut benetan neat ideia bat da esatea.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Iragan aste honetan, Norbaitek galdera bat SharePoint ingurune dokumentu berrien bolumena nahiko altua kudeatuko litzateke sortzeari buruz (10,000 +/- kasu honetan). I don’t know much about this, baina thanks to this white paper, Askoz hobeto informatuak sentitzen dut.

Niretzat, 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.

Eskerrik asko, 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.

</amaiera>

Nire blog Harpidetu.

Azken astean zehar, nire lankide and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" travail eraikitze (gure ordenagailu eramangarriak aurka). While doing that, ran gutxi akatsak dugu urrats hauek jarraituz:

• MS word dokumentua ireki Windows Explorer bidez (erabiltzen duten WebDAV).
• Egin aldaketa bat.
• Gorde.

Konturatu ginen batzuetan (lehen aldia izan ohi) Dokumentua gorde dugu, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.

Ez dugu ulertu root arazoa puntu honetan, 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, errore hau lortu dugu:

Oraingo honetan, aldaketa guztietan bezala zirudien, Izan ere,, gorde, whether we answered Yes or No to the scripts question.

Izan dugu azkenik Office benetako bertsio begirada bat eta bihurtzen da travail zela MS Office 2000 zerbitzua pack 3 Laguntza erakusten ditu pean> About as "Office 2002".

Istorioaren morala: Erabili egingo dut beti. Office 2003 nire oinarrizko gutxieneko bulegoan bertsioa WebDAV eta MOSS erabiliz.

</amaiera>

Nire blog Harpidetu.

(Bilatzailea helburuetarako, error testuaren):

Line: 11807

Char: 2

Errorea: Objektu ez jabetza edo metodo hau onartzen

Code; 0

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

Scriptak exekutatzen orri honetan jarraitu nahi duzu?

Bat edo nire Oso lehenengo blog-mezu, SPS bezero migratzeko jarraitu genuen prozesu orokorra deskribatu dut 2003 to MOSS. A reader left a comment asking for more detail and here it is.

Migrazio-proiektu, SPS asko mugitzeko modu ona aurkitu behar izan dugu 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.

Dokumentu berri honek liburutegia da:

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:\aldi baterako unitatean, baina SPS bat seinalatuz imajinatu dezakezu 2003 Dokumentu liburutegia:

Arrastatu eta jaregin eragiketa, eta ondoren, nire Helburu itxura:

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. Gainera, Demagun ez dira ehunka dokumentuen (agian milaka) 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. Horren ordez, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" ikusteko gisa agertzen dira:

Orain, norbaitek eseri behera bere esleitu eguneroko ordu bat edo bi pasatzeko migratu dokumentuak etiketatu, they can use the "untagged documents" ikusteko beren ahalegina bideratzen:

Erabiltzaile tag dokumentuak, utzi dute zerrenda honetan.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. Kutxa Out, 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. Hala eta guztiz ere, erabiltzailearen fitxategiak eta, ondoren, nabigatzailea ixten bada (edo Windows Explorer erabiltzen dokumentua igo), ezin dugu behartu erabiltzaileari meta datuak sartu (berriro, koadroan out).

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.

</amaiera>

Nire blog Harpidetu.

Aste honetan, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, Arazo mota estimua handiagoa txostena MSDN foroak eta beste nonbait daukat.

Azken baserriko konfigurazio:

• SQL / Index / Intranet WFE firewall barruan.
• DMZ, WFE.
• Mota batzuk suebaki DMZ eta barne-zerbitzariaren arteko.

Proiektuaren aurretik hasi ginen, we let the client know which ports needed to be open. During the give and take, atzera eta aurrera baino gehiago, esplizituki inoiz ez dugu esan bi gauza garrantzitsu:

1. SSL esan nahi du ziurtagiri bat behar duzu..
2. The DMZ server must be part of a domain.

Egun bat, 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.

Puntu honetan, nahasmena aurkitu dugu ziurtagiria SSL eta gehiagoko, zoritxarrez, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. Batez besteko denbora, dugu konponbidea arkitektoek mugitu aurretik enpresa stuff.

Asteburuan A doa eta bezeroaren ziurtagiria lortzen.

Gure azpiegitura lasaia erakusten du eta deskubritzen DMZ zerbitzaria ez da edozein domeinu sartu (bai konfiantza mugatua edo intranet domeinu domeinu perimetroa). We wasted nearly a 1/2 duten egunean. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….

Beste egun batean pasatzen du, eta segurtasun-batzordeak hainbat, interesatuek eta (beraz, ez) errugabeen bystanders guztiak bat datoz dela OK intranet domeinu zerbitzaria DMZ sartu (hau da poc, azken finean, ez da ekoizpen irtenbide bat).

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" egoera.

Long Narrazio laburren, 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 konfigurazio morroia eta voila! We were in business.

</amaiera>

Nire blog Harpidetu.

Ez da egia, nahiz eta literalki, praktiko gisa materia, Interneteko web-begira aurrean DMZ batean bukaera behar domeinu bat izango da (I.E. ez da gutxi egin lantalde zerbitzari standalone batzuk). It doesn’t need to be in the same domain as the internal WFE(s) eta beste zerbitzariak (eta, seguruenik, behar ez), baina domeinu bat izan behar du.

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. Tamalez, Esaldi bat nonbait esan gehitzeko huts egin dugu, to efektua, "the whole bloody point of this configuration is to allow your DMZ WFE server, domeinu bat, barne baserria batzeko."

Ekitaldi ekaitz perfektua A, non dugu, funtsean, aurpegia geratzen denean begiratu izan dugu agian eskubidea, konspiratu arazo hau ezkutatzeko, gugandik nahiko prozesuan berandu arte, beraz, niri saihesten dei batetik nire "esango albiste txarra goiz" araua.

Sigh.

Nire blog Harpidetu.

Forum users frequently as questions like this:

> Kaixo,
>
> Mesedez, esan dit ez dira aukerak edozein zerrenda pertsonalizatu bat eraiki nahi izanez gero
> master eta xehetasun-mota (fakturak bezalako) without using InfoPath.
>

SharePoint kutxa eginbideak onartzen duten enpresa horrelako eskakizunak mota daudelarik batzuk eskaintzen.

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

Use additional lists to maintain customer numbers, product numbers, etc.

Use a content query web part (in MOSS only) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) is also available for the reporting side of it.

Hala eta guztiz ere, 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:

• Size of related lookup lists 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 elementuak, that’s going to be a problem. The lookup control does not page through those items. Horren ordez, 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. Esate baterako, 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. I’ve written about this here. You can’t implement cascading drop-downs, conditionally enable/disable fields, 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. Adibidez, SharePoint allows you to create two custom lists, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Gero, you can delete the customer from the list. Kutxa Out, there is no way to prevent this. To solve this kind of problem, you would normally use event handlers.

It may seem bleak, 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 enables us to fill those gaps using tools such as:

• Event handlers. Use them to enforce referential integrity.
• Custom columns: Create custom column types and use them in lieu of the default lookup column. Add paging, buffering and AJAX features to make them responsive.
• 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 is a MOSS feature (not available in WSS) and is challenging to configure.

• ASP.NET web form: Create a full-featured AJAX-enabled form that uses the SharePoint object model and/or web services to leverage SharePoint lists while providing a very responsive user interface.

The last option may feel like you’re starting from scratch, but consider the fact that the SharePoint platform starts you off with the following key features:

• Security model with maintenance.
• Menu system with maintenance.
• "Master table" (I.E. Ohiko zerrendak) with security, built-in maintenance and auditing.
• Bilatu.
• Back end integration tools (BDC).

If you start with a new blank project in visual studio, you have a lot of infrastructure and plumbing to build before you get close to what SharePoint offers.

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, Mesedez, utzi iruzkin bat.

</amaiera>