SharePoint Optimus Actiones conferentia, “Optimus Actiones,” et elephantos locus

I was lucky to attend and present at last week’s SharePoint Best Practices conference. I’m still new to the whole speaking "thing" et, ingenue, I was a bit nervous for the first half while I sweated out waiting to speak myself. That sort of nervous feeling made it a little hard for me to pay attention to the presenters (Non ego neglexi eos,). Pro, Ego aliquantulus magis focused in attendees.

Conferences always set my mind racing and there was a lot take in at this one. This conference was excellent. I think it was unusual in several ways. It wasn’t a heavy developer conference. There were certainly dev parts to it, sed certe puto 60% Dev quaestiones focused in non-, maybe as high as 80%. I think that speaks to the evolving nature of the SharePoint market. Companies are implementing SharePoint in a variety of ways and they are looking for guidance on how to do it right. And not just guidance on how to create features/solutions (quae iam, optime constitutum fuerit).

I believe the conference was tremendously valuable to most everyone that attended and I know that the organizers plan to do the conference again early next year.

Dixisset, I believe there was a missed opportunity which I hope the next conference addresses. I say it’s a missed opportunity, but that’s not a bad thing. Discovering a community need is in and of itself a good thing. The conference discussed a number of best practices in a variety of areas such as governance, institutio, conventu requisita, quaerere, progressionem, architectura indicium, etc. I think that the missed opportunity has to do with the "green field" positionibus subiecta multi de optimis institutis.

Quando loquuntur de viridi prato, we mean that SharePoint hasn’t gone into production and we’re starting with a clean slate. This is ideal because you can start straight away using best practices for defining and managing governance, architectura indicium, etc. Autem … quod iam accidit adipiscing elit multis milibus (or 10’s of thousands) et non ambulaverunt in principio optimum exercitia? I’ve seen companies with … EM … admodum imparem information architecture baked into their environment. I don’t think that this conference provided much guidance for organizations with that kind of problem (et non solum hoc I, sed regiminis, quaerere, multis aliis locis). Utique, scientes quoniam magna pars problematis solutionem pretii ipsum dolor.

I think that the online SharePoint community hasn’t done much to address this either. I know I have not. It’s a very hard problem to solve at many levels. Technically it’s hard. Budget-wise it’s hard. Culturally, it’s hard. Autem, it’s probably a bigger real world problem than most. Since the conference ended, I’ve been thinking about these kinds of problems and how one would solve them. There has to be a better answer than, "uninstall and reinstall" caput et faciem eget civitatis.

I think that this a great opportunity for the blogging community and experienced thought leaders to lay out some guidance on how to repair their environments. I think there’s a small but non-zero risk that SharePoint could end up with a bad and enduring reputation as a result of poorly architected implementations that fail due to poor governance, IA, etc.

</finem>

Scribet ad mea blog.

Technorati Tags:

Blogger novum in scandalum

Collegam meum EMC, Ericus Swenson, iam persuaserat ut jump in proelium, stand up and be counted 🙂

Qui de blogs de varietate SharePoint notans ad locos http://erikswenson.blogspot.com/. Some of his recent posts include interesting stuff about Photoshop, Microsoft Muneris Ago enim parva res, Regimen SharePoint, creating custom WCM styles and so forth. He does not confine himself to branding. It’s quite an interesting mix which is a little bit different from a lot of the SharePoint blogs with which I’m familiar.

RSS nutritor eius est: http://feeds.feedburner.com/SharepointBrandingDesign

Check it out and give him a little encouragement. We all need that from time to time, praesertim cum primo vere demerguntur in hoc mundo blogging.

</finem>

Scribet ad mea blog.

Technorati Tags:

Optimus Actiones conferentia: “Magnus adepto Requisita” PowerPoint Presentation

Ive uploaded PowerPoint est enim unus de meo sessionibus, "Get Great Business Requirements," hic jus (http://cid-1cc1edb3daa9b8aa.skydrive.live.com/self.aspx/Public/Paul 20Galvin%%% 20Great 20Requirements.pptx).

Aside ex serie egregie punctis, potenter fecit, the deck includes extensive notes which supplement and enhance the afore-mentioned brilliant talking points.

Illi vestrum ut desiderari Optimus Actiones colloquio, I was lucky enough to present and discuss a process that works very well when trying to discover accurate end user business requirements for SharePoint projects. The PowerPoint plus notes describe this in pretty good detail. It supplements one of my earliest blog postings here: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!146.entry

</finem>

Scribet ad mea blog.

Technorati Tags: ,

Latin SharePoint Dashboards Seminar

Online amici mei, Mark et super Miller Finem User SharePoint (www.endusersharepoint.com) currat libero iaculis una hora Seminario, sicut semper facit, at the SharePoint End User community. It takes place at 1pm EDT. Details are here: http://www.endusersharepoint.com/?p=785

Ego sedebat in in online unum de Seminario et ultimum mensis factum est et si tu incolumis interested in aliquid practica Info on dashboards in SharePoint, Certe tanti est 1 hora obsideri.

</finem>

Scribet ad mea blog.

Technorati Tags: ,

User SharePoint Group nocte Webcast

Nocte, 08/20/08, SharePoint Connecticuttensis in user coetus conventus a molestie lacus est webcast pro contione mensis huius physicae.

Nocte scriptor locus: "Microsoft Office SharePoint Server 2007 – Extranei instruere methodologies"

Microsoft’s own Chris Lavista will lead the discussion. I’ve worked with Chris before and he really knows his stuff. If you have any interest in this subject, reprehendo eam. Here are the details:

User SharePoint Group Webcast: https://www.clicktoattend.com/invitation.aspx?code=130299

Topic: Microsoft Muneris SharePoint Server 2007 – Extranei instruere methodologies
Dicentis:
Chris Lavista Microsoft

Date: Veneránda 20th Tempus suscipiat: 6:15 PM Tempus: 6:30 PM -8:00PM


Descriptio:
Permittit enim plures optiones SharePoint instruere. Fiet sermo, quemadmodum tuto posita extranei in suggestu SharePoint posset explicuit. Discutere et mores optimos quibus missiones integrationem vitae frontem, Isaiah Server 2006 et IAG 2007. Optionally, signum in usum casibus loqui unius sustinetur.
De Chris:
Chris Lavista is a Technical Architect at recently opened Microsoft Technology Center in New York. His focus is on SharePoint, Collaborationem, adunauit Communicationibus. Quam operatus est in oeconomus officia industria, (Fugent, Citigroup) prius jungens pro Microsoft 8 annis. He started at Microsoft in 2000 sicut pars consulens officia quadrigis in usu prius jungens MTC diluculo 2006.

Registration & More Info: https://www.clicktoattend.com/invitation.aspx?code=130299

</finem>

Scribet ad mea blog.

Technorati Tags:

Lorem ipsum Met tua mense isto?

Suus 'bonus ut a principio mensis et nunc est tempus, ut aliqua quaerere ipsum comitatu tuo ut simul et resolvere Optimus sponsionibus, non ita bene et feliciter perscrutatur, etc.

Non est consilium quaerere? Deinde formare unum 🙂

WSS and especially MOSS search benefit from some human oversight. Investing a few hours a month on a consistent monthly basis is not only magis fun quam dolium simiarum, Nequit:

  • 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" tunc vos can utor ut erudiret in ubi, et quomodo invenient folks indicium.
  • Help your organization refine its information architecture.
  • Eandem occasionem augendae Thesaurus.
  • Alii occasionibus non dubium adsisterent.

Consilium in quaero quis debet catholicus? You would know your people best, sed considerandum:

  • Saltem unus (et maybe unum tantum) Delirat qui intelligit (aut potest cognoscere) varias vias ad tweak quaerere, possidet optimum sponsionibus, Thesaurus, administratur proprietates, etc.
  • Quod materia peritis, plura legere investigationis tradit, glutiam salivam et communicant negotium sagaces-actiones ad illam, ut possit ventilabit buttons, trahendum vectibus et aperta / proxima valvulae sicut oportet in commissionibus commendatione.
  • Qui architectorum vel magis notitia potest convalidandum, uno modo vel alio, sive notitia architectura est quaerere utrum operetur ex bene coeptis atque amica.
  • 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.

Beatus analyzing!

</finem>

Scribet ad mea blog.

Technorati Tags:

Vivos et Securus: Adepto de SPFolder SPItemList

Vestibulum et metus cursus in neque custodiam quid volo facere videtur, Ego figuratur ego ita scriberet.

Ego fuerit faciens multus of vicis susceptor debugging week vel duos in novissimo. The ER is defined against a document library. The individual items in the document library are tightly related to their parent folders. Ita, I am always getting the folder of the item for various manipulations. While debugging, EGO necessarius ad update metadata a folder pro certo scio item cujus ID.

Hic 'a console parum application (currere in server cogitavit ruris) quod duae allegationes: Item ID: et de pretio agri dare, "Approval Status". It hard codes a lot of stuff and has no error checking.

Codex suspicit duram site coded, gets a hard coded document library and then finds the indicated item. It then finds the parent folder of that item and assigns the status value.

The key lesson here for me is that SPItem doesn’t get you access to the folder. You need to use SPListItem.File.

Censura qui curat offerre folder vel ut rem melius suadet, commodo licentia a ineo.

<Codicem>
usura System;
usura System.Collections.Generic;
usura System.Text;
usura Microsoft.SharePoint;
usura System.Collections;

Spatium nominale Conchango
{
    /// <Summary>
 /// </Summary>
 genus ManualFolderUpdate
    {
        static Irrita Main(filum[] args)
        {
            filum msh = "ManualFolderUpdate (v1.0): "; // msh = "Message Header"

 Consolandum.WriteLine(msh + "Starting up.  Last modified on 08/04/08 sum.");

            filum url = http://localhost/xyzzy;

            usura (SPSite oSPSite = novum SPSite(url))
            {

                usura (SPWeb oSPWeb = oSPSite.OpenWeb())
                {
                    SPList docLib = oSPWeb.Lists["Documents"];

                    Consolandum.WriteLine(msh + "Got the document library.");

                    Consolandum.WriteLine(msh + "Doc lib item count: [" + docLib.ItemCount + "].");

                    int FolderID = 0;
                    filum NewStatus = "Xyzzy";

                    FolderID = System.Convoco.ToInt32(args[0].ToString());
                    Consolandum.WriteLine("Seeking folder for item: [" + FolderID + "].");

                    SPListItem li = docLib.GetItemById(FolderID);

                    SPFolder thisItemFolder = li.File.ParentFolder;

                    Consolandum.WriteLine(msh + "Got the parent folder.");

                    NewStatus = args[1].ToString();
                    Consolandum.WriteLine("Setting status to [" + NewStatus + "].");

                    Consolandum.WriteLine("Press return to commit the update or CTRL-C to abort.");

                    Consolandum.ReadLine();

                    thisItemFolder.Item["Approval Status"] = NewStatus;
                    thisItemFolder.Item.Update();

                    Consolandum.WriteLine(msh + "Finished updating the folder.  Exeunt.");

                } // usura SPWeb

            } // usura SPSite

 Consolandum.WriteLine(msh + "Finished.");

        } // Main

    } // classis foldersync
} // Spatium nominale
</Codicem>

</finem>

Scribet ad mea blog.

Technorati Tags:

Dominica matutina Funny: “Pater, Non Etiam Scitis”

Nos aquilonis New Jersey Galvin scriptor sunt magna fans de politica satura tv. progressio, Cotidie Show hosted by Jon Stewart. I don’t like to get political in my blogging, dicam id quod omnes sine Quotidie Show, Ut bene permanenter perdidit omnes sensus humor in vel de 12/12/2000.

Nos sunt habens prandium in deck mane ultimum septimana et decem anni filius inducit recens episode de Ostendere. Ego fecit comment, "Jon Stewart scit quod melius non fun de me or there will be terrible consequences for Jon Stewart."

Dicens fili paulisper consideranti: "Pater, numerus: He doesn’t even know you."

Sustinui enim a numero duo, sed statuit quod satis et movetur ad deinde subiectum sine exsiliens a pulsu.

Quod dictum esse posset de genere multus magis mileage iocis, but he’s getting too used to me or too mature or both. I need to adjust somehow.

</finem>

Scribet ad mea blog.

Technorati Tags:

Operarius Lorem ipsum et materia Template — Sedem comes Bug Plus Obses Fix(?)

Hoc est satis popularis "fabulosa 40" Template. It also has a bug which is widely known (Ego etiam blogged de quam ad infige).

Sogeti dimisit a codeplex project hoc septimana quod figit cimex (quod est delicatus per se, sed non terra-fracturis) sed etiam petere ad soluta multo thornier problema: security. The fab 40 Template requirit ipsa liberalis securitatem occasum (users indiget contributor gradu accessum ad virtualiter omnia). Not any more! According to the codeplex summary:

"Hoc ipsum etiam includit consuetudinem workflow actio qua in Template ad operari sine ad omnibus users conferre permissions ad cursus album."

Quod bonis effercio et dignitas reprehendo ex.

</finem>

Scribet ad mea blog.

SharePoint amet Workflow, Eventus accepimus et “Update List Item” versus “Posuit Field in Current Item”

Nobis statuto de SharePoint excogitatoris workflows quod "communicare" with an event receiver on the list via changes to site column values. Verbigratia, si a site agmen "SetDuedate" vera posuere workflow, eventus susceptor detegit quod mutatio, reputet debitum date et assignat quod date ad aliud site agmen, "Due Date." We split things up like this because the event receiver can calculate a due date using complex business rules (accipiens weekends et comitatu festis in propter) dum SPD vere potest non.

In specialis puta, we ran into a problem with this trick. Debugging all this is pretty difficult, hic autem ad id determinat (saltem), the event receiver was not running all the time. In one step of the workflow, we would change the value of a site column and the event receiver didn’t appear to run. Autem, est currit constanter in a diversis gradum workflow.

Post recognoscens eam, Animadverti quod beatus workflow gradus usus "Update List Item" while the other step used "Set Field in Current Item." Update List Item was updating the "current item." I’m not sure why we picked one over the other since they would seem to be doing the same thing.

Ita … the Update List Item action did cause the event to fire. SED CONTRA, in pone Field in Current Item actio non.

Ego Update List Item in utroque et hyacintho! It worked. [[ Totalis seorsum, Ego lusit in vitae enim in a cotidie basis fere 15 annis ]]

Ex hoc, Ego relatione credere quod "Pone Field" actio non faciat eventus receptatores ad ignis, at least some of the time.

This issue bedeviled us for weeks.

Hoc est unum eorum "observavit moribus" posts. I observed this happen once in a specific environment and I’m making some guesses as to why things happened as they did. If you have any insight into this one, placere participes in ineo.

</finem>

Scribet ad mea blog.

Technorati Tags: