Kama wengi SharePoint mshauri aina, I’ve been exposed to a lot of SharePoint functionality. Some times, 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.
Wiki hii, 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. Katika kesi hiyo, 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" ni SharePoint Hands maana, ni wazi kutosha, something like "turn me on if you want end users to be able to create sites when they want to."
Hivyo, Mimi kugeuka juu, kujaribu nje na kwa ajili yangu, it’s not creating sites. It’s creating site makusanyo. Pretty big difference. That’s not what I want, si wakati wote.
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, I learn that it’s deceived others as well 🙂
Mimi bado kazi nje ya jinsi ya kutoa kidogo ya mchakato wa zaidi harmoniserad wakati anakaa rena nje ya boksi, but there’s a definite path to follow. Just don’t get distracted by that label.
</mwisho>
Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin
The, you have to set the default quota in the ‘Web application general settings’ katika Usimamizi wa Kati. Mara hii ni kuweka, yoyote mpya tovuti makusanyo ya kuundwa kwa programu maalum ya mtandao kwa kutumia SSSC itakuwa na upendeleo hii kutumika.
Nakubaliana na Dan, collaboration sites especially those that users can create on a whim should be site collections in a "siloed" mbali eneo la shamba. Katika uzoefu wangu, collaboration sites within the IA of the "Information Portal" husababisha masuala zaidi chini ya kufuatilia kama kawaida database, archive / ahueni ya maeneo ya, maintainability… Mimi kusema kutoa ushirikiano watumiaji uhuru kwa kuwapa uwanja wa michezo yao wenyewe (tovuti ya ukusanyaji) na kuwa na sera katika mahali kwa wakati wao kufanya kitu kijinga kama accidently kufuta thier mwenyewe tovuti – hey tangu ni mkusanyiko tovuti angalau utakuwa rahisi kupona!
Nilishangaa….When SharePoint allows creating Top level site collection by "Self Service enabling"; kwa nini wao si kutoa kazi ya kuchagua templates upendeleo kwa ajili ya maeneo kuwa aliumbwa kutoka ukurasa huu. Mtu yeyote havind wazo lolote kama hii inawezekana?
Eric, ndiyo, ni dhahiri iwezekanavyo. Hata hivyo, siyo inapatikana nje ya boksi. Nimefanya hivyo kwa kutumia hatua desturi katika SharePoint Designer workflow kwamba waomba huduma ya mtandao ambayo inajenga tovuti… Siyo ngumu sana, lakini inachukua baadhi ya juhudi.
Je, wewe ni starehe coding na kwamba aina ya kitu? Kama ni hivyo, Naweza kukupa kuyatumia baadhi ya.
Nina swali…ni ni possibel kujenga workflow kwamba mtumiaji anaweza kick off kuzalisha tovuti ya msingi juu ya template?
Wewe ni haki kwamba hii inaweza kuwadanganya. jambo moja kutambua ingawa ni kwamba kama una mazingira rena shirikishi kwa maombi maalum ya mtandao nje ya msingi imefungwa chini ya programu ya mtandao katika mazingira yako, this comes in pretty handy 🙂 Power to the people! Viva las SharePoint! Bila shaka, kama kurejea hii juu ya, kuhakikisha kwamba upendeleo ni kutumika kwa default, mwingine inaweza kupata messy…