Nire lankide, David Drinkwine, does a (slightly more than) pen-on-napkin estimate for building a truly world class intranet for a large enterprise organization. Dezakezu read about it here: (http://www.bigapplesharepoint.com/pages/View-An-Insight.aspx?BlogID=86&stitle=WCI).
</amaiera>
SP2010 Oso cool stuff da, baina egokitu lukete zerrenda eta liburutegiak ezarpenak 'orrietan hizkuntza orduan kudeatzeko eduki mota da nahi dut:
Hizkuntza bera WSS / MOSS leku izan zen. Just aldatu hitza "delete" eta "kendu" eta bakarrik izango da lautada gehiago zentzurik.
Follow me on Twitter http://www.twitter.com/pagalvin
</amaiera>
Nire azken artikuluak SharePointBriefing.com da, eta hemen, ostikoka: http://sharepointbriefing.com/features/article.php/3887276/The-Road-to-SharePoint-Mastery.htm
Hona hemen aurkezpenik da:
Hau da, funtsean, nire publikoa Ezagunenak aurkezpen bertsioa nahiko labur eta kondentsatutako on bat "SharePoint ikasi On." Banjoa txantxak No, Hala ere,.
Ezazu!
</amaiera>
Follow me on Twitter http://www.twitter.com/pagalvin
(Kontuan izan: Artikulu hau zeharkatuko-etan hemen: http://www.endusersharepoint.com/?p=1912)
Eguneratu 09/01/09: Twitter feedback oinarritutako, I need to clarify that InfoPath is supported in the sense that BPOS provides forms libraries. What I mean when I write "not supported in any way" is that InfoPath forms services functions are not supported. That means that you can’t publish an InfoPath form to BPOS and and have it render in the web browser. It also means that some out of the box workflows, erabilera InfoPath (are standard MOSS edizioan) don’t work in BPOS because their initiation and other forms use InfoPath. Hopefully that clears things up.
Aukera bat benetan Microsoft Online eskaintza sartu dig lehenago aurten izan nuen, eta, zehazki, enpresa-produktibitatea online suite (BPOS). This came along before I even hard a firm plan to set out on my own at Arcovis. I immediately saw, Hala ere,, BPOS nire enpresaren barne azpiegitura zati gako bat izan daiteke, eta denboran zehar, it has become exactly that. Arcovis, uses it on a daily basis. I thought I’d share some of that experience from a practical perspective in case you want to evaluate it for yourself or are just curious about it.
Hitza "suite" BPOS gisa, esan nahi du, aplikazio sorta txiki bat lortuko duzu:
Horietako bakoitzean eros dezakezu, Uste dut. It’s all spelled out relatively clearly on the Microsoft gune online. You may be able to get better deals through MSFT partners. Arcovis has been working with Cloud estrategiak eta beren stuff ezagutu dirudite, beraz, horiek barne hartzen nuen zure saltzaileen zerrenda egin duzu multi-saltzaile bilaketa bat bada.
Nire esperientzia eta pentsamenduak azalduko dut horietako bakoitzean, hurrenez hurren.
Honek ekar truke ingurumena eta nire ikuspuntutik ez da, it works like any other Exchange server I have ever used. It’s fully integrated with all of my fellow Arcovis partners’ environments and gives me access to the calendar (hau da, erraldoi). Good stuff.
Era berean, Outlook Web Access (OWA) interface. That means I can get my email on any machine that has a web browser.
Nire HTC telefono mugikorra, Windows Mobile exekutatzen 6.1(?) connected to it nicely via Active Sync. It did this in exactly the way I expected and wanted.
Ez dut kontuan hartu etorkizunaren noizbehinkako eta truke erabiltzaileak baino askoz gehiago nire burua ez dago benetan garrantzitsua Exchange eginbideak besterik ez dira onartzen eta ez nuke, ezinbestean jakin izan daiteke, beraz,.
I think the strongest recommendation I make for this is that I am completely unaware that my exchange environment is “somewhere else.” I don’t know see any difference in Exchange and how I use it on a daily basis versus the half dozen or so other times I used someone’s exchange environment. Izan ere,, hobe da, besterik gabe lan egiten dugulako.
Beheko line - ostalaria trukea da, zer izan behar da eta oso pozik nago.
This is a truly indispensible tool when you’re in the consulting business. I fire up instant live meetings several times a week to show intermediate work product to clients, nire irtenbideak hondatu horiek ikusi ahal izateko, horrela, ez dakit nola konpondu, egin salmenta aurkezpenak, etc. Live meeting is bundled with BPOS and it’s very easy to use.
I’m even less of a live meeting expert than I am on exchange. Hala eta guztiz ere, nire helburuetarako, handia da.
Orain arte,, I use communicator almost only for presence information. I say “only” but have that presence data available to me whenever I’m connect has become addictive. With communicator installed and running, my colleagues know when I’m available, what my schedule is like at this moment, and can IM me (though the IM interface is pretty dull, at best). It’s one of those things that I really miss when I don’t have it. I actually get a little annoyed when my colleagues aren’t running communicator because the presence information is missing.
The presence indicator feels pervasive. It shows up in SharePoint whenever their name appears as an author to a document, esleitutako zeregina, etc. It shows in email, embedded right in outlook. It shows up in the communicator client itself.
For the most it just sits there running in the background and decorates my outlook and SharePoint screens with real-time presence information. It’s very cool.
My favorite bit, jakina, is SharePoint.
BPOS provides a modified version of MOSS standard edition. I’ll explain “modified” below. We’ve been using our BPOS SharePoint portal for stuff like:
Funtsean,, SharePoint erabiltzea espero duzun stuff.
Bidean, Ezaugarri teknikoak erabili dugun bezalako:
What can’t I do with it? There are a bunch of things that would be nice:
The last bit is a little sad because we can’t do as much search configuration I would like.
Ematen dizu, funtsean, gaitasun tekniko asko eta behartutako kanpo-de-la-kutxa SharePoint funtzionalitatea mugarik barruan bizi.
I can live with that. I have found myself wanting to slap together an event receiver or use a custom action once or twice,, baina gehienak, Ez dut nabarituko eza.
I should add that this is not a comprehensive list of the differences between a hosted “on prem” MOSS environment and SharePoint on line. Cloud Strategies has a very detailed presentation that goes into all that if you’re interested. I’m speaking from the perspective of a business owner leveraging the tool.
Microsoft bat nifty mahaigaineko aplikazio azkar eta erraz ematen BPOS funtzio guztiak eskaintzen ditu:
Zuk ez duzu erabili, baina beharra aplikazio bakoitzean sartu bereizita eta bilera zuzeneko kanporatzea, Nahiko polita da "erantzuteko orain" saioaren duzu egin ahal izango delako, besterik gabe, ekin 2 klik ("Web bidezko batzarrak" botoia gainean eta beste bat, web nabigatzaileak azalduko an). It’s also nice to get OWA with one click, ahal izango duzu, besterik gabe, nahiz eta jarri duten zure nabigatzailean gogokoetara baita.
The other major advantage with this desktop application is that it provides a background kind of single sign on service. As long as this is running in the background, Ireki dut web nabigatzaile eta nire BPOS ingurune konektatu inoiz kredentzialak sartu beharrik gabe.
Microsoft made BPOS available to me for free so I am not currently paying the monthly per user fee at this time. Hala eta guztiz ere, Balioa han ikusi dut, eta fede on onar ditzakezu (edo ez) that I would pay for this service. The fact is that I can’t count on Microsoft providing this for free forever and it’s become so strongly integrated with my business that moving … the mind quails.
BPOS is an insanely feature rich platform. Exchange, SharePoint (Moss Standard!), presentzia, berehalako zuzeneko bilerak - funtzionaltasun asko da nuke sorely, sorely miss if I had to live without it. My business would be severely impacted without it. Could I find replacement functionality? Probably, baina agian cobble elkarrekin saltzaileek beste barietate bat dut uste dut, complicating my life. BPOS has so far proven itself to be stable and reliable. For the right kind of customer (Nire enpresa bezala), BPOS indartsu kontuan merezi.
</amaiera>
Follow me on Twitter http://www.twitter.com/pagalvin
Izan dut MSDN foroak jarraituz ondo urtebete baino gehiago (eta, seguru asko, ia 2 puntu honetan urte) and every now and then I hear from someone how “hard” it is to do that. I find it quite easy and thought I’d share my “technique”. This technique also works for www.endusersharepoint.com (http://www.endusersharepoint.com/STP).
Taking MSDN as an example, I first go to standard forum page such as the General Questions for SharePoint main page here: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads
You should right away notice that the forums are RSS enabled, ikus daitekeen bezala:
I’ve been using Google Reader for managing my RSS feeds for a long time now (www.google.com / reader). I go there, add the RSS feed for the forum and now I’m getting all new forums posts via RSS. My Google feeds for SharePoint forums look like this:
Google provides me a nice view of the posting itself:
Eta, azkenik,, Google ematen dizu teklatua erabil dit foroetan mezuak joateko modu honetan.
Azkar ezin dut mezu bidez eskaneatu eta soilik sentitzen naiz zentratu erabilgarria ekarpen bat egin ahal izango dut.
Alerts close the loop. Updates to posts don’t come through RSS (Nik uste dut, erabilitako denbora luze bat dute, nahiz eta duela). Hala eta guztiz ere, Zelan foro batean mezuak bidaltzeko erantzun bat bada, the forums alert me via email and IM that someone responded in turn. Edo, ezin dudanean egin erabilgarria ekarpen bat da, baina beste batzuk, zer esan jakin nahi dut, Sartu ahal izango dut zulatzeko eta alertak esplizituki eskatu denean, beste batzuk erantzuteko.
Ordubete edo gutxiago, prozesu hori ezar dezakezu, eta ohiko erabileran, eta aste batean, ikasteko, hainbat trikimailu eta teklatu lasterbideak da, beraz, bigarren izaera bihurtzen da.
I use the exact same technique for End User SharePoint.Com’s “Stump the Panel” forums. This is their RSS feed: http://www.endusersharepoint.com/STP/rss/.
Foroak awesome modu bat dira, ziurrenik modurik onena, zuzeneko esperientzia pertsonala laburrean, produktua ikasteko eta nola munduko inkesta polit bat lortzeko, handietako, uses SharePoint. Give it a try!
</amaiera>
Follow me on Twitter http://www.twitter.com/pagalvin
Arrazoia, hainbeste denbora pasatzen dugun (edo behar, hala ere) working out governance plans is because we want the SharePoint solution to be as effective as possible. We want good infrastructure and rules to keep it humming and safe in case of disaster. We want good security processes to both properly secure the environment but also make it reasonable to manage. We want a good information architecture that will stand the test of time, ideally managing to survive a major organizational change in the company.
Desiragarria helburu hori lortzeko, gobernantza dokumentu eta plan sorta bat "duc" devolve eta "ez duc-en", bezala:
"Gorte Orokorre Thou" eta "ez zara", zalantzarik gabe, bere lekua izan gobernantza plan.
A more successful governance plan will also have a strong marketing angle. It should sell and justify itself to the maximum extent possible. A truly successful governance plan relies upon the voluntary cooperation of all SharePoint users. (Daude Fringe kasuetan ez da beharrezkoa komunitatearen lankidetza, adibidez SharePoint ongi kudeatzen erabiltzaile kopurua oso txikia da erabiltzen; Ziur besteen dezakezu uste dut). If the user community doesn’t buy into your governance plan then it will be partially successful at best.
I use that word “buy” deliberately. The community will buy the governance plan if it’s fundamentally sound and you go to some effort to sell them on it. Selling leads to marketing and that’s why I think that a governance plan should be considered a marketing plan too. Convince your end users that they need to follow the governance plan and they will voluntarily follow it. If you can get a critical mass of people following the governance plan then the plan’s benefits follow and you’ll have a stronger environment for it.
</amaiera>
Follow me on Twitter http://www.twitter.com/pagalvin
MSDN foroak buruz luze idatzi nuen, protokoloak, izendatzen konbentzio, bilatu, etc. I may do that, Izan ere,. I wanted to point out a small thing which may help people have a better overall experience.
Azkenaldian dut jendeak kontatzeko arazo mota batzuk sartu exekutatu zure SharePoint ingurumena, garapen-proiektu edo beste SharePoint erlazionatutako jarduera, post a question to the forums earlier in your action chain rather than later. I know for myself that when I have a problem, a number of potential solutions present themselves right away. I order these potential solutions in terms of likelihood, applicability and how easy they are to investigate. I go through that list and by the time I’ve gotten to #10, Erregistro aldaketa egiten dut, giltza "/ foo / bar / almostThere / isThisIt / noThisIsNotIt / iCantBelieveIAmDoingThis / finallyThere!"Blog baten aholkuari orrian aurkitu 8 of a Google search. When that doesn’t work, MSDN galdera bat bidaltzeko, azkenik, I (e.g. hemen: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads).
I suggest that you reverse that approach. Post the forums much earlier in your investigation because:
Beraz,, funtsean, erraza eta doakoa da eta erantzun mota batzuk lortzeko jaurtiketa ona duzu, baina pixka bat hartuko du erantzun hori lortzeko (berriro, Oraindik duzu, zortea ezean).
I used to think that I should hold off on looking for community help because I don’t want to waste someone’s time asking for help when I could find it out myself. Some forum moderators and active participants may feel that way, baina ez dut (gutxienez, Nik ez dut neure burua horrela sentitzen gehiago). I don’t see any downside. The worst case is that you post a question and then answer it yourself some time later, possibly “wasting” some one’s time. I don’t see a big risk in that and there’s value in the researching of questions like that in any event.
</amaiera>
Follow me on Twitter http://www.twitter.com/pagalvin
Irakurri dut pare bat atzera begirako an 2008 and this has got me to thinking about 2009. Here are my guesses at the future of SharePoint in 2009.
SharePoint MVP bat naiz eta, ondorioz,, I sometimes get a little advance information before it’s public. I am NOT making any such information public. I really haven’t been around long enough to be entrusted with that kind of stuff anyway.
Modu kanpo duten, to iragarpenak on ...
I believe that FAST will become a very hot topic in 2009. It’s already well known in the enterprise search community. Hala eta guztiz ere, denek jotzen inguruan SharePoint batera 2009 will soon be interested in this product and what it can do for them. New consulting companies will spring up around it and existing partners will work and scramble to add it to its portfolio. This time next year, ia SharePoint komunitatean, denek izango dute entzun eta azkar buruzko iritzia izan.
FAST is targeted at large companies and that will continue. I think there’s at least an outside chance that Microsoft will release a more focused version of the product that is accessible to smaller companies. Failing that, they will open up the SharePoint search engine so that it can be customized along the lines that FAST can be customized. Adibidez, FAST uses pipeline architecture for consuming content and indexing it. FAST admins and developers can assemble pipeline components per data source and even create new pipeline components. We don’t have this flexibility with SharePoint today. If FAST remains firmly targeted at very large companies, SharePoint bilaketa azkarra ezaugarri batzuk hartuko ditu.
Atera egingo da sinesten dut 2009.
I believe that it will provide us the ability to secure views on a list or document library. This may be more of a hope than a belief 🙂
Azken erabiltzaileei laguntza hobea batzuk emango da SharePoint Designer eta, bereziki, workflow espero dut.
Ez dakit askoz bestela, I have been actively tracking what I do find here: http://delicious.com/pagalvin/SharePoint_O14.
Gaur egun, most SharePoint vendors seem to be gadget oriented. Take Banbu edo Corasworks adibidez. They have a huge following and great portfolio of products. Hala eta guztiz ere, gadgety moduko dirudite niri edo sustatzailearen / tool focused. Admin tools, Tresna workflow, etc. That’s not a criticism at all because SharePoint can definitely use some gadgets.
Urtean 2009, saltzaileek batzuk (eta oso seguru asko, beraiek Bamboo, irakurri dut hau bada behar bezala) batera jarriko verticalized enpresa aplikazio txantiloiak formularioa, ezaugarri, irtenbideak, etc. I’m thinking about the fabulous forty templates today but tailored to specific industries. I’m sort of surprised it’s not already exploited this way. SharePoint is a platform for delivering these kinds of things. What’s everyone waiting for? They won’t wait any longer in 2009.
Aldi berean,, Silverlight eta beste cool. NET gauza berriak erregaia egingo, hobea eta interesgarri gadgets.
Sharepointreviews.com produktu hauen komunitatearen funtsezko katalogo bihurtuko dira.
2009 Amaiera Erabiltzaileak sorrera ikusiko blogari nagusietako foku gisa, organizations and Microsoft themselves. Mark Miller End Erabiltzaile SharePoint.Com rola jokatu handi batean 2008 and will continue to do so in 2009. End Users will begin to blog, laguntzeko Erabiltzaile taldeak eraldatzeko aretoak gutxiago teknikoak sartu eta nahiz eta norbait edo erakundea konbentzitu hutsa End Erabiltzaile bideratuta hitzaldi abiarazteko.
Speaking of conferences – they will continue to expand and grow in number and focus. Aside from end user content, jarraituko da, garatzaileei eta administratzaileak erantzuteko dute.
Virtual hitzaldiak jasotzen hasiko da eta aurretik dauden hitzaldiak zuzeneko jarioak emango urruneko ekitaldira joan ezin duten edo aukeratu ez pertsonalki joatea.
Free egoitzatan egingo zabaltzeko, esate baterako, Mike Lotter en (et al) SharePoint larunbata.
Hau oso garrantzitsua izango da bertara, garatzaile berriak ugaritasuna handi bat izaten jarraituko baitu, kudeatzaileek eta erabiltzaileek duten craving izango informazio mota talde horiek.
Demand for social computing features will rise. All things being equal, duten enpresak ezartzeko eraginkorra gizarte informatika estrategiak hobeto egin izan ditu, eta bere lehiakideak baino indartsuagoa.
Enpresa txikiagoak ezaugarri hauek hartuko ditu modu azkar eta eraginkorrean enpresa handiak baino.
Enpresa handiak: beware 🙂
Urtean 2008, SharePoint blogari eta erakunde eta Microsoft beraiek asko igaro denbora asko out kalkulatzen modurik onena zenbait arazo konpontzeko (normalean arazo teknikoak).
There are still opportunities to define and foster adoption of best practices. Hala eta guztiz ere, dugu sido bitartean kalkulatzen modurik onena instalatu, konfiguratzeko eta kudeatzeko SharePoint, ehunka eta milaka enpresa izan dira instalatzen, konfigurazioa eta kudeatzeko SharePoint eskuan praktika horiek onena gabe.
Urtean 2009, a lot of companies are going to realize they have some deeply rooted problems to solve and will be looking to the elite members of the SharePoint community and Microsoft for help to fix them. I think this will extend well into 2010 eta, seguru asko abiarazi cottage industria konponketa zerbitzuak eskaintzen duten enpresa benetan behar eta SharePoint erabili, baina gaizki mina delako erabakiak eskasa egin hasieran euren ezarpenean.
Urtean 2009, Ama-ontzia eta itzuli egingo ekarri Bob Fox hasiera.
Nik ez dut neure burua SharePoint edozein modu errealean lan egiten urtarrila arte 2007. Iruditzen zait SharePoint dela benetan hartu off frogatu eta beraren balioa asko entregatu bi urte hauetan gai diren. Uste dut modu askotan, ez da benetan bere burua altxa out azpiegitura egunera arte. Du, hala ere, bere arazoen eta arazoak, baina dugu modu batera etorri zenetik 01/2007. 2009 SharePoint da urte pankarta bat izango.
</amaiera>
Follow me on Twitter http://www.twitter.com/pagalvin
Hau da, nahiko popular "Primerako 40" txantiloia. It also has a bug which is widely known (Are dut nola konpondu buruz Blogetakoak).
Sogeti bat kaleratu codeplex proiektua aste hau bug konpontzen (hau da, berez, polita, baina ez lurra-shattering) baina erreklamatzeko ere konpondu dute askoz thornier arazoa: security. The fab 40 txantiloi bat oso eskuzabala segurtasun ezarpena eskatzen du (erabiltzaile laguntzaile maila sarbidea behar du ia guztia). Not any more! According to the codeplex summary:
"This template also includes a new custom workflow action which enables the template to work without having to give all users contribute permissions to the courses list."
Hori gauza ona da eta merezi checking da.
</amaiera>
