Sa anong lumilitaw na kanyang pampasinaya blog post, chiqnlips Na delved sa kabaliwan na ay isang kinakalkula haligi at inilarawan ng solusyon sa isang karaniwang SharePoint Designer workflow problema email aktibidad: How to display a person’s real name in an email instead of "domain\username."
Hindi ko pa sinubukan ito sa aking sarili, but it looks promising. Tingnan ito.
</dulo>
Sundin ako sa Twitter sa http://www.twitter.com/pagalvin
Ko na basahin ng ilang retrospectives sa 2008 and this has got me to thinking about 2009. Here are my guesses at the future of SharePoint in 2009.
Ako ay isang SharePoint MVP at bilang isang resulta, 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.
With that out of the way, on to the predictions …
I believe that FAST will become a very hot topic in 2009. It’s already well known in the enterprise search community. Gayunman, everyone that plays around with SharePoint in 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, almost everyone in the SharePoint community will have heard of and have an opinion about 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. Halimbawa, 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 search will adopt some of FAST’s features.
I believe it will come out in 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 🙂
I hope it will provide some better support for end users in SharePoint Designer and particularly workflow.
I don’t know much else, I have been actively tracking what I do find here: http://delicious.com/pagalvin/SharePoint_O14.
Ngayon, most SharePoint vendors seem to be gadget oriented. Take Kawayan o Corasworks halimbawa. They have a huge following and great portfolio of products. Gayunman, they seem sort of gadgety to me or developer / tool focused. Admin tools, workflow tools, at iba pa. That’s not a criticism at all because SharePoint can definitely use some gadgets.
Sa 2009, some vendors (and very possibly Bamboo themselves, if I read this correctly) will put together verticalized business applications in the form of templates, features, solutions, at iba pa. 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.
Sa parehong oras, Silverlight and other cool .NET stuff will fuel new, better and more interesting gadgets.
Sharepointreviews.com will become the essential community catalog of these products.
2009 will see the emergence of the End User as a major focus for bloggers, organizations and Microsoft themselves. Mark Miller’s End User SharePoint.Com played a big role in 2008 and will continue to do so in 2009. End Users will begin to blog, help to transform user groups into less technical venues and even convince someone or organization to launch a pure End User focused conference.
Speaking of conferences – they will continue to expand and grow in number and focus. Aside from end user content, they will continue to cater to developers and administrators.
Virtual conferences will start to pick up and existing conferences will provide live feeds to remote attendees who cannot or choose not to attend in person.
Free venues will expand, tulad ng Mike Lotter’s (et al) SharePoint Sabado.
This is going to be very important because there will continue to be a large influx of new developers, admins and end users who will be craving the kind of information these groups provide.
Demand for social computing features will rise. All things being equal, companies that implement effective social computing strategies will do better and be stronger than their competitors.
Smaller companies will adopt these features more quickly and effectively than large companies.
Large companies: beware 🙂
Sa 2008, a lot of SharePoint bloggers and organizations and Microsoft themselves spent a lot of time figuring out the best way to solve certain problems (usually technical problems).
There are still opportunities to define and foster adoption of best practices. Gayunman, while we’ve been figuring out the best way to install, configure and manage SharePoint, hundreds and thousands of companies have been installing, configuring and managing SharePoint without those best practices at hand.
Sa 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 and possibly spawn a cottage industry providing remediation services for companies that really need and use SharePoint, but are hurting badly because of poor decisions made early in their implementation.
Sa 2009, the Mother Ship will return and bring Bob Fox home.
I didn’t start working with SharePoint myself in any real way until January 2007. It seems to me that SharePoint has really taken off and proven itself capable of delivering a lot of value in these two years. I think that in many ways, it didn’t really straighten itself out until the infrastructure update. It still has its bugs and problems, but we’ve all come along way since 01/2007. 2009 is going to be a banner year for SharePoint.
</dulo>
Sundin ako sa Twitter sa http://www.twitter.com/pagalvin
Kukunin ko ay ang paggawa ng dalawang mga presentasyon sa SharePoint Pinakamahusay na Kasanayan Conference na ito Pebrero sa San Diego.
Hindi ko pa nai-paggawa ng bagay na ito may sapat na katagalan upang makakuha ng pinagod ito sa pamamagitan ng, kaya bawat conference dumalo ako ay isang, nang tapat, kasindak-sindak. Gayunman, 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, kaya lahat ng mga nagsasalita ay masyadong naa-access (hindi bababa sa kapag sila ay putting out fires kamalig). This means that in addition to the great formal presentations, Maaari kang magkaroon ng ilang mga mahusay na pag-uusap at debate na may virtually bawat speaker sa halos anumang oras, starting with communal breakfast up to late night imbibing at the hotel bar.
Higit pa ang mga nagsasalita, 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, magagawa mong energized at puno ng mga mahusay na ideya na magdala pabalik sa trabaho upang makatulong na mapabuti ang iyong SharePoint kapaligiran.
Mahusay Ito ay nagkakahalaga ng pamumuhunan.
The web site is top notch. Tingnan ito para sa mga petsa, rehistrasyon, mga paksa at mga speaker.
</dulo>
Sundin ako sa Twitter sa http://www.twitter.com/pagalvin
Ito nakaraang tag-init, habang ako ay nagtatrabaho sa dalawang kabanata para sa pinakamahusay SharePoint panlipunan computing libro kailanman, 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 hindi pa nababasang mga item, ito lamang sabi, "1000 ".
Sa nakalipas na ilang linggo, Ko ang pag-upo down at sistematikong pagbasa ito at pag-tag sa mga ito bilang pumunta ko para sa sanggunian sa hinaharap (Gamitin ko Delicious.com).
Ito nakaraang weekend ko pinapanood lahat ng Nawala, season apat sa isang pares ng mga sittings at pansing up sa 1000+ blog entry nararamdaman sa parehong paraan.
</dulo>
Sundin ako sa Twitter sa http://www.twitter.com/pagalvin
Mark Miller sa ibabaw www.endusersharepoint.com nai-post ang aking mga pinakabagong artikulo sa SharePoint Designer workflow dito (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, parehong site koleksyon o isang ganap na magkaibang mga bukid (e.g. mula sa pag-unlad sa produksyon).
This is a complicated subject so I only covered a very basic scenario. Sa susunod na linggo, I’ll write up a more useful real world example.
Tingnan ito at ibahagi ang anumang mga komento doon.
<dulo>
Sundin ako sa Twitter sa http://www.twitter.com/pagalvin
Mark Miller ay nai-post ang aking mga pinakabagong End User nakatuon sa SharePoint Designer workflow artikulo up sa kanyang site dito: http://www.endusersharepoint.com/?p=1008
Tatangkain kong magbigay ng straight-forward sagot sa tanong, "Why can’t I easily port a SharePoint designer workflow from development to test?" In the process, I also give some insight into what SPD is actually doing behind the scenes when we use it to create a workflow solution.
Sa susunod na linggo, I describe an End User friendly way to port SPD workflow from one server to another, or at least as End User friendly a solution as is possible given the state of the tool set.
</dulo>
Sundin ako sa Twitter sa 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. Unfortunately, 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. Gayunman, Hindi ko kailanman mawawala ang aking interes sa mga produkto at, pa nang kawili-wili, ang mas malaking problema ng findability.
Ko talagang hindi gusto ang salitang iyon, but I'm trying to get used to it 🙂 Sa kabila ng awkwardness, findability ay isang tunay na (o hindi bababa sa, umuusbong) term. Do a mabuhay paghahanap kung interesado ka sa paghahanap ng mga teknikal na mga kahulugan, ngunit ang paraan ng ipaliwanag ko ito sa paligid ng opisina ay tulad ng ito:
Intelektwal na kapital na hindi maaaring matagpuan maaaring pati na rin hindi umiiral.
Ito ay halos bilang tunay na sabihing ito:
Intelektwal na kapital na hindi maaaring matagpuan nang mabilis at madali maaaring pati na rin hindi umiiral.
Intelektwal na kapital (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. Dito nagsisimula ang gulo 🙂
Mga iyang araw, pagtatala karaniwan ay nangangahulugan na ang ideya ay dokumentado sa anyo ng isang MS Word doc, Excel workbook, at iba pa. and eventually stuck in electronic format on a hard drive somewhere. IC obviously takes other forms like, tulad ng mga imahe, mga video, lubos na nagbibigay-kaalaman blog, wiki … it’s impossible to list them all. Sa parehong oras, IC ay naka-imbak sa iba't-ibang mga lugar tulad ng mga system file, database, linya ng negosyo mga application (ERP, CRM, SharePoint, Documentum), at iba pa.
Ito ang findability problema: kung paano mabilis at madaling mahanap ang IC na ay naka-imbak sa dose-dosenang o daan-daan ng mga format sa dose-dosenang o daan-daang libo, laksaan (maglakas-loob sabihin ko daan-daang libo) ng mga lokasyon sa isang samahan?
It’s a difficult problem to solve. Bill Ingles ay pagsusulat tungkol sa 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, isang mabaliw Pranses (Ferdinand de Lesseps) Nagsimula ng pribadong kompanya upang bumuo ng mga kanal, proyekto ang inabanduna para sa ilang mga taon, 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, magpatuloy, at sa wakas matapos). And yet, it’s still not truly finished. Sa pagkaalam ko, mga bangko ng canal ni na hindi kailanman matugunan ang kanilang mga anggulo ng pahinga, 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, lalo na kung paano ito kaugnay sa 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, Pupunta ako sa subukan at ilagay ang isang kahon sa paligid ng mga problema upang ipakita kung gaano kahindik-hindik na ito ay talagang (ito ay mas kakila-kilabot kaysa sa iyong iniisip 🙂 ). It’s awful, but at least it does fit inside a box.
</dulo>
Sundin ako sa Twitter sa http://www.twitter.com/pagalvin
Ang isa sa mga … side effect … 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, kaya ng maraming mga press release ay, talaga, 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 (paramdam: ito ay tungkol sa Impormasyon).
Ang ilang mga beses, mga press release ay lubos na madaling maunawaan at isa sa mga ito ay tungkol sa Mozy. Mozy is an on-line backup tool. You install a lightweight client on your workstation (laptop sa aking kaso), mo sabihin dito kung ano ang nais mong i-back up at kung kailan at pagkatapos ay ginagawa nito ito sa pamamagitan ng pagpapadala ng iyong data sa ilang mga server(s) on the cloud. It does it in the background.
Aking unang nagpatakbo ng backup na sa loob lamang sa ilalim ng 4 hours and according to Mozy is 550MB or so of data. I only backed up "My Documents" (kaya, ang relatibong maliit na halaga ng data).
Ito nagpatakbo muli (Sa tingin ko 24 oras mamaya), back up ng ilang higit pang mga bagay-bagay tungkol sa 8 minuto. I never noticed it happen. There was no obvious impact on any work I was doing at the time.
Ako ginawa ng isang pagsubok na pagpapanumbalik at nagbibigay ito ng isang disenteng sapat na user interface upang piliin ang file(s) you want to restore. It was quick, maliksi, nagbibigay-kabatiran … Hindi ko alam kung paano ito maaaring maging anumang mas mahusay na.
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, o kung gagawin mo ngunit hindi matandaan ang pangalan nito, Mozy ay maaaring makatulong sa iyo na magkano sa mga tuntunin ng madaling paghahanap ng mga ito upang ibalik ang.
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.
Ika-line, kung may isang taong magtatanong sa akin kung dapat silang gamitin Mozy para sa mga online backup, ang aking mga sagot sa ngayon ay, "Hell, yes."
</dulo>
Sundin ako sa Twitter sa http://www.twitter.com/pagalvin
