Please enter the product folder in the distribution zip-file, run the installer (*.exe) and install or upgrade the product following the steps. Use the "Run as Admin
" option of the context menu (right click).
After sucessfull installation please activate the timer job that runs the Auto Tagger in Central Administration > Manage Farm Features as a Farm Administrator. Please re-schedule if required:
Fig.: The Auto Tagger Timer Job runs as a Farm Feature.
Please also activate the Auto Tagger feature on site collection
level as a site collection
Fig.: How to activate auto-tagging in Microsoft SharePoint 2010 for taxonomy-based background content categorization.
The "Auto Tagger" feature generally activates background content categorization for the current site collection and creates the following lists (if not exists):
"Auto Tagger Configuration List" to define configuration items (jobs) to run at a specific time
"Auto Tagger Scope List" to define scopes for certain configuration items (jobs), e.g. to include or exclude specific web sites, lists / libraries, columns or content types with tagging.
Please use these lists to setup more advanced options manually. By default no items or documents are in any scope of the Auto Tagger to avoid unwanted data modification.
Fig.: Sample Auto Tagger Configuration List item to re-tag the scope every 24 hours. Please note, that the TargetUid column is no longer available starting with version 1.7.
You can use any title you want to describe your configuration item.
No longer used. The target is defined in the scopes list since version 1.7
Set the run interval in hours here. By default this is set to 24h. Please make sure that the Auto Tagger Timer Job setting is shorter compared to your interval settings. The timer job takes a look at this list to execute certain entries, if required.
Setting the overwrite flag to true (enabled) causes a complete new tagging for each item or document of the target area, which overwrite all previously given tags. By default the overwrite flag is set to false (disabled). In this way manually given tags are kept by default. The auto tagger by default only adds new and additional tags to the item or document.
This entry is automatically written by the timer service to report the last run date and time.
This entry is automatically written by the timer service to set the next run date and time. You can overwrite this, to enforce executing.
This entry is automatically written by the timer service to report the duration of the last execution of this entry (in seconds). Please make sure, that the duration is significantly shorter than your given interval.
This entry is automatically written by the timer service to report the number of tags given to items and documents with the last execution.
This entry is automatically written by the timer service to report the number of Items and documents tagged with the last execution.
This entry is automatically written by the timer service to report the number of warnings in the last execution. See SharePoint Log for more detailed information.
This entry is automatically written by the timer service to report the number of errors in the last execution. See SharePoint Log for more detailed information.
Last Error Message
This entry is automatically written by the timer service to report the last error message. This entry should be blank, if no errors occurred. See SharePoint Log for more detailed information in case of errors.
Use System Update
By default "System Update" is used to modify the item or document entry with tags by the auto tagger. That means, the "Last Modified" date/time and user is not changed by auto tagger. No workflows, offline replications etc. are started on item or document change by auto tagger. If disabling this entry, normal update is used. The "Last Modified" information is changed and e.g. workflows and offline replications are started on item / document change (if defined).
Please describe your configuration item here.
The program version installed is listed here for debug and support.
log.txt contains all log information of the last run. It is replaced with the next run.
The scopes are defined in the "Knowledge Managament Suite AutoTagger Scopes List":
Fig.: Sample scope antry that excludes a specific column from auto tagging.
Use the item title to describe your scope.
Reference a configuration item here with lookup.
Website, List, Column, Content Type
You can include or exclude any Web Site, List, Column or Content Type here.
For example you can create one entity that includes all (using *) and another entry that excludes some elements. Alternatively you can include some specific elements only. In case of using Content Types you can include / exclude inherited content types of e.g. myContentType using myContentType*.
If enabled, the elements are included in tagging, otherwise excluded.
Please describe the scope for others to understand your entry.