Content Manager for SharePoint 2010 (organizer)

If we use a SharePoint site to store departmental/team documents, we usually build the appropriate document libraries and folders in the site in advance, according to the structure we want. For example, we will create a "technical document library", to hold documents for the technical category while creating a business document library that holds business categories of documents, and in the Technical document library, you may also create folders such as "CSharp", "C + +", "Java", and so on, in terms of the type of programming language. Place the technical documents in the appropriate folder, according to the categories they belong to.

However, no matter how well and intact the administrator builds the structure, it is likely that users will not upload documents to the correct document libraries and folders according to the actual category of the document. The Content manager for SharePoint 2010 helps site administrators automate document routing and storage. After a user uploads a document to a Web site, the content manager of the Web site automatically moves the document to the correct location according to the rules that you set beforehand.

The rules of the Content manager are basically based on two conditions of judgment:

1, the content type of the document. For example, files that belong to the technical document content type, where they move, and files that belong to the business document content type, are moved to where. Content Manager rules can only handle content types that are inherited from the document content type, which means that content managers can manage only the contents of file types, not other list item content types.

2, the value of the property. Based on the 1th judgment condition, the administrator can also set the judgment condition based on the document's properties. For example, the value of the technology category attribute equals the document for Web program, and where to move to. The 2nd judgment condition cannot exist independently of the 1th.

Content Manager is a site-level feature, not a site collection level. So, first of all, you need to enable the Content Manager feature in Web Site feature management:

After the Content Manager feature is enabled in the Web site, a drop library document library is included in the site. This "Drop Library" is one of the core Content manager, in fact, all content Manager rules are applied to the drop library.

And then in the Site Administration page, you'll get more out of the Content Manager settings and Content Manager rules link:

The Content Manager Settings interface is a global setting for the Content Manager feature of the entire Web site.

If the submit new content to library option is selected, the document is automatically moved to the drop library to apply the rule, regardless of where the user uploads the document to the site. But I found that there seemed to be bugs in Beta2, and even if the administrator checked this option, documents uploaded to other places by the user would not automatically be moved to the "drop library" so that the rules would be applied only to documents uploaded to the drop library.

If you select the Allow rules to designate other sites as the destination option, you can move the uploaded document to another site in the rule. However, the target location of other sites must be previously available to the administrator after the Central administration-general application settings-Configure Send to connection setting.

The option to automatically create subfolders is useful so that you can avoid storing too much content in one folder. It is not recommended to store more than 5,000 files in one folder.

If a file with the same name already exists in the target location, the following options determine how the content Manager handles the situation. However, if the administrator chooses to use version control, but the target document library does not have versioning enabled, the content manager is still using the method of automatically adding a unique character after the filename.

Keeping the audit logs and attributes of a document helps to keep the document in record management.

Rule Manager allows administrators to specify who can set content manager rules. If a user is a site administrator, but is not a rule administrator, he or she cannot manage the Content manager rules. If a user is a rule administrator, but is not a webmaster, he still cannot manage the Content manager rules.

The next step is to create a rule for the content manager. Each rule has a priority, and a high priority rule is executed first so that if a document meets the conditions of multiple rules, only the highest precedence rule is applied to the document.