I’m on a project where we need to collect metrics around a function named "Share a Story." The idea is very simple — ако сте у потрази на занимљивом чланку о интранету и желите да се га поделите са неким, click a link labeled "Share this story" пошаљи га то иоур другара.

Ми смо играли са око прилагођеном облику за ову намену, али на крају, Здрав разум победио и дан смо само користите упознат <хреф = маилто:…> technique. (<хреф маилто:…> је изненађујуће робустан мало ХТМЛ-а; као бонус, које су повезане ме враћа на моје старе УНИКС ман странама дана; то су били дани!).

Ова техника пружа одличан интерфејс за крајње кориснике, јер они добијају да своје познате МС Оутлоок клијента (или шта год емаил клијент су инсталирали).

То чини ствари теже по нас лоше програмерске врста јер клијент * и * жели да покренете извештај у будућности који показује колико често корисници деле приче, па чак и приче које се деле најчешће.

We whiteboarded a few potential solutions. My favorite is to carbon copy (ЦЦ) a SharePoint list. That way, the end user still gets the outlook client while we get to capture the event because we’ll get a copy of the email ourselves. There are some obvious drawbacks. The main problem is that the user could simply blank out or otherwise mangle the CC address. И, we need to manage that event library of emails. We have a scheduled job on the white board responsible for that cleanup.

Уколико имате неки паметан приступ решавању овог проблема, молим вас реците.

</крај>

Претплатите се на мој блог.

Следите ме на Туиттер на http://www.twitter.com/pagalvin

Као што је тражио и обећао, I’ve uploaded my presentation on how to obtain "great" requirements from end users for SharePoint projects and implementations. It’s here: хттп://цид-1цц1едб3даа9б8аа.скидриве.ливе.цом/селф.аспк/СхареПоинт/Паул 20Галвин%%% 20Греат 20Рекуирементс.зип

Изнео сам овај на СхареПоинт најбољих пракси конференцији у фебруару 2009 (ввв.схарепоинтбестпрацтицес.цом). If you attended the conference, такође ћете добити ово на конференцији ДВД.

The presentation includes a lot of notes with most slides. It’s not just bullet points.

(See here for my other presentation on a governance case study: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!3099.entry

</крај>

Претплатите се на мој блог.

Следите ме на Туиттер на http://www.twitter.com/pagalvin

Попут многих врста СхареПоинт консултантских, I’ve been exposed to a lot of SharePoint functionality. Неки пута, 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.

Ове недеље, 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. У овом случају, 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" СхареПоинт Линго је значење, очигледно довољно, something like "turn me on if you want end users to be able to create sites when they want to."

Тако, Окрећем се на, Пробајте и за мене, it’s not creating sites. It’s creating site колекције. Pretty big difference. That’s not what I want, нимало.

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 🙂

Ја сам још увек радимо на томе како да се обезбеди мало модернизовану процеса током боравка чисто из кутије, but there’s a definite path to follow. Just don’t get distracted by that label.

</крај>

Претплатите се на мој блог.

Следите ме на Туиттер на http://www.twitter.com/pagalvin

Ја сам био један од 20 или 30 (или можда 100?) панелисти синоћ Њујорк Корисници СхареПоинт групе meeting. Instead of the usual presentation format, ово је све о К&A between the audience and the panel members. Early on, Мајкл Лоттер увео ме у нове идеје и желео сам да поделим.

An audience member described how his company had paid a consultant to write an application for his company. The consultant wrote it as a console application using the SharePoint object model. Као резултат тога, this meant that the program had to be run on a server in the farm. This meant that anyone that wanted to use the app would have to log onto the server, do the work and log off. Прво, ово није био проблем, али ускоро, више (не-техничке) users needed to use the utility. His question was (парафразирање):

"What are my options? I don’t want to keep letting users log directly onto the server, али им је потребно да функционалност."

Мајкл Лоттер предложио да конфигуришете нову виртуелну машину, join it to the farm as a WFE and let users run the application from there.

This is a pretty stunning idea for me. Generalizing this solution brings to mind the notion of essentially temporary, almost disposable WFE’s. I think it’s a pretty neat concept. This temporary WFE can run a console application that uses the SharePoint object model. You could also use it to run stsadm commands. It doesn’t have to be part of regular local balancing. If it goes down or gets wrecked, you can just spin up a new one. I repeat myself, али морам да кажем да мислим да је стварно уредан идеја.

</крај>

Претплатите се на мој блог.

Следите ме на Туиттер на http://www.twitter.com/pagalvin

Прошле недеље, неко је поставио питање о стварању амбијента који би СхареПоинт рукује прилично велику количину нових докумената (10,000 +/- у овом случају). I don’t know much about this, али захваљујући овом белом папиру, Осећам се много боље информисани.

За мене, Овај бели папир је прилично једноставно књига ознака у тренутку, but I did start reading through it and thought I’d highlight my main take-away. SharePoint can be scaled to handle, у најмању руку, ово оптерећење:

• 50к нова документа дневно.
• 10 Укупна милиона докумената.

I write the 50k/10MM figures because they are easy enough to remember. As long as you know they are minimums, you won’t get into trouble. The maximums are at least 10 одсто већи него и са Ектреме Тунинг, вероватно много већи.

Хвала, Мике Валсх, још једном за његов недељно ВСС ФАК исправке и корекције пост. If you’re not subscribed to it, озбиљно треба мислити о томе ради.

</крај>

Претплатите се на мој блог.

Током протекле недеље, мој колега and I were doing some work for a client in NYC. We were testing a different aspects of a MOSS implementation using their "standard" Воркстатион буилд (за разлику од наших лаптоп рачунара). While doing that, наишли смо на неколико грешака тако што ћете пратити следеће кораке:

• Отворите МС Ворд документ из Виндовс Екплорера (који користи ВебДАВ).
• Направите промену.
• Сачувајте га.

Дошли смо да схватимо да неки пута (обично први пут) смо сачували документ, the save didn’t "stick." Save did not save. We would pull that document back up and our changes simply were not there.

Нисмо разумели питање корена у овом тренутку, but we figured that we should make sure that the latest MS Office service pack had been installed on that work station. The IT folks went and did that. We went through the test again and we discovered a new problem. When we saved it, ми смо сада добили ову грешку:

Овај пут, изгледало је као да је свака промена, заправо, сачувана, whether we answered Yes or No to the scripts question.

Коначно смо имали поглед на актуелну верзију система Оффице, а испоставило се да је радна станица ради МС Оффице 2000 сервице пацк 3 који се појављује под Помоћ -> About as "Office 2002".

Наравоученије: Увек ће користити Оффице 2003 као мој минимална верзија основног канцеларијског када користите ВебДав и маховине.

</крај>

Претплатите се на мој блог.

(За потребе претраживача, ово је греска у тексту):

Линија: 11807

Знак: 2

Грешка: Објекат не подржава ово својство или метод

Код; 0

УРЛ адреса: http://sharepoint01/DocumentReview/_vti_bin/owssvr.dll?location=Documents/1210/testworddocument.doc&dialogview=SaveForm

Да ли желите да наставите покретање скрипти на овој страници?

In one or my very first blog posts, Ја сам описао цео процес пратили смо да пребаце клијентима из СПС-а 2003 to MOSS. Читалац лефт а цоммент тражећи више детаља и овде је.

За тај пројекат миграције, смо морали да нађемо добар начин да се крене пуно СПС 2003 documents over to MOSS. The initial load was easy enough. Create a new target document library in MOSS and use windows explorer to move the documents.

This is the new document library:

Open up two windows explorers. Point the first at SPS 2003 and the second at the new document library in MOSS. The following screen shot shows this. Note that the top browser is actually pointing at my c:\temp drive, but you can imagine it pointing to an SPS 2003 document library:

After that drag and drop operation, my target looks like this:

Now it’s time to deal with the metadata. Assume we have just one column of metadata for these documents named "location." We can see from the above "all documents" view that the location is blank. It’s easy enough to use a data sheet view to enter the location, or even go into each document’s properties one by one to add a location. Let’s assume that there is no practical way to assign the location column a value automatically and that end users must do this by hand. Furthermore, let’s assume there are hundreds of documents (maybe thousands) and that it will take many many days to update the metadata. As we all know, no one is going to sit down and work for four of five days straight updating meta data for documents. Уместо тога, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" view as shown:

Сада, when someone sits down to spend their allocated daily hour or two to tag migrated documents, they can use the "untagged documents" view to focus their effort:

As users tag documents, they drop off this list.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. Оут оф тхе бок, there’s no way to prevent a user from uploading a document to MOSS and then not enter meta data. We can specify that a particular site column is mandatory and the user won’t be allowed to push the save button. Међутим, if the user uploads and then closes the browser (or uses windows explorer to upload the document), we can’t force the user to enter meta data (поново, out of the box).

This approach can be used to help with that situation. We can use a "poorly tagged data" view to easily identify these documents and correct them. Couple this with a KPI and you have good visibility to the data with drill-down to manage these exceptional circumstances.

</крај>

Претплатите се на мој блог.

Ове недеље, Ја сам се борио мало са својим тимом да се инсталира Мос у једноставном две фарме сервера. Пошто прође кроз то, Имам више разумевања за оне врсте проблема људи пријављују на МСДН форумима и на другим местима.

Коначна фарма конфигурација:

• СКЛ / Индек / интранет ВФЕ унутар зида.
• ВФЕ у ДМЗ.
• Some kind of firewall between the DMZ and the internal server.

Before we started the project, we let the client know which ports needed to be open. During the give and take, back and forth over that, we never explicitly said two important things:

1. SSL means you need a certificate.
2. The DMZ server must be part of a domain.

Day one, we showed up to install MOSS and learned that the domain accounts for database and MOSS hadn’t been created. To move things along, we went ahead and installed everything with a local account on the intranet server.

У овом тренутку, we discovered the confusion over the SSL certificate and, нажалост, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. У међувремену, we solution architects moved ahead with the business stuff.

A weekend goes by and the client obtains the certificate.

Our infrastructure guy shows up and discovers that the DMZ server is not joined to any domain (either a perimeter domain with limited trust or the intranet domain). We wasted nearly a 1/2 day on that. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….

Another day passes and the various security committees, interested parties and (not so) innocent bystanders all agree that it’s OK to join the DMZ server with the intranet domain (this is a POC, уосталом, not a production solution).

Infrastructure guy comes in to wrap things up. This time we successfully pass through the the modern-day gauntlet affectionately known as the "SharePoint Configuration Wizard." We have a peek in central administration and … yee haw! … DMZ server is listed in the farm. We look a little closer and realize we broke open the Champaign a mite bit early. WSS services is stuck in a "starting" статус.

Да скратимо причу, it turns out that we forgot to change the identity of the service account via central administration from the original local account to the new domain account. We did that, re-ran the configuration wizard and voila! We were in business.

</крај>

Претплатите се на мој блог.

Иако то није буквално истина, у практичном смислу, Интернет суочава веб предњи крај у ДМЗ мора бити у домену (и.е. није неки самостални сервер у свом малом радној групи). То не треба да буде у истом домену као унутрашње ВФЕ(с) и другим серверима (и вероватно не би требало), but it needs to be a domain.

My colleagues and I spent an inordinate amount of time on a proposal which included SharePoint pre-requisites. This included a comprehensive list of firewall configurations that would enable the DMZ server to join the farm and so forth. Нажалост, we failed to add a sentence somewhere that said, to the effect, "the whole bloody point of this configuration is to allow your DMZ WFE server, in a domain, to join the internal farm."

A perfect storm of events, where we basically looked left when we might have looked right, conspired to hide this problem from us until fairly late in the process, thus preventing me from invoking my "tell bad news early" rule.

Уздах.

Претплатите се на мој блог.

Форум корисници често као оваква питања:

> Здраво,
>
> Молим вас реците ми да ли постоје могућности за изградњу прилагођене листе са
> мастер и детаљ типа (као фактура) без употребе ИнфоПатх.
>

СхареПоинт пружа неке из кутије функција које подржавају врсте пословним захтевима као што је тај.

У глобалу, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Користите додатне листе за одржавање бројева купаца, бројеви производа, итд.

Користите Веб сегмент упита садржаја (у МОСС само) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (СРС) је такође доступан за извештајни стране њега.

Међутим, there are some important limitations that will make it difficult to use pure out-of-the-box features for anything that is even moderately complex. These include:

• Величина вези листе проналажење вс. "smartness" of the lookup column type. A lookup column type presents itself on the UI differently depending on whether you’ve enabled multi-select or not. In either case, the out-of-the-box control shows all available items from the source list. If the source list has 1,000 ставке, that’s going to be a problem. The lookup control does not page through those items. Уместо тога, it pulls all of them into the control. That makes for a very awkward user interface both in terms of data entry and performance.
• Lookups "pull back" one column of information. You can never pull back more than one column of information from the source list. На пример, you cannot select a customer "12345" and display the number as well as the customer’s name and address at the same time. The lookup only shows the customer number and nothing else. This makes for an awkward and difficult user interface.
• No intra-form communication. Писао сам о томе овде. You can’t implement cascading drop-downs, условно омогућите / онемогућите поља, итд.
• No cascading deletes or built-in referential integrity. SharePoint treats custom lists as independent entities and does not allow you to link them to each other in a traditional ERD sense. На пример, СхареПоинт вам омогућава да креирате две прилагођене листе, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Онда, you can delete the customer from the list. Оут оф тхе бок, there is no way to prevent this. To solve this kind of problem, што то обично користите за претовар догађаја.

То може да изгледа суморно, but I would still use SharePoint as a starting point for building this kind of functionality. Though there are gaps between what you need in a solution, СхареПоинт нам омогућава да попуни те празнине коришћењем алата као што су:

• Event handlers. Use them to enforce referential integrity.
• Прилагођене колоне: Create custom column types and use them in lieu of the default lookup column. Add paging, баферовање и АЈАКС функције да их одговоре.
• БДД. This MOSS-only feature enables us to query other SharePoint lists with a superior user interface to the usual lookup column. BDC can also reach out to a back end server application. Use BDC to avoid replication. Rather than replicating customer information from a back end ERP system, use BDC instead. BDC features provide a nice user interface to pull that information directly from the ERP system where it belongs and avoids the hassle of maintaining a replication solution.

  БДД је МОСС функција (није доступна у ВСС) and is challenging to configure.

• АСП.НЕТ Веб Форм: Направите потпуно функционалан АЈАКС омогућен образац који користи СхареПоинт објектни модел и / или веб сервисима СхареПоинт листама искористи док пружа веома брз кориснички интерфејс.

Последња опција може да се осећате као да почињете од нуле, али у обзир чињеницу да је СхареПоинт платформа вам се полази од следећих кључних карактеристика:

• Безбедност модел са одржавањем.
• Мени систем са одржавањем.
• "Master table" (и.е. Прилагођене листе) са обезбеђењем, уграђене одржавање и ревизија.
• Претражи.
• Назад крај алата интеграције (БДД).

Ако почнете са новом празном пројекта у Висуал Студио, имате пуно инфраструктуре и водовод за изградњу пре него што дођете близу оно СхареПоинт нуди.

I do believe that Microsoft intends to extend SharePoint in this direction of application development. It seems like a natural extension to the existing SharePoint base. Microsoft’s CRM application provides a great deal of extensibility of the types needed to support header/detail application development. Although those features are in CRM, the technology is obviously available to the SharePoint development team and I expect that it will make its way into the SharePoint product by end of 2008. If anyone has an knowledge or insight into this, оставите коментар.

</крај>