Microsoft Office Tutorials and References
In Depth Information
a document workspace subsite. This kind of list is meant to integrate with Office, because
the templates associated with library list items are mostly Office templates such as Word,
Excel, PowerPoint, or even InfoPath. In addition, like any list, a document library can also be
opened in Access, exported to Excel (well, the metadata anyway), and connected to Outlook.
Form Library This type of library requires Microsoft Office InfoPath, preferably InfoPath
2007 or newer. InfoPath is a program that creates forms for users to ill out. More specifically,
it lets you design your own form templates; when a user opens the template, it creates a form
instance which allows the user to ill the form with data. InfoPath 2010 comes in two flavors, ,
InfoPath Designer and InfoPath Filler. You design and publish InfoPath forms to a forms
library using InfoPath Designer, and the users can ill out the form using InfoPath Filler.
InfoPath files are XML files, and they require InfoPath to be installed locally on the machine
from which you will be using the library. This type of library is useful for companies that
process vacation requests, purchase orders, and other kinds of InfoPath forms that need to be
filled out by the users. Because InfoPath forms are based on templates, if you move a file from
one form library to another, you’ll need to relink it to its template.
Picture Library This type of library is intended to store images that you can access
elsewhere on the site; each image file is given a direct URL that can be referred to in an image
web part or hyperlink field of a list item (such as an item in a Contacts list). You may have
noticed that images aren’t inserted into fields of web parts (such as the Content Editor) or
RSS pages; instead, these features all refer to an image’s location and display the image from
there. No embedding is necessary. Image files in a picture library are stored in the content
database, so they are convenient to the entire site and are backed up when the content
databases are backed up. A picture library uses the Picture Manager that is installed with Office
(preferably 2010, but 2007 and 2003 have one, too) to edit images and add multiple images to
the library. A user who does not have an Office product installed will only be able to upload
one picture at a time to the library. The picture library also has several unique views, and
this version of SharePoint even has a picture library slide show web part, if you would like to
add a slide show from one of your picture libraries to a page (the web part takes a lot of
processor power for the client viewing it, though).
Wiki Library This type of library is basically a document library of HTML files that
support the wiki syntax when linking to other files in the same library. This library is unique
insofar as it displays the contents of the wiki file called Home instead of displaying its
contents in a list on its content page. To access the actual content page for the library, you can
click the library’s link in the content breadcrumb. A wiki library has versioning enabled by
default, and it does not allow content types. Unlike the other library types, it does not
support Open with Explore, so you cannot drag and drop multiple files into the library. Wiki
libraries have no means to upload existing pages.
Creating a library is easy, but before you create one, you need to do some planning first. You
should ask yourself these questions:
Is there a maximum file size you want to allow on SharePoint sites? The default is 50 MB.
Are there any types of files you do not want to be uploaded to a library? Some file types are
helpfully blocked by default in Central Administration. You may want to block different
files or unblock the defaults. This setting applies per web application, so you need to keep
it in mind when planning for document libraries.