Automatic Content Organizer
Routes documents to appropriate place in SharePoint. End users don’t even have to be aware of SharePoint and think which document library this document should go into! Now they just work in word or office and SharePoint moves documents that were submitted by users to appropriate place.
- At the same time users can be more specific about tagging by means of tagging with taxonomy and view suggestions for taxonomy based on:
- Rules for content rerouting
- Content Types
- Property based conditions
- (Can apply multiple rules )
Documents are identified by their respective document IDs. With custom setup for ID mapping, ex: you can specify that document IDs in a library can be mapped to "HR_Policies_2009_XXXXX. At the same time if needed existing documents IDs can be reset to specific ID schema.
Folders are being looked at as means of security and retention policies granularity. Nested folders can either inherit policies from parent or have their own.
Retention policy consists of retention stages. There can be multiple stages set up for policy, stages that can fire off after specified period of time, ex: after 90 days move document somewhere, then after a year another stage might delete the document.
- auto complete from managed term set
- managed term sets are taxonomy
- taxonomy is geared towards foxonomy
- terms sets can be managed by individuals or by owners of the part of the taxonomy
- Central taxonomy
- Create your own taxonomies
- Taxonomy structure tree view
- Taxonomy store (centralized service)
- Taxonomy term store
- Multi language support for taxonomies
Folder like structure for grouping multiple documents together with advanced capabilities, almost like folder with special meaning...
- Provision multiple content type docs in one doc set
- Add Web Parts on the landing page of the doc set, ex: description or instructions, or even dashboard
- Automate repetitive content creation – EX: response to RFP
- Allows consistency and process insight
- Foundation for document assembly