Katika nini inaonekana kuwa blog yake ya uzinduzi posting, chiqnlips ina delved katika wazimu kwamba ni safu ya mahesabu na ilivyoelezwa ufumbuzi wa ya kawaida SharePoint Designer tatizo workflow email shughuli: How to display a person’s real name in an email instead of "domain\username."
Mimi si kupimwa ni mimi mwenyewe, but it looks promising. Kuangalia ni nje.
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
Nimesoma retrospectives chache juu ya 2008 and this has got me to thinking about 2009. Here are my guesses at the future of SharePoint in 2009.
Mimi nina MVP SharePoint na kama matokeo, 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.
Pamoja na kwamba nje ya njia, kwenye utabiri ...
I believe that FAST will become a very hot topic in 2009. It’s already well known in the enterprise search community. Hata hivyo, kwamba kila mtu anacheza karibu na SharePoint katika 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, karibu kila mtu katika jamii SharePoint itakuwa nimesikia habari na kuwa na maoni juu FAST.
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. Kwa mfano, 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 tafuta mapenzi kupitisha baadhi ya makala ya FAST.
Naamini itakuwa kuja nje katika 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 🙂
Natumaini itakuwa kutoa baadhi msaada bora kwa watumiaji wa mwisho katika Designer SharePoint na hasa workflow.
Sijui kiasi kingine, I have been actively tracking what I do find here: http://delicious.com/pagalvin/SharePoint_O14.
Leo, most SharePoint vendors seem to be gadget oriented. Take Mianzi au Corasworks kwa mfano. They have a huge following and great portfolio of products. Hata hivyo, wanaonekana aina ya gadgety kwangu au developer / tool focused. Admin tools, workflow zana, nk. That’s not a criticism at all because SharePoint can definitely use some gadgets.
Katika 2009, baadhi ya wachuuzi (sana na uwezekano wa Bamboo wenyewe, kama mimi kusoma hii kwa usahihi) kuweka pamoja maombi ya biashara verticalized katika fomu ya templates, makala, ufumbuzi, nk. 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.
Wakati huo huo, Sliverlight na nyingine baridi. NET mambo itazua mpya, bora zaidi na ya kuvutia gadgets.
Sharepointreviews.com itakuwa muhimu jumuiya ya orodha ya bidhaa hizo.
2009 utaona kuibuka mtumiaji Mwisho kama shabaha kuu kwa wanablogu, organizations and Microsoft themselves. Mwisho Mark Miller Maoni ya SharePoint.Com jukumu kubwa la 2008 and will continue to do so in 2009. End Users will begin to blog, kusaidia kubadilisha makundi ya mtumiaji katika kumbi chini ya kiufundi na hata kushawishi mtu au shirika kuzindua safi mtumiaji wa mwisho ililenga mkutano.
Speaking of conferences – they will continue to expand and grow in number and focus. Aside from end user content, wataendelea kuhudumia watengenezaji na watendaji.
Mikutano virtual kuanza kuchukua na zilizopo mikutano itatoa kuishi feeds kwa waliohudhuria kijijini ambao hawawezi au kuchagua si kuhudhuria katika mtu.
Kumbi bure itapanua, kama vile Mike Lotter ya (et al) SharePoint Jumamosi.
Hii ni kwenda kuwa muhimu sana kwa sababu kuna itaendelea kuwa na kufurika kubwa ya watengenezaji mpya, admins na watumiaji wa mwisho ambao watakuwa tamaa aina ya taarifa makundi haya kutoa.
Demand for social computing features will rise. All things being equal, makampuni ambayo kutekeleza mikakati madhubuti ya kompyuta kijamii kufanya vizuri na kuwa na nguvu zaidi kuliko washindani wao.
Makampuni madogo kupitisha makala haya kwa haraka zaidi na kwa ufanisi zaidi kuliko makampuni makubwa.
Makampuni makubwa ya: beware 🙂
Katika 2008, mengi ya wanablogu SharePoint na mashirika na Microsoft wenyewe alitumia muda mwingi kuhesabia njia bora ya kutatua matatizo ya baadhi ya (kawaida matatizo ya kiufundi).
There are still opportunities to define and foster adoption of best practices. Hata hivyo, wakati tumekuwa kuhesabia njia bora ya kufunga, configure na kusimamia SharePoint, mamia na maelfu ya makampuni wamekuwa kufunga, Configuring na kusimamia SharePoint bila mazoea ya wale bora katika mkono.
Katika 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 na uwezekano wa spawn sekta ya Cottage kutoa huduma remediation kwa makampuni ambayo kwa kweli wanahitaji na kutumia SharePoint, lakini ni kuumiza vibaya kwa sababu ya maamuzi maskini kufanywa mapema katika utekelezaji wake.
Katika 2009, Meli mama atarudi na kuleta Bob Fox nyumbani.
Mimi si kuanza kufanya kazi na SharePoint mwenyewe katika njia yoyote halisi hadi Januari 2007. Inaonekana kwangu kwamba SharePoint ina kweli kuchukuliwa mbali na kuthibitika yenyewe uwezo wa kutoa mengi ya thamani katika miaka hii miwili. Nadhani kwamba katika njia nyingi, haikuwa kweli kunyoosha yenyewe nje mpaka miundombinu update. Bado ina matatizo yake na mende, lakini tumekuwa wote kuja njiani tangu 01/2007. 2009 ni kwenda kuwa mwaka bendera kwa SharePoint.
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
Mimi itakuwa kufanya maonyesho mawili katika SharePoint Best Practices Mkutano huu Februari katika San Diego.
Mimi si kufanya jambo hili kwa muda wa kutosha kupata jaded kwa hilo, hivyo kila mkutano mimi kuhudhuria ni, kusema ukweli, kutisha. Hata hivyo, I do think this conference is special. There is zero marketing focus and the whole thing is about offering real-world practical advice on how to untangle some of the thorniest issues we face dealing with SharePoint. It’s not gigantic, hivyo wote wa wasemaji ni kupatikana sana (angalau wakati wao si kuweka nje moto nyuma nyumbani). This means that in addition to the great formal presentations, unaweza kuwa na mazungumzo na baadhi kubwa ya mijadala na karibu msemaji kila saa karibu wakati wowote, starting with communal breakfast up to late night imbibing at the hotel bar.
Zaidi ya wasemaji, you’ll have great opportunities to build and cement networks of other SharePoint users in the community. By the end of the last session and conference wrap-up, wewe utakuwa energized na kamili ya mawazo mazuri ya kuleta nyuma kazi ya kusaidia kuboresha yako SharePoint mazingira.
Ni vizuri yenye thamani ya uwekezaji.
The web site is top notch. Kuangalia ni nje kwa tarehe, usajili, mada na wazungumzaji.
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
Huu majira zamani, while I was working on two chapters for the best SharePoint social computing book ever, I began to get very far behind in my blog reading. I use Google Reader for my RSS stuff and when you have more than 1000 unread vitu, tu anasema, "1000 ".
Zaidi ya mwisho ya wiki chache, I’ve been sitting down and systematically reading them and tagging them as I go for future reference (I use Delicious.com).
This past weekend I watched all of Lost, season four in a couple of sittings and catching up on 1000+ blog entries feels the same way.
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
Mark Miller zaidi ya saa www.endusersharepoint.com posted makala yangu ya karibuni juu ya SharePoint Designer workflow hapa (http://www.endusersharepoint.com/?p=1037).
I describe the basic approach for moving a workflow you create in one list to another list. The other list can be in the same site, sawa tovuti ukusanyaji au shamba tofauti kabisa (e.g. na maendeleo ya uzalishaji).
This is a complicated subject so I only covered a very basic scenario. Wiki ijayo, I’ll write up a more useful real world example.
Kuangalia nje na kushiriki maoni yoyote kuna.
<mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
Mark Miller ina posted Mwisho wangu karibuni mtumiaji oriented SharePoint Designer Workflow makala kwenye tovuti yake hapa: http://www.endusersharepoint.com/?p=1008
Mimi kujaribu kutoa jibu sawa-mbele kwa swali, "Why can’t I easily port a SharePoint designer workflow from development to test?" In the process, Mimi pia kutoa baadhi ya ufahamu katika yale SPD ni kweli kufanya nyuma ya pazia wakati sisi kutumia kwa kujenga ufumbuzi workflow.
Wiki ijayo, Mimi kueleza mtumiaji Mwisho kirafiki njia ya bandari SPD workflow kutoka server moja hadi nyingine, au angalau kama mtumiaji wa mwisho wa kirafiki ufumbuzi kama inawezekana kutokana na hali ya kuweka chombo.
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
I had the good fortune of attending some partner training from FAST last spring. I was really impressed with the product and was looking forward to working with it. Kwa bahati mbaya, one project fell through and then EMC acquired my company. Predictably, a certain amount of chaos ensued while we learned about EMC and EMC learned about us. FAST technology dropped a few points on the priority scale during that period. Hata hivyo, I never lost my interest in the product and, more interestingly, the bigger problem of findability.
I really don’t like that word, but I’m trying to get used to it 🙂 Despite it’s awkwardness, findability is a real (au angalau, emerging) term. Do a live search if you’re interested in finding more technical definitions, but the way I explain it around the office is like this:
Intellectual capital that cannot be found may as well not exist.
It’s almost as true to say this:
Intellectual capital that cannot be found quickly and easily may as well not exist.
Intellectual capital (IC) starts as an idea in a person’s head and is then refined via collaboration with colleagues and interactions with various communities. To be truly useful, these resulting ideas must be recorded. This is where the trouble begins 🙂
Siku hizi, recording normally means that the idea is documented in the form of an MS Word doc, Excel workbook, nk. and eventually stuck in electronic format on a hard drive somewhere. IC obviously takes other forms like, like images, videos, highly informative blogs, Wiki … it’s impossible to list them all. Wakati huo huo, IC is stored in a variety of places like file systems, databases, line of business applications (ERP, Ali, SharePoint, Documentum), nk.
This is the findability problem: how can quickly and easily find IC that is stored in dozens or hundreds of formats in dozens or hundreds of thousands, tens of thousands (dare I say hundreds of thousands) of locations in an organization?
It’s a difficult problem to solve. Bill English has been writing about findability from a very grand perspective in what I have come to think of as the Panama Canal approach. The history of the Panama Canal is amazing. In a nut shell, a crazy Frenchman (Ferdinand de Lesseps) started a private company to build the canal, the project was abandoned for some years, picked up again and finally finished by the American government under President Roosevelt. This reminds me of Bill’s approach because as he rightly points out, solving the findability is both hard and never stops. It took years and years of effort from the some of the hardest working humans on the planet to start, kuendelea, and finally finish). And yet, it’s still not truly finished. Mbali kama mimi najua, the canal’s banks have never met their angle of repose, meaning that they have to be shored up and otherwise maintained even to this day. Solving findability is the same way. I definitely recommend that you read Bill’s series and subscribe to his blog for his point of view on findability, particularly as it relates to SharePoint.
I too am interested in this problem. Due to my exposure to FAST and on-going discussions on this subject with my brilliant EMC colleagues, I have some more ideas I plan to write about over the coming weeks and months. In my next article on this little series, I’m going to try and put a box around the problem to show how awful it really is (it’s more awful than you think 🙂 ). It’s awful, but at least it does fit inside a box.
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
Moja ya … madhara … of working for a giant corporation is that I get a lot press releases in my inbox every month. I’m still new to the EMC world, hivyo mengi ya releases hizi vyombo vya habari ni, kimsingi, inscrutable. This or that company purchased these or those EMC products, blah blah blah. I’m not complaining. I actually take this as an incentive to learn more about EMC as time goes by so that I better understand the big picture of what EMC is all about (ladha: it’s about Habari).
Some times, those press releases are quite easy to understand and one of them was about Mozy. Mozy is an on-line backup tool. You install a lightweight client on your workstation (laptop in my case), you tell it what you want to back up and when and then it does it by sending your data to some server(s) on the cloud. It does it in the background.
My initial backup ran in just under 4 hours and according to Mozy is 550MB or so of data. I only backed up "My Documents" (hence, the relatively small amount of data).
It ran again (I think 24 hours later), backed up some more stuff in about 8 dakika. I never noticed it happen. There was no obvious impact on any work I was doing at the time.
I did a test restore and it provides a decent enough user interface to select the file(s) you want to restore. It was quick, snappy, informative … I don’t know how it could be any better.
I spoke to one of my colleagues about it who has more experience with online backup. He said that Mozy is good but that it lacks an ability to tell Mozy to do the equivalent of "restore files that I deleted." This is to say that if you don’t know you deleted a fie, or if you do but don’t remember its name, Mozy may not help you much in terms of easily finding it to restore.
They impose a 2GB limit if you just want to use the service for free. It looks like it’s $5/month for unlimited storage.
Bottom line, if someone asks me if they should use Mozy for online backup, my answer right now is, "Hell, yes."
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
