FIELD
- Last Updated: October 30, 2026
- 2 minute read
- Semaphore
- Documentation
Restricts the text search to the named field only
For general office documents fields have a very simple meaning - the “body” field is the text of the document - all other fields come from the meta information for the file. The name of the fields depends upon the file type that is processed (and what meta information was included with the file).
When Classification Server is invoked from a Content Management System or a similar type of editorial system fields can be used to pass some of the CMS information to Classification Server. See for instance the SharePoint metadata passed to Classification Server.
/docs/integrations/semaphore_for_sharepoint_2013_-_administration_guide/appendix_-_reference_information#information_passed_to_classification_server
Multiple fields can be specified at once using a boolean OR noted as |. For instance “A|B” will find data in field A or field B.
Fields can be expressed as XPATH, this allows to specifically target a sub-field, this is particularly useful for titles for instance as the following are defined:
- title/document_title - The actual title of the document
- title/article_title - The title of the current article
- title/original_title - The original document title if it was overwritten by a title specified by the request
This way field=“title” will search all of these titles but field=“title/article_title” will search that specific title sub-field only.
There are two special fields which are not aligned to incoming metadata:
- “HeaderFooter”: containing any text in a header or footer for the document - note this is a sibling field to body so body restricted searches will not find any data in headerfooter
- “Emphasised”: any text that is bold/italic or underlined in the original document will be marked as belonging to a child field called “emphasised” - since this is a child field a “body” restricted rule will still search this text
Field is an inherited attribute - ie it may be set on a containing rule and will be the default for all child rules; therefore field is a valid attribute for all rules - However only has functionality for text rules.
- Author
- CreationDate
- Creator
- Producer
- Title
- WordFinder Version
- Number Of Pages
Fields extraction from Office documents
Type
Document Comment
Keyword
Last Saved By
Author
Subject
Title
Abstract
Account
Address
Application Version
Attachments
Authorization
Backup Date
Bill To
Blind Copy
Carbon Copy
Category
Checked By
Client
Completed Date
Character Count
Page Count
Word Count
Creation Date
Department
Destination
Disposition
Division
Minutes Edited
Editor
Forward To
Group
Language
Last Print Date
Mail Stop
Matter
Office
Operator
Owner
Project
Publisher
Purpose
Received From
Recorded By
Recorded Date
Reference
Revision Date
Revision Notes
Revision Number
Secondary Author
Section
Security
Source
Status
Document Type
Typist
Version Date
Version Notes
Version Number
Base File Location
Manager
Company
Last Saved Date
Presentation Format
Count Bytes
Count Lines
Count Paragraphs
Count Slides
Count Slides Hidden
Count Notes
Count MM Clips
Count Characters with Spaces
Scale Crop
Links Dirty
Title of Parts
Heading Pairs
Document Number
User defined fields
- META_### where ### is specific property num in document (This is for user defined meta data)
Applies to
Values
- “FIELD_NAME”