View Complete Post
I need to import 700 Word docs (2003 & 2007) from Windows Server 2003 into a SharePoint Server 2010 library. I only have a test server to work with right now and want to do as much pre-work before we launch the actual
My goal: When we launch the shpt server, import all docs into a library so that columns propagate with metatdata automatically.
I'm not sure what the best approach is...
Can I can open each doc and add custom properties (maybe with InfoPath) to import as metadata, then import managed metadata through the term store tool and have it associate with the manually entered custom properties? I don't fully understand
managed metadata, which might pose a problem. And before I start importing terms, I thought I should find out if I've completely misunderstood how taxonomies work.
Or I have an excel spreadsheet with info about each doc in columns that can act as metadata. I could upload this as a list then associate each doc with the list. But it seems wiser to enter the metadata into the documets.
Is it possible to update my docs in advance so that uploading goes smoothly? I have help now for data entry that I won't have later.
I have no resources to spend on tools, and have to figure out and build this&nbs
Sharepoint 2010 Upgrade Question - A customer is currently running sharepoint 2007 on a 64bit windows 2003 OS with SQL 2005 sp2, they are looking to install/upgrade to Sharepoint 2010 and want to use the current SQL server,for the upgrade a new SharePoint
2010 environment will be built and for a short while they will have two instances of SharePoint running SP2007 and SP2010. The plan is to then manually migrate the data from SP2007 to SP2010 (ENT), the web and application servers will be newly built. From
research I think they have three options
1) Upgrade the current SQL 2005(SP2) instance to SQL 2008 R2 standard.
2) Install a new instance of SQL 2008 R2 on the same server and have both SQL 2005 & SQL 2008 running on the same server (Is this an option? Will sharepoint happily run from a SQL server running two SQL instances, do I have to be
careful regarding the installation and configuration, could I break the existing sharepoint farm doing this?)
3) Upgrade the current SQL server to SP3 and install a new instance of SQL 2005 SP3 and install SharePoint 2010 Enterprise here, again I have all the questions from point 2 above.
We are thinking of trying option 1, then 2, then 3, and obviously only moving to the next option if we come across a show stopper. H
Office 2010 and SharePoint 2010 include a new set of components called Application Services. These put a rich set of tools in a developer's bag for Office automation. We'll show you how to use Office OpenXML, Word Automation Services and SharePoint to build a simple application that merges separate status reports into a single document.
Manvir Singh, Ankush Bhatia
MSDN Magazine July 2010
The knowledge worker is greatly empowered if she is able to access information across the enterprise from a central access point. With the SharePoint Portal Server 2001 Search Service you can catalogue information stored in Exchange public folders, on the Web, in the file system, and even in Lotus Notes databases. This article discusses the use of ActiveX Data Objects and the Web-based Distributed Authoring and Versioning protocol for creating search solutions based on SharePoint Portal Server 2001.
MSDN Magazine April 2002