16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 19: Working with Documents in SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> 541<br />

Check-In/Check-Out Processes<br />

<strong>Microsoft</strong> Windows SharePoint Services gives users the ability to keep versions of<br />

documents <strong>and</strong> to check documents in <strong>and</strong> out.<br />

About Document Versioning<br />

!<br />

Document versioning allows you to keep multiple versions of a document. This<br />

functionality is not enabled by default. By enabling document versioning, if a<br />

change needs to be reversed, you can restore the previous version <strong>and</strong> continue<br />

working. A Version History comm<strong>and</strong> is included on the drop-down list users see<br />

when they click the arrow next to a document name <strong>and</strong> on the toolbar in the Edit<br />

Properties or View Properties page for the document. The Version History comm<strong>and</strong><br />

is also available in client applications compatible with Windows SharePoint Services,<br />

such as <strong>Microsoft</strong> Office Word 2003, <strong>Microsoft</strong> Office Excel 2003, <strong>and</strong> <strong>Microsoft</strong><br />

Office PowerPoint 2003. When the user clicks Version History, a list of the previous<br />

versions of the document appears. The user can open an old version, restore a version<br />

(replacing the current version), or delete an old version.<br />

Important When a file is deleted from a library, all previous versions are<br />

deleted as well.<br />

Versions can be created for all file types except HTML files that contain<br />

images or embedded objects. If you want to create versions as HTML,<br />

you must use the archive, or thicket, MHTML format (often saved as .mht)<br />

when saving to this website. This restriction applies to other compound documents.<br />

Although you can save several versions of a compound document—say,<br />

a <strong>Microsoft</strong> Word document with a link to a <strong>Microsoft</strong> Excel<br />

spreadsheet held within a document library—the link within the <strong>Microsoft</strong><br />

Word document will always point to the most recent version of the Excel<br />

spreadsheet <strong>and</strong> not to the version of the spreadsheet that matched the<br />

version of the Word document at time of creation. If you want to match information<br />

from several sources at a particular instance, you need to include<br />

the content within one document <strong>and</strong> not link to it. In SharePoint Server<br />

2001, compound documents were supported only in st<strong>and</strong>ard folders.<br />

By default, picture <strong>and</strong> document versioning is turned off for the document<br />

libraries that are created for each portal site area, Topic, <strong>and</strong> SharePoint site. You can<br />

enable <strong>and</strong> disable versioning once a document library is created. When you create<br />

a new library, you have the option of turning on versioning. This means that you<br />

can turn on versioning for libraries that store important information <strong>and</strong> turn off this<br />

feature for libraries that don’t need versioning.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!