Skip to main content

Co-authoring in SharePoint Server 2010

Image
By
Co-authoring in SharePoint Server 2010 addresses these issues by making it possible for multiple users to work on a document, at any time, without interfering with each other's changes. This approach streamlines many common document-collaboration scenarios. For example:
  • Two or more authors are working on different parts of a composite document. While one author works on his section of the document, another author can work on hers, without either interrupting their work.
  • Several authors are working on a composite slide show. Each author can add slides to the presentation and edit them, instead of working in isolation and trying to merge several documents and make them consistent all at the same time.
  • A document is sent out to several experts and stakeholders, each of whom has some edits or additions. No user’s edits are lost, because they are all working on a central, server-stored document.
Microsoft Defination

Co-authoring Office 2010 and Office Web Apps products: Several Office 2010 and Office Web Apps products enable multiple authors to edit documents at the same time
  • Word 2010
  • PowerPoint 2010
  • Excel Web App
  • OneNote 2010
  • OneNote Web App
Co-authoring and the checking out of documents (Microsoft)

Co-authoring is not compatible with the process of checking out and checking in documents in a library. Checking out a document means you want to exclusively write to it, and then eventually check it back in so others can see the changes or do further work on the document. Therefore, when you check out a file, other users cannot co-author the document with you. By default libraries do not require checking out files, and should not be enabled where co-authoring will be used. You should also not explicitly check out a document if you want to co-author the document.
Software Version Requirements

For users to co-author documents by using Office 2010, those documents must be stored in SharePoint Server 2010 or SharePoint Foundation 2010. To take advantage of the co-authoring functionality, users must have Word 2010, PowerPoint 2010, or OneNote 2010.

Co-authoring test cases : User A and User B working on the same document.

Following are the test cases

Test Case
Condition
Result
1
1. User A checks out first.
2. User B tries to check out the same doc
B was unable to check out and got a message indicating that A already checked it out.
2
1. User A opens the doc directly without specifically checking out.
2. User B tries to check out.
B had the option to check out and overwrite A's change. However, when B chose to do it he was unable to check back in. In the meantime, A was not able to check in from her side.
B Unable to check out. Because document is locked.
3
1.  User A opens the doc without checking out.
2. User B opens the doc without checking out. 
User B is not allowed to edit the Document. It is locked Exclusive to the User A.
4
1. User A checks out first.
2. User B opens the doc without checking out. 
User B is not allowed to edit the Document. It is locked Exclusive to the User A.




Test Case 1:User B Unable to check out. The document already checked out or locked for editing by another user



Test Case 2:
User B Unable to check out. Because document is locked for shared use by “User A”.



Test Case 3:User B is not allowed to edit the Document. It is locked Exclusive to the User A.



Test Case 4:User B is not allowed to edit the Document. It is locked Exclusive to the User A.


Some of contents taken from the following articles.

Configure versioning for co-authoring (SharePoint Server 2010)

Configure the co-authoring versioning period (SharePoint Server 2010)

Configure the maximum number of co-authoring authors (SharePoint Server 2010)

Disable co-authoring (SharePoint Server 2010)
Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

By
What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...
1 comment
Read more

SharePoint 2013 Search Database Part 1

By
SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...
Post a Comment
Read more

STS CryptographicException Error : Key set does not exist

By
Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis
Post a Comment
Read more