Essential SharePoint 2007, 2nd Edition

Creating Library Applications

So far, this chapter has talked about how you do things with libraries but has said very little about what you can do with them. One reason for that is kind of obvious: libraries are for storing documents. But the real reason is because libraries are usually closely associated with the sites that contain them. It's hard to talk about a library application without using examples based on site templates.

So, let's forget that this is Chapter 5 for a moment and look at some of the site templates that create library applications. The four main types of library applications are listed in Table 5-4.

Table 5-4. Library application types

Application type	Site template	Core needs
Project	Team Site	Organized by project Keep version history Multiple authors, editors, reviewers Only team members have access
Task	Custom	Organized by type (template) Grouped by client or case Multiple authors, editors, reviewers Department has access
Document control	Document Center (MOSS)	Single location Track versions Formal process (workflow) Approve/reject submissions Single (or few) authors Revisions occur offline Everyone can read
Archive	Records Center (MOSS)	Central location for final documents Once stored, can't be changed Track status of submissions Controlled access

The application types listed in Table 5-4 are the types I see over and over again with clients. Really, I've just sorted common client needs into four groups and picked the site template that most closely matches those needs.

Project ...