Title Page
EMC® Kazeon-eDiscovery
Version 4.8.0
IS1200 Metadata Reference Guide
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright © 2007 - 2015 EMC Corporation. All rights reserved.
Published September 2015
EMC believes the information in this publication is accurate as of its publication date. The information is subject to
change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. Adobe and
Adobe PDF Library are trademarks or registered trademarks of Adobe Systems Inc. in the U.S. and other countries. All
other trademarks used herein are the property of their respective owners.
The IS1200 software is based in part on software licenses from the following:
Outside In® Content Access © 1991-2015, Chicago, Inc.
Open Source code from www.java2s.com called the itext.asian.jar available at:
http://www.java2s.com/Code/Jar/GHI/itext-asian.jar.htm
Copyright 2009 - 12 Demo Source and Support. All rights reserved
In part on the work of the Independent JPEG Group.
Code from Inxight Software, Inc. Copyright © 1996-2015. All rights reserved. www.inxight.com.
Certain icons used by the Kazeon Web applications come from the Silk Icon set
(http://www.famfamfam.com/lab/icons/silk/)
licensed under the Creative Commons Attribution 2.5 license
(http://creativecommons.org/licenses/by/2.5/).
ii
IS1200 Metadata Reference Guide— v4.8.0
Contents
Preface ............................................................... ......................................vii
Chapter 1
The Metadata Schema and Tag Management
What is Metadata? .............................................................................. 2
About the Metadata Schema ............................................................. 4
The fulltext Metadata Field ......................................................... 4
Default Metadata Schema Fields ................................................ 5
Viewing the Metadata Schema ................................................... 7
How Tags Are Defined in Metadata Schema.................................. 7
Metadata Tag Attributes.............................................................. 7
Metadata Tag Types ...................................................................10
Date Format Requirements .......................................................10
Fully Qualified Tag Names .......................................................11
Metadata Tag Namespaces .......................................................11
Using ‘set schema’ to Add Tags to the Metadata Schema........... 15
Deleting a Field from the Metadata Schema...........................16
Other CLI Commands for Tag Maintenance................................. 16
Creating New Namespaces .......................................................16
Editing Tags.................................................................................16
Un-hiding Tags ...........................................................................17
Listing Name Spaces ..................................................................17
Listing Tags in a Specific Name Space ....................................17
Listing the Indexed Tags in a Name Space .............................17
Listing the Details of a Specific Fully Qualified Tag .............18
Synchronizing Tag Management with Database ...................18
Best Practices ..................................................................................... 18
Customizing the Metadata Schema for Web-Search Preview .... 19
Customizing the Search Schema for DICOM Data ...................... 19
IS1200 Metadata Reference Guide— v4.8.0
iii
Contents
Chapter 2
The Default Schema and Metadata Tags
How Metadata Tags and Namespaces are Organized ................ 22
Namespace Tables Legend .............................................................. 23
System Default Namespaces ........................................................... 24
Calendar Namespace ................................................................. 24
Contact Namespace.................................................................... 25
CTA Namespace ......................................................................... 27
Detected Namespace.................................................................. 28
DICOM Namespace ................................................................... 28
Digest Namespace ...................................................................... 29
Directory Namespace................................................................. 29
Document Namespace............................................................... 30
EnvCommon Namespace.......................................................... 33
Hierarchy Namespace ............................................................... 35
InheritedMail Namespace ......................................................... 36
IPTC Namespace ........................................................................ 38
Kazcollection Namespace.......................................................... 39
Kazeon Namespace .................................................................... 40
Legalapp Namespace................................................................. 41
Legal Namespace........................................................................ 42
LegalExport Namespace............................................................ 44
MailDerived Namespace........................................................... 45
Mail Namespace ......................................................................... 46
MDB Namespace ........................................................................ 52
Objcommon Namespace............................................................ 52
OriginalSource Namespace....................................................... 53
Persistentnamespace Namespace............................................. 53
Processingservice Namespace .................................................. 54
Retention Namespace ................................................................ 54
System Namespace..................................................................... 56
Systemusertags Namespace...................................................... 58
Task Namespace ......................................................................... 58
Tiff Namespace ........................................................................... 60
Userdefined Namespace............................................................ 62
Userextracted Namespace......................................................... 63
Version Namespace.................................................................... 63
Namespaces Populated by Rulesets .............................................. 64
Amex Namespace....................................................................... 65
Centera Namespace.................................................................... 65
DinersClub Namespace ............................................................. 66
Discover Namespace.................................................................. 66
EIN Namespace .......................................................................... 67
Entity Namespace....................................................................... 67
iv
IS1200 Metadata Reference Guide— v4.8.0
Contents
GLBA Namespace.......................................................................70
ITIN Namespace .........................................................................72
JCB Namespace ...........................................................................72
Master Namespace......................................................................73
NIN Namespace ..........................................................................73
NPI Namespace...........................................................................74
PCI Namespace ...........................................................................75
SIN Namespace ...........................................................................77
SSNCC Namespace.....................................................................77
SSN Namespace ..........................................................................78
Visa Namespace ..........................................................................78
Namespaces Populated by Optional Module Connectors .......... 79
Atmoscloud Namespace ............................................................80
Centera Namespace ....................................................................80
CSVC Documentum Namespace..............................................81
CSVC SharePoint Namespace ...................................................85
Directory Namespace .................................................................87
Domino Namespace ...................................................................87
Dumpster Namespace ................................................................88
EnterpriseVault Namespace......................................................88
Exchange Namespace.................................................................90
NSF Namespace ..........................................................................90
Sourceonearchive Namespace ..................................................91
Alphabetic Listing of Indexed Default Metadata Tags: ............... 92
Chapter 3
Metadata Mapping
Background ........................................................................................ 96
Creating a Mapping File to Capture OMR Custom Attributes .. 97
Identifying the OMR Custom Attributes.................................97
Identifying and Creating the IS1200 Metadata Tags to Map
To...................................................................................................97
Obtaining the Mapping Template from the IS1200 ...............98
Editing and Saving the Mapping File ......................................98
Mapping File Naming and Syntax ...........................................99
Default Connector Metadata Mappings ...................................... 101
NFS Default Metadata Mappings...........................................102
CIFS Default Metadata Mappings ..........................................103
Centera Default Metadata Mappings.....................................104
Enterprise Vault (EV) Default Metadata Mappings ............106
SharePoint Default Metadata Mappings ...............................108
Documentum Default Metadata Mappings ..........................110
IS1200 Metadata Reference Guide— v4.8.0
v
Contents
Chapter 4
Legal Export Default Tags
Legal Export Tags Default profile................................................. 116
Post Legal Export Tagging for Rolling Exports .......................... 118
Rolling Export Metadata Tags ................................................ 118
Appendix A
NSF Metadata Tags
How NSF Metadata is Mapped to IS1200 Tags .......................... 120
Appendix B
Using DICOM Tags
Using DICOM File Attributes as Metadata................................. 124
Enabling DICOM File Recognition ........................................ 124
Selecting the DICOM Properties to Extract .......................... 125
Adding DICOM File Attributes to the Search Schema ....... 125
DICOM Properties That Can Be Extracted As Extended
Attributes ......................................................................................... 126
Glossary ........................................................... ......................................147
vi
IS1200 Metadata Reference Guide— v4.8.0
Preface
As part of an effort to improve its product lines, EMC periodically releases
revisions of its software and hardware. Therefore, some functions described
in this document may not be supported by all versions of the software or
hardware currently in use.The product release notes provide the most
up-to-date information on product features.
Contact your EMC technical support professional if a product does not
function properly or does not function as described in this document.
Note: This document was accurate at publication time. Go to EMC Online
Support (https://support.emc.com) to ensure that you are using the latest
version of this document.
Audience
Related
Documentation
This is a reference guide for advanced users, such as IS1200
administrators, that need detailed information about the metadata
fields in the IS1200 Metadata Schema, how to map files between the
IS1200 and repositories accessed through optional modules (such as
Microsoft Exchange servers), what metadata fields are exported
through the Legal Export function, and other information about
using IS1200 metadata.
IS1200 Installation and Quickstart Guide
- describes installing and configuring the IS1200 server software.
IS1200 Web-Admin User and Configuration Guide
- describes using Web-Admin to setup and manage Kazeon clusters.
IS1200 Web-Search User Guide
- describes using Web-Search to perform basic and advanced searches.
IS1200 Metadata Reference Guide— v4.8.0
vii
IS1200 Web-Reports User Guide
- describes using Web-Reports to create and use basic and advanced reports.
IS1200 eDiscovery Case Manager Administrators and Supervisors Guide
- for legal representatives, a primer of all the web-based Interfaces
above for performing eDiscovery.
IS1200 Command Line Interface Reference Guide
- describes the IS1200 Command Line Interface and all its commands.
Follow these steps to download IS1200 document from the web:
1. Go to https://support.emc.com and click the SUPPORT BY
PRODUCT option in the home page.
2. In the Find a Product field, enter Kazeon. From the product
selection list, choose one of the sub-headers (such as Kazeon
ECS) and click the Find button.
3. Kazeon ECS window is displayed. Click the link for
Documentation.
4. In the left-navigation menu, choose a version level to display the
available documents.
Conventions used in
this document
EMC uses the following conventions for special notices:
DANGER indicates a hazardous situation which, if not avoided, will
result in death or serious injury.
WARNING indicates a hazardous situation which, if not avoided,
could result in death or serious injury.
CAUTION, used with the safety alert symbol, indicates a hazardous
situation which, if not avoided, could result in minor or moderate injury.
NOTICE is used to address practices not related to personal injury.
viii
IS1200 Metadata Reference Guide— v4.8.0
Note: A note presents information that is important, but not hazard-related.
IMPORTANT
An important notice contains information essential to software or
hardware operation.
Typographical conventions
EMC uses the following type style conventions in this document.
Normal
Used in running (nonprocedural) text for:
• Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus)
• Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords,
clauses, environment variables, functions, utilities
• URLs, pathnames, filenames, directory names, computer names, filenames, links, groups, service
keys, file systems, notifications
Bold
Used in running (nonprocedural) text for:
• Names of commands, daemons, options, programs, processes, services, applications, utilities,
kernels, notifications, system calls, man pages
Used in procedures for:
• Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus)
• What user specifically selects, clicks, presses, or types
Italic
Used in all text (including procedures) for:
• Full titles of publications referenced in text
• Emphasis (for example a new term)
• Variables
Courier
Used for:
• System output, such as an error message or script
• URLs, complete paths, filenames, prompts, and syntax when shown outside of running text
Courier bold
Used for:
• Specific user input (such as commands)
Courier italic
Used in procedures for:
• Variables on command line
• User input variables
<>
Angle brackets enclose parameter or variable values supplied by the user
[]
Square brackets enclose optional values
|
Vertical bar indicates alternate selections - the bar means “or”
{}
Braces indicate content that you must specify (that is, x or y or z)
...
Ellipses indicate nonessential information omitted from the example
IS1200 Metadata Reference Guide— v4.8.0
ix
Where to get help
EMC support, product, and licensing information can be obtained as
follows.
EMC product, and licensing information can be obtained as follows.
Product information — For documentation, release notes, software
updates, or for information about EMC products, licensing, and
service, go to the EMC Online Support at:
https://support.emc.com
Technical Support — Go to EMC Online Support and click Service
Center. You will see several options for contacting EMC Technical
Support. Note that to open a service request, you must have a valid
support agreement. Contact your EMC sales representative for details
about obtaining a valid support agreement or with questions about
your account.
Documentation
Feedback
Your suggestions help us continue to improve the accuracy,
organization, and overall quality of the user publications. Please send
your comments or opinions on this document to:
ECD.Documentation.Feedback@emc.com
Revision History
Table 1
x
Revision History Details
Revision Date
Description
September 2015
Updated the Deduplication section in “Glossary”
December 2013
Initial Publication
IS1200 Metadata Reference Guide— v4.8.0
1
The Metadata Schema and Tag Management
This chapter discusses metadata tag creation and management using
the Command Line Interface (CLI) to edit the metadata schema,
originally called the Kaz Schema. Most tag management tasks can
only be performed from the CLI. See the
IS1200 Command Line Interface Reference Guide for complete
descriptions of the CLI commands described here.
Topics include:
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
◆
What is Metadata? ............................................................................... 2
About the Metadata Schema .............................................................. 4
The fulltext Metadata Field ................................................................ 4
Default Metadata Schema Fields ....................................................... 5
Viewing the Metadata Schema........................................................... 7
How Tags Are Defined in Metadata Schema ................................... 7
Metadata Tag Namespaces ............................................................... 11
Using ‘set schema’ to Add Tags to the Metadata Schema............ 15
Other CLI Commands for Tag Maintenance.................................. 16
Best Practices....................................................................................... 18
Customizing the Metadata Schema for Web-Search Preview ..... 19
Customizing the Search Schema for DICOM Data ....................... 19
The Metadata Schema and Tag Management
1
The Metadata Schema and Tag Management
What is Metadata?
Data is information recorded in files on data repositories (file servers).
Metadata is data that describes data. Generally, metadata refers to the
information that describes the file, or is contained in the file.
File type, file path, and creation date, as well as any textual content
found in a file, are all examples of metadata. IS1200 classifications
extract this metadata and store it in centrally located metadata
repositories to allow comprehensive searches of all your registered
repositories from one place.
You can also use metadata to group files and to assign them to policy
groups. See the About Policies and Policy Groups chapter of
IS1200 Web-Admin User and Configuration Guide for complete details
on using Policies.
The IS1200 works with many types of metadata including; file system
or standard metadata; application-specific metadata; and fullText, custom,
or user-defined metadata.
File system metadata or standard metadata consists of standard file
attributes taken from data repository directories. It includes attributes
such as file type, file size, creation and modification dates, file path, etc.
These attributes are extracted from the file’s data repository directory
listing and are attributes all files have.
2
IS1200 Metadata Reference Guide— v4.8.0
The Metadata Schema and Tag Management
Application-specific metadata is information that is specific to certain
types of files. For example in an Microsoft Word document, the Properties
dialog shows application-specific standard-document properties such as
Title, Subject, and Author, and application-specific custom-document
properties such as Checked By.
Figure 1
Standard or Application Specific Metadata Examples
FullText metadata is probably the most commonly searched metadata
field. fullText is extracted from files with textual content, see
“fullText” on page 156 for more details. All words found in file text
content (except stop words, see “stop words” on page 166 for details)
are individually indexed and may be searched for as “keywords” in
basic and advanced searches.
Custom metadata or user-defined metadata, is also extracted and indexed
from file content, but it is indexed according to guidelines found in
extraction rules, see “Extraction Rules” on page 155 for more details.
For instance, custom metadata can be defined to identify all files
containing the word “confidential”. Custom metadata is also used to
identify files that contain patterns such as social security numbers,
drivers license numbers, or part numbers. Custom metadata search
expressions may contain boolean operators to specify multiple
parameters.
The Metadata Schema and Tag Management
3
The Metadata Schema and Tag Management
About the Metadata Schema
The Metadata Schema (originally called the Kaz Schema) defines the
set of metadata fields used to build a Search Index for registered data
repositories (file systems). The Search Index is built whenever a
classification is performed, and the information extracted is stored in
the Search Index. This allows the IS1200 to parse the Search Index for
search query terms rather than directly accessing the files on all
registered data repositories.
Basic classifications store standard metadata like file size; file name;
and file creation, modification, and access dates in the Search Index.
Deep classifications add even more information based on extractions
rules which define custom metadata to locate and index. Custom
metadata is defined by extraction rules that locate information like
social security numbers, part numbers, or key words like
“confidential” or “private”.
The fulltext Metadata Field
The custom metadata field called “fulltext” deserves special
attention. This field is defined and contained in an extraction rule
called “the fulltext rule” and this rule constitutes the default rule set
applied to new deep classifications when they are created. The
fulltext extraction rule looks at the body of a file (for example, the text
in the body of a word processing or email document) and indexes
each word in the document body in the Search Index and includes the
full textual content of the object in a metadata field called “fulltext”.
Simple searches, for example looking for a company name like
“ACME Inc.”, actually check the fulltext metadata field in the Search
Index for the string “ACME Inc.”.
Note: Fulltext does not necessarily index all the “text” in a file, so simply
searching for a string like “the acme project” will not return a file, like an
email, if the search string is not in the email’s body, even though the string is
contained in the email’s subject. Likewise, searching for an “author” named
“john smith” will not return a Word file authored by John Smith (and duly
recorded in the file’s directory attributes) unless the name “john smith” is
actually a part of the text body of the file.
HOWEVER, information in metadata fields like “author” and “mailsubject”
can be made part of the fulltext search index, and thus searchable with simple
keyword searches, by manually configuring the Search Index to include the
information from those metadata fields. See “Using ‘set schema’ to Add Tags
4
IS1200 Metadata Reference Guide— v4.8.0
The Metadata Schema and Tag Management
to the Metadata Schema” on page 15 for more details.
Fulltext is extracted separately for file objects and sub-objects. For
example for container objects such as ZIP, TAR, JAR, and PST or NSF
files, individual fulltext is extracted and indexed for the container
object (the parent) and each of it’s sub-objects (children).
It is important to note that files with embedded objects, for example
Microsoft Word files containing embedded OLE objects (spreadsheets
or graphics), are not considered to be container objects and
sub-objects. Consequently, the fulltext of embedded objects (for
example the text of an embedded spreadsheet) is extracted and
included in the fulltext of it’s parent object.
Default Metadata Schema Fields
The default Search Schema contains the following types of metadata
fields:
File system fields: These metadata fields consist of file properties
such as FileType and Owner extracted during basic classification.
Do not delete these.
Kazeon-configured fields: The IS1200 provides an extraction rule
set named sampleruleset that contains several pre-defined
extraction rules. The Metadata Schema contains metadata fields
added for these sample extraction rules to populate. These
metadata fields can be deleted if you choose to not use these
rules.
For more information on the sampleruleset, see the section Sample
Extraction Rule Set from the Policies: Classification, Extraction, and
Assignment Rules chapter of IS1200 Web-Admin
User and Configuration Guide.
Internal fields: The IS1200 uses internal metadata fields to
classify files and perform other operations. You cannot delete
these fields.
With the appropriate optional modules installed, the following are
available:
Centera fields: Centera-specific metadata is extracted during
basic classification.
Snapshot fields: These Snapshot-specific metadata fields are
extracted during basic classification.
The Metadata Schema and Tag Management
5
The Metadata Schema and Tag Management
SnapLock fields: These SnapLock-specific metadata fields are
extracted during basic classification.
Not all fields are populated because field values depend on file
contents and document type. For example, the Kazeon-defined field
called “Company” is a property of Microsoft Word files. So, the
system populates this field with values extracted from Microsoft
Office files. But PDF files do not contain a “Company” field, so the
system leaves “Company” unpopulated in that metadata field for pdf
files. You can use extraction rules to populate empty fields. For
information on extraction rules, see the section Using Extraction Rules
from the Policies: Classification, Extraction, and Assignment Rules
chapter of IS1200 Web-Admin User and Configuration Guide.
The Metadata Schema can be customized for any kind of meta field
needed. For information, see “Using ‘set schema’ to Add Tags to the
Metadata Schema” on page 15.
Note: When classifying PST files, the IS1200 maps the file type to “MS
Outlook Personal File Folder” and extracts the following metadata fields:
MailCc, MailFrom, MailTo, MailSubject. Add these fields to the Search index
to use them in search. For more information, see “Using ‘set schema’ to Add
Tags to the Metadata Schema” on page 15.
Typically, the Search schema is set only once, when the IS1200 is
originally configured. If a new keyword is added to the Search
schema later, the Search index must be rebuilt by doing a deep
classification to update the metadata fields. This ensures the index
contains the appropriate metadata to retrieve information from the
corresponding file systems.
Note: See “System Default Namespaces” on page 24 for the fields included in
the default search schema.
6
IS1200 Metadata Reference Guide— v4.8.0
The Metadata Schema and Tag Management
Viewing the Metadata Schema
To view the current contents of the Metadata Schema use the CLI
command:
show schema
The system responds:
Figure 2
CLI Command: show schema
How Tags Are Defined in Metadata Schema
The ‘set schema’ command adds new tags to the Metadata Schema.
Tags have a variety of parameters and attributes that must (or can) be
set when using this command. These parameters and attributes must
be understood before using the command.
Metadata Tag Attributes
The following types of attributes may be specified when issuing the
set schema command.
◆
attributes (space separated list)
◆
search-attributes (comma separated list)
◆
display-attributes (comma separated list)
◆
report-attributes (comma separated list)
◆
delimit-attributes (comma separated list)
Each is set using a specific CLI command keyword.
The set schema attribute keywords, and their usage, follows:
The Metadata Schema and Tag Management
7
The Metadata Schema and Tag Management
Table 2
8
Types of Attributes for ‘set_schema’ CLI Command
set schema keyword
Attribute Description
attributes
A list of one or more attributes separated by spaces within single quotes. If set schema is in
edit mode, new attributes are added to existing ones. Attributes include:
• Keep: The tag must be populated during classification and persists during IS100
software upgrades.
• Indexed: The tag must be populated in the search index
• Usertag: The tag is cumulative across classifications
• Multivalued: The tag can have a set of values
• Property: Extracted from a predefined property of the document type
• Alias: The tag is an alias of another tag, this attribute may not be used with any other
attribute.
Example:
set schema NewTag type string namespace foo attributes 'keep
indexed'
defines the fully qualified tag fooNewTag that is a string and has the attributes keep and
indexed.
search- attributes
A list of one or more attributes separated by commas within single quotes. These are
search-specific system configuration parameters. When set schema is used in edit mode,
new search-attributes are added to existing ones. Search-attributes include the following:
• Text: Specifies that the field contains full form text such as sentences, paragraphs and
long bodies of text.
• Kaztext: Specifies that Kazeon specific aggressive tokenization be used on the value of
the tag while indexing and search.
• String: Tag contains a complete string and can only be searched for as a complete
string.
• Date: The tag contains date/time values that are parsed using all internationally
accepted date formatters (MM/dd/yyyy, dd/MM/yyyy, yyyy-MM-dd are defaults).
• Uri: The value for this tag is tokenized with <slash> and <space> as a universal resource
indicator
• Email: The tag value should be tokenized with as an e-mail.
• Saved: Specifies that the field value should be stored in the search index repository,
instead of fetching from metadata store. Generally this should not be used as it may
result in slow retrieval performance.
• Stemmed: Specifies that Porter stemming analyzer should be used for the field while
indexing and searching.
• Content: Specifies the tag is populated in both fullText and the search index.
Example:
set schema NewTag type string namespace foo
search-attributes ‘saved, stemmed'
defines the fully qualified tag fooNewTagName that is a string and has the search-attributes
saved and stemmed.
IS1200 Metadata Reference Guide— v4.8.0
The Metadata Schema and Tag Management
Table 2
Types of Attributes for ‘set_schema’ CLI Command
set schema keyword
Attribute Description
display- attributes
A list of one or more attributes separated by commas within single quotes. Provides a way to
control display screen clutter so only tags of interest are displayed. By setting
display-attributes to ‘hidden’, tags are not displayed in some displays. Only ‘hidden’ and
‘extractable’ are currently supported. When set schema is used in edit mode, new
display-attributes are added to existing ones.
Example:
set schema NewTag type string namespace foo
display-attributes ‘hidden'
defines the fully qualified tag fooNewTagName that can be classified (works in the search
index and the database) but is hidden on the screen. To un-hide, see “Un-hiding Tags” on
page 17.
report- attributes
A string containing report-specific system configuration parameters. Used for internal
purposes, not for general use.
delimit- attributes
A string containing multi-valued tokenization system configuration parameters.
These attributes can be used to increase classification performance when populating
multi-valued tags with long lists of values, e.g., when adding lengthy recipient lists to eMail
metadata tags for PST files.
To increase performance, use:
delimit-attributes 'semantics=fifoset'
Some properties like MailTo, MailCC, DocumentAuthor etc have this setting by default.
The Metadata Schema and Tag Management
9
The Metadata Schema and Tag Management
Metadata Tag Types
Each metadata tag has a type which can also be set using the set
schema command. Types include: string, url, date, integer,
decimal, boolean, and email.
When the set schema command is issued without specifying a type,
set schema looks for an existing tag with the name specified and
attempts to enter edit mode to modify the existing tag.
Date Format Requirements
Date information stored in metadata values (the value side of a
metadata tag-value pair) must match one of the following formats to
be indexed properly and be searchable:
◆
“yyyy-MM-dd'T'HH:mm:ssZZZZZ”
◆
"EEE MMM dd HH:mm:ss yyyy"
◆
"EEE, d MMM yy HH:mm:ss Z"
◆
"F, d MMM yy HH:mm:ss Z"
◆
"EEE, d MMM yy HH:mm:ss z"
◆
"yyyyMMddHHmmss"
◆
"yyyy-MM-dd'T'HH:mm:ss"
◆
"yyyy-MM-dd"
◆
"ddMMMyyyy"
◆
"MMMyyyy"
◆
"MM/dd/yy"
◆
"MM/dd/yy"
◆
"dd/MM/yyyy"
◆
"d MMM yy HH:mm:ss"
◆
"d MMM yy HH:mm:ss zzzzz"
New metadata tags (such as dates) can be added to the search schema
via Command Line Interface or Web-Admin. When adding classification
rules to via Web-Admin, the Set Search Schema dialog box appears
allowing the new tag to be added to the search schema. Metadata
dates added via this dialog must use the formats above.
10
IS1200 Metadata Reference Guide— v4.8.0
The Metadata Schema and Tag Management
Fully Qualified Tag Names
A fully qualified tag name contains both its namespace and the tag
name. For example the default namespace document contains a tag
called author.
This tag’s fully-qualified name is documentauthor
and will appear in GUI-generated search queries as
‘DocumentAuthor’
and in GUI metadata field drop-down menus as
‘Author[Document]’.
Metadata Tag Namespaces
A namespace must be declared whenever a new metadata field (tag) is
added to the Metadata Schema using the set schema command.
IS1200 software versions 4.0 and higher, organizes metadata tags into
a hierarchy defined by namespaces. Namespaces group similar sets of
tags, for example all the file level tags, like FileType, FileSize,
aTime, and cTime are grouped together under the System namespace.
The standard IS1200 software installation provides a standard set of
active namespaces. Additional namespaces may be created as
needed. Additionally, some standard namespaces are not normally
enabled at installation, but can be activated if needed. See “Using
DICOM Tags” on page 123 for more details.
Standard Installation Name Spaces
At the time this chapter was written, the standard IS1200 installation
provided the standard namespaces the following table. A complete,
updated, list of all namespaces can be obtained at anytime using the
Command Line Interface command:
show schema namespaces
Table 3
Standard or Default Name Spaces
Namespace
Description
Amex
Tags specific to American Express rule set
AtmosCloud
Tags specific to Atmos Cloud rule set
Calendar
The Metadata Schema and Tag Management
11
The Metadata Schema and Tag Management
Table 3
Namespace
Standard or Default Name Spaces
Description
Centera
Contact
CTA
Tags specific Cloud tiering appliance
Deduplicate
Tags specific to Deduplication
Detected
Digest
Dinersclub
Tags specific to Dinersclub rule set
Directory
Tags specific to Directory Reporting Rule set
Discover
Tags specific to Discover rule set
Document
Tags specific to Microsoft Office documents, PDF, HTML, etc
Documentum
Domino
Dumpster
Tags specific to objects in the dumpster folder
Ein
Tags specific to EIN rule set
Enterprisevault
Tags specific to data from enterprise vault files
Entity
Envcommon
Exchange
12
Glba
Tags specific to GLBA rule set
Hierarchy
Internal name space for Hierarchical objects like, zip, tar, pst files.
InheritedMail
Internal name space for managing inheritance of properties under a given hierarchy
IPTC
Tags specific to JPEG and GIF file properties
Itin
Tags specific to ITN rule set
Jcb
Tags specific to JCB rule set
Kazcollection
Internal name space managed by quick rule builder
IS1200 Metadata Reference Guide— v4.8.0
The Metadata Schema and Tag Management
Table 3
Standard or Default Name Spaces
Namespace
Description
Kazeon
Tags specific to some prepackaged default rule sets
Legal
Tags specific to Legal service
Legalapp
Tags specific to Legal application, like Interactive tagging.
LegalExport
Mail
Tags specific to the Email properties of exchange, pst, and other email objects
MailDerived
Master
Tags specific to Master Card rule set
MDB
Tags specific to Access database files
Nin
Tags specific to NIN rule set
NSF
Objcommon
OriginalSource
PersistentNameSpace
ProcessingService
Retention
SharePoint
Sin
Tags specific to SIN rule set
Ssn
Tags specific to social security number rule set
Ssncc
Tags specific to SSNCC rule set
System
Tags specific to system metadata captured by IS1200
SystemUserTags
Task
TIFF
UserDefined
Tags populated from CD_tagging services, see below for more details.
The Metadata Schema and Tag Management
13
The Metadata Schema and Tag Management
Table 3
Standard or Default Name Spaces
Namespace
Description
UserExtracted
Tags created by extraction rules, and tags carried over during upgrades from
pre-existing extraction rule tags that have no specific namespace defined., see below.
for more details.
Version
Visa
Tags specific to Visa rule set
Additionally, new tags may be created by Actionable Services and
Extraction rules and they will use the following standard
namespaces:
Table 4
User Defined Namespaces
Namespace
Description
Userdefined
Tags populated from CD_tagging services
Userextracted
Tags created by extraction rules, and tags carried over during upgrades from pre-existing
extraction rule tags that have no specific namespace defined.
The IS1200 uses the name spaces UserDefined and UserExtracted
for special purposes aimed at preserving custom tags. All tags
created in GUI screens (such as Actionable Services Tagging services)
are automatically added to the UserDefined name space. An alias is
defined for the tag entered for the field.
The UserExtracted name space is populated during upgrades from
releases earlier then 3.X or 4.X. All custom tags found during an
upgrade are automatically added to the UserExtracted name space to
preserve them beyond the upgrade process.
14
IS1200 Metadata Reference Guide— v4.8.0
The Metadata Schema and Tag Management
Using ‘set schema’ to Add Tags to the Metadata Schema
The CLI set schema command is used as follows:
set schema <fieldName> namespace <nameSpaceName> type
<typeCode>
attributes <spaceSeparatedListOfAttributes in quotes>
search-attributes <commaSeparatedListOfAttributes in
quotes>
display-attributes <commaSeparatedListOfAttributes in
quotes>
Where:
<fieldName> is the name of the new metadata tag
<nameSpaceName> is the name of the namespace to add the new
tag to
<typeCode> is either text, string, integer, decimal, boolean, or
date and the attributes, search-attributes, and display-attributes
lists are defined in “Types of Attributes for ‘set_schema’ CLI
Command” on page 8.
For example:
set schema capacity namespace geex type string
attributes 'indexed keep' search-attributes ‘saved,
stemmed' display-attributes ‘hidden'
Defines a new metadata field (tag) with the fully-qualified name
geexcapacity, for the tag capacity in the namespace geex, of type
string, with attributes indexed and keep, with search-attributes of
saved and stemmed, and the display-attributes of hidden.
All extraction rules populating the field geexcapacity will add
(cumulatively, not replace) the data of geexcapacity both in the search
indexer and the database.
Note: Date information stored in metadata values (the value side of a
metadata tag-value pair) must match certain formats to be indexed properly
and be searchable. See “Date Format Requirements” on page 10 for more
information.
The Metadata Schema and Tag Management
15
The Metadata Schema and Tag Management
Deleting a Field from the Metadata Schema
Enter the following command at a command line prompt and press
Enter:
remove schema fieldName
where fieldName is the name of the metadata field to remove.
Do not delete file system metadata from the Metadata Schema
because these fields are required to search file systems successfully.
The IS1200 does not allow deleting IS1200 internal metadata fields.
However, you can delete the IS1200-configured metadata or any
custom metadata added to the Metadata Schema.
Other CLI Commands for Tag Maintenance
Besides adding and deleting tags in the Metadata Schema, the CLI
can be used to perform other kinds of tag maintenance, and to inspect
the Metadata Schema. To show the basic Metadata Schema, see
“Viewing the Metadata Schema” on page 7.
Creating New Namespaces
When the set schema command specifies a namespace that does not
exist, it automatically creates a new namespace with the name
specified.
For example, if the following command is issued:
set schema newTagName namespace foo type string
attributes 'keep indexed'
And if the namespace foo does NOT exist, the IS1200 creates a new
foo namespace and adds the new tag newTagName to it.
Editing Tags
Generally, tags may be edited by using the set schema command
without a type designator. When type is omitted, and new attributes
specified are added to current attributes, rather than replacing the
current ones.
For example, to modify search-attributes previously set with:
16
IS1200 Metadata Reference Guide— v4.8.0
The Metadata Schema and Tag Management
set schema categories type string namespace geex
attributes 'keep indexed' search-attributes 'saved,
stemmed'
To change the tag geexcategories to be aggressively tokenized by
the search indexer, use the command:.
set schema categories namespace geex search-attributes
'saved, stemmed, kaztext'
Note the type parameter is not used.
Un-hiding Tags
Assuming a the ‘hidden’ display-attribute was previously applied, to
un-hide the tag geexemailaddress, use the command:
set schema emailaddress namespace geex
display-attributes ''
This makes the geexemailaddress tag visible in GUI screens, the tag
name will now appear in all drop-down menus where metadata field
names can be chosen.
Listing Name Spaces
The CLI command: show schema namespaces
Displays the name spaces currently under tag management.
Listing Tags in a Specific Name Space
The CLI command: show schema document namespace
Displays the fully qualified tags under the name space document.
Listing the Indexed Tags in a Name Space
The CLI command: show schema document namespace select
indexed
Displays the indexed tags in the name space document. Similarly, one
can select keep, multivalued, and other attributes and restrict the
display to those specific fields.
The Metadata Schema and Tag Management
17
The Metadata Schema and Tag Management
Listing the Details of a Specific Fully Qualified Tag
The CLI command: show schema geexcategories
Displays all details of the fully qualified tag geexcategories.
Synchronizing Tag Management with Database
The CLI command: synchronize schema
Synchronizes tag management with the database. Use this command
after editing a field to ensure subsequent classifications are affected.
Use this command only when other services are not running. Tag
management changes should only be done when no services are
running.
Best Practices
The following Best Practices should be followed.
Always synchronize the tag management with database after editing
any tag.
Always use fully qualified tags in extraction and assignment rules
Always define different name spaces for extraction rule set tags and
assignment rule set tags.
Tags designated for extraction rule sets should not be cumulative
(should not have an attribute of ‘usertag’), this ensures that each
successive classification puts new metadata in the tag, and that
previous values do not persist.
When required, edit a tag's properties to un-hide a tag or change
search attributes.
Tags that are not defined anywhere in the tag management are
temporary tags and are not persisted
18
IS1200 Metadata Reference Guide— v4.8.0
The Metadata Schema and Tag Management
Customizing the Metadata Schema for Web-Search Preview
To enable Preview mode in Web-Search, issue this
Command Line Interface command.
For v4.2 or greater:
set previewer status enable
For v4.1.2 or earlier:
set schema System.FullText search-attributes
kaztext,content,indexed,index=primary,saved
This allows Preview mode to display the fullText of search results
files in the Web-Search Previewer pane. Once set, a new deep
classification must be run to extract and record the Preview
information
Customizing the Search Schema for DICOM Data
If you intend to classify DICOM files, the IS1200 is designed to
recognize and classify the standard DICOM file attributes. However,
because there are hundreds of these, they are not a part of the default
search schema.
Be aware that the IS1200 only classifies DICOM file headers, the
images themselves are not opened or parsed.
To add any of the DICOM file attributes to the default search schema,
see “Using DICOM Tags” on page 123.
The Metadata Schema and Tag Management
19
The Metadata Schema and Tag Management
20
IS1200 Metadata Reference Guide— v4.8.0
2
The Default Schema and Metadata Tags
All IS1200 installations come with a standard default set of metadata
tags which are organized by namespaces. See “Metadata Tag
Namespaces” on page 11 for more details on namespaces.
Additionally, other standard metadata tags are automatically
available when specific rulesets or optional modules are employed.
This chapter lists all the standard IS1200 metadata Schema
namespaces and the standard metadata tags associated with those
namespaces.
Topics include:
◆
◆
◆
◆
◆
◆
How Metadata Tags and Namespaces are Organized..................
Namespace Tables Legend................................................................
System Default Namespaces ............................................................
Namespaces Populated by Rulesets................................................
Namespaces Populated by Optional Module Connectors...........
Alphabetic Listing of Indexed Default Metadata Tags:................
The Default Schema and Metadata Tags
22
23
24
64
79
92
21
The Default Schema and Metadata Tags
How Metadata Tags and Namespaces are Organized
All metadata tags are discussed as part of their namespace. However,
namespaces are grouped according to the following categories:
22
◆
“System Default Namespaces” on page 24:
The metadata tags in these namespaces are always populated
whenever a deep classification using the fullText ruleset is run.
◆
“Namespaces Populated by Rulesets” on page 64:
The metadata tags in these namespaces are only populated when
a deep classification is done and a specific ruleset (extracted or
assignment) is applied to the classification. See the Policies:
Extraction and Assignment Rules chapter of the IS1200
Web-Admin User and Configuration Guide for more details on
rulesets.
◆
“Namespaces Populated by Optional Module Connectors” on
page 79: The metadata tags in these namespaces are only
populated when a specific Optional Module Connector license is
installed and a deep classification is run on a data repository
accessed by that optional module. See the Optional Modules
section of the Introduction chapter of the IS1200 Web-Admin
User and Configuration Guide for more details on optional
modules.
◆
“Alphabetic Listing of Indexed Default Metadata Tags:” on
page 92: Not all the default tags are automatically indexed, only
those with the key word “indexed” in the Schema, see for details.
This table lists all default tags that have the “indexed” keyword.
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Namespace Tables Legend
The Namespace tables are organized as follows:
◆
Description: Describes properties common to all the tags in this
namespace.
◆
Service populating namespace: List the types of jobs, services,
reports, etc. that can be used to populate the namespace’s
metadata fields.
◆
Extraction ruleset: The extraction ruleset that must be used by the
job or service above to populate the metadata fields.
◆
Assignment ruleset: The assignment ruleset that must be used by
the job or service above to populate the metadata fields.
The Namespace Tags tables below:
◆
Tags: List the metadata tags contained by that namespace.
◆
Saved in DB (reportable): Is checked if the metadata information
is saved by default to the database, and therefore usable in
reports.
◆
Indexed (searchable): Is checked if the metadata information is
saved by default to the search index, and therefore searchable by
that tag.
◆
Comments: Unique information about the metadata tag.
The Default Schema and Metadata Tags
23
The Default Schema and Metadata Tags
System Default Namespaces
The metadata tags in the following namespaces are always populated
whenever a deep classification using the fullText ruleset is run.
Calendar Namespace
Table 5
Calendar Namespace
Description
Outlook Calendar (meeting or appointment) information tags
Service populating namespace
Deep, reclassify, collection-with-source-fulltext-indexing, collection-target-indexing,
copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 6
Calendar Namespace Tags
Tags
Saved in DB
(reportable)
CalendarEndTime
Y
Comments
Outlook Calendar Appointment/ Meeting end time
CalendarFrom
Alias for MailFrom
CalendarLocation
Alias for MailLocation
CalendarOptionalAttendees
Alias for MailCc
CalendarRecurrence
Y
Outlook Calendar Appointment/ Meeting Recurrence
CalendarRequiredAttendees
Alias for MailTo
CalendarSentDate
Alias for MailDate
CalendarStartTime
Y
CalendarSubject
24
Indexed
(Searchable)
IS1200 Metadata Reference Guide— v4.8.0
Outlook Calendar Appointment/ Meeting start time
Alias for MailSubject
The Default Schema and Metadata Tags
Contact Namespace
Table 7
Contact Namespace
Description
Outlook contact information tags
Service populating namespace
Deep, reclassify, collection-with-source-fulltext-indexing, collection-target-indexing,
copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 8
Contact Namespace Tags
Tags
Saved in DB (reportable)
ContactAnniversaryDate
Y
ContactAssistantName
Y
ContactAssistantPhone
Y
ContactBirthDate
Y
ContactBusiness2Phone
Y
ContactBusinessAddress
Y
ContactBusinessFax
Y
ContactBusinessPhone
Y
ContactCallbackPhone
Y
ContactCarPhone
Y
ContactCompany
Y
ContactCompanyPhone
Y
ContactDepartment
Y
ContactDisplayAs
Y
ContactEMail2Address
Y
ContactEMail3Address
Y
ContactEMailAddress
Y
ContactFamily Name
Y
Indexed (Searchable)
Comments
The Default Schema and Metadata Tags
25
The Default Schema and Metadata Tags
Table 8
26
Contact Namespace Tags
Tags
Saved in DB (reportable)
ContactFileAs
Y
ContactFirstName
Y
ContactFullName
Y
ContactGender
Y
ContactHome2Phone
Y
ContactHomeAddress
Y
ContactHomeFax
Y
ContactHomePhone
Y
ContactIMAddress
Y
ContactISDNPhone
Y
ContactJobTitle
Y
ContactManagerName
Y
ContactMiddleName
Y
ContactMobilePhone
Y
ContactNameSuffix
Y
ContactNickname
Y
ContactOffice
Y
ContactOtherAddress
Y
ContactOtherFax
Y
ContactOtherPhone
Y
ContactPager
Y
ContactPrimaryPhone
Y
ContactProfession
Y
ContactRadioPhone
Y
ContactSpouseName
Y
IS1200 Metadata Reference Guide— v4.8.0
Indexed (Searchable)
Y
Y
Comments
The Default Schema and Metadata Tags
Contact Namespace Tags
Table 8
Tags
Saved in DB (reportable)
ContactTelexPhone
Y
ContactTitle
Y
ContactTTYPhone
Y
ContactWebPage
Y
Indexed (Searchable)
Comments
CTA Namespace
CTA Namespace Tags
Table 9
Tags
Saved in DB (reportable)
Indexed (searchable)
Comments
CTAFileSizeOnDisk
Y
Y
Additional attribute to report
actual disk space used, in
case of NFS/CIFS storages
connected to EMC CTA
appliance).
The Default Schema and Metadata Tags
27
The Default Schema and Metadata Tags
Detected Namespace
Table 10
Detected Namespace
Description
Service populating namespace
Deep, reclassify, collection-with-source-fulltext-indexing, collection-target-indexing,
copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 11
Detected Namespace Tags
Tags
Saved in DB (reportable)
Indexed (Searchable)
detectedalternates
Y
Y
detectedlanguage
Y
Y
Comments
DICOM Namespace
Table 12
DICOM Namespace
Description
DICOM file information tags
Service populating namespace
Deep, reclassify, collection-with-source-fulltext-indexing, collection-target-indexing,
copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
See “Using DICOM Tags” on page 123 for the list of DICOM
metadata tags available and details about added them to the schema.
28
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Digest Namespace
Table 13
Digest Namespace
Description
Tags to store object's digest information (used for De-duplication)
Service populating namespace
Any classification service
(basic/deep/collection-with-source/target-indexing/copy-with-target-indexing/in-plac
e-processing)
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 14
Digest Namespace Tags
Tags
Saved in DB (reportable)
Indexed (Searchable)
Comments
DigestObject
Y
Digest of the object
DigestProfileId
Y
ID of profile used for digest calculation
Directory Namespace
Table 15
Directory Namespace
Description
Namespace that populates up to first five directory names of a file path
Service populating namespace
Basic, Deep, Reclassify-Action
Extraction Ruleset
n/a
Assignment Ruleset
DirectoryReporting
Table 16
Directory Namespace Tags
Tags
Saved in DB (reportable) Indexed (Searchable)
Comments
directorydir1
Y
First directory in the file path (if it exists)
directorydir2
Y
Second directory in the file path (if it exists)
directorydir3
Y
Third directory in the file path (if it exists)
directorydir4
Y
Fourth directory in the file path (if it exists)
directorydir5
Y
Fifth directory in the file path (if it exists)
The Default Schema and Metadata Tags
29
The Default Schema and Metadata Tags
Document Namespace
Table 17
Document Namespace
Description
Information about metadata of objects like Microsoft office documents, PDF
documents, etc.
Service populating namespace
Deep, reclassify, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 18
Document Namespace Tags
Tags
Saved in DB (reportable)
Indexed (Searchable) Comments
Y
Y
Y
Y
DocumentAccount
DocumentAddress
DocumentAttachments
DocumentAuthor
DocumentAuthorization
DocumentBackupDate
DocumentBaseFileLocation
DocumentBillTo
DocumentBlindCopy
DocumentCarbonCopy
DocumentCategory
DocumentCharacterCount
DocumentCheckedBy
DocumentClient
DocumentComments
Y
DocumentCompany
Y
DocumentCompletedDate
30
IS1200 Metadata Reference Guide— v4.8.0
Y
The Default Schema and Metadata Tags
Table 18
Document Namespace Tags
Tags
Saved in DB (reportable)
Indexed (Searchable) Comments
Y
Y
Y
Y
Y
Y
DocumentContributor
DocumentCountBytes
DocumentCountCharsWithSpaces
DocumentCountLines
DocumentCountMMClips
DocumentCountNotes
DocumentCountParas
DocumentCountSlides
DocumentCountSlidesHidden
DocumentCreationDate
DocumentDepartment
DocumentDescription
DocumentDestination
DocumentDisposition
DocumentDivision
DocumentDocNumber
DocumentDocType
DocumentEditor
DocumentForwardTo
DocumentHeadingPairs
DocumentKeyWords
Y
DocumentLanguage
Y
Y
Y
Y
DocumentLastPrintDate
DocumentLastSaveDate
DocumentLastSavedBy
The Default Schema and Metadata Tags
31
The Default Schema and Metadata Tags
Table 18
Document Namespace Tags
Tags
Saved in DB (reportable)
Indexed (Searchable) Comments
Y
Y
Y
Y
DocumentLinksDirty
DocumentMailStop
DocumentManager
DocumentMatter
DocumentMinutesEdited
DocumentOffice
DocumentOperator
DocumentOwner
DocumentPageCount
Objects with
PageCount as an
attribute, are extracted
by the parser and
exported by the legal
export.For example,
Microsoft word files.
Note: PageCount is
only supported for
Microsoft word 2010
documents.
PageCount is always
displayed as 1 for the
Microsoft word
documents saved in
the versions prior to
Microsoft word 2010.
DocumentPresentationFormat
DocumentProject
Y
Y
DocumentPublisher
Y
Y
DocumentPurpose
DocumentReceivedFrom
DocumentRecordedBy
32
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Table 18
Document Namespace Tags
Tags
Saved in DB (reportable)
Indexed (Searchable) Comments
Y
Y
DocumentSubject
Y
Y
DocumentTitle
Y
Y
DocumentRecordedDate
DocumentRelation
DocumentRevisionDate
DocumentRevisionNotes
DocumentRevisionNumber
DocumentScaleCrop
DocumentSection
DocumentSecurity
DocumentSource
DocumentStatus
DocumentTitleOfParts
DocumentTypist
DocumentVersionDate
DocumentVersionNotes
DocumentVersionNumber
DocumentWordCount
DocumentWorkGroup
EnvCommon Namespace
Table 19
Description
EnvCommon Namespace
Environment specific metadata
The Default Schema and Metadata Tags
33
The Default Schema and Metadata Tags
Table 19
Service populating namespace
Any classification service
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 20
34
EnvCommon Namespace
EnvCommon Namespace Tags
Tags
Saved in DB (reportable) Indexed (Searchable)
Comments
EnvcommonMtime
Y
Y
Environment specific
mtime;Mailreceive time for
mails, otherwise mtime of
objects.
EnvcommonRepositorytype
Y
Y
Repository type (e.g., domino,
documentum, etc.)
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Hierarchy Namespace
Table 21
Hierarchy Namespace
Description
Information of objects and sub-objects in composite objects
Service populating namespace Any classification service (note that anot all properties/tags are populated in all
classification services)
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 22
Hierarchy Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
HierarchyActionCasid
Y
Casid of parent object on which action can be
taken.
HierarchyChildrenCompleted
Y
Internal use
HierarchyDepth
Y
Level of the sub-document in the composite file.
HierarchyDisplayObjectType
Y
Y
Type of subdocument like 'embedded email' ,
'embedded file' etc.
HierarchyErrorMessage
Y
Y
Any Errors while parsing the object.
HierarchyFileName
Y
Y
Filename if physical object. Sub-document name if
object is a subdocument. Mail Subject if object is a
mail.
HierarchyFolderName
Y
Y
Name of any folder where the subdocument
resides in the composite file.
HierarchyHasChild
Y
Set to 't' if object has any children.
HierarchyLineage
Y
Internal use
HierarchyOffsets
Y
Internal use
Comments
The Default Schema and Metadata Tags
35
The Default Schema and Metadata Tags
InheritedMail Namespace
Table 23
InheritedMail Namespace
Description
Information parent mail properties inherited by sub-documents (email attachments)
Service populating namespace Deep, reclassify-action, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
Table 24
36
fulltext (rule)
InheritedMail Namespace Tags
Assignment Ruleset
n/a
InheritedMailBccLevel1
Y
Y
If immediate parent is email, mailbcc list of that
parent
InheritedMailBccLevel2
Y
Y
If immediate grandparent is email, mailbcc list of
that grandparent
InheritedMailBccLevel3
Y
Y
If object's lineage above 2 levels has email(s),
union of mailbcc list of all those parents
InheritedMailCcLevel1
Y
Y
If immediate parent is email, mailcc list of that
parent
InheritedMailCcLevel2
Y
Y
If immediate grandparent is email, mailcc list of
that grandparent
InheritedMailCcLevel3
Y
Y
If object's lineage above 2 levels has email(s),
union of mailcc list of all those parents
InheritedMailDateLevel1
Y
Y
If immediate parent is email, maildate of that
parent
InheritedMailDateLevel2
Y
Y
If immediate parent is email, maildate of that
parent
InheritedMailDateLevel3
Y
Y
If object's lineage above 2 levels has email(s),
union of maildates of all those parents
InheritedMailFromLevel1
Y
Y
If immediate parent is email, mailfrom list of that
parent
InheritedMailFromLevel2
Y
Y
If immediate grandparent is email, mailfrom of that
grandparent
InheritedMailFromLevel3
Y
Y
If object's lineage above 2 levels has email(s),
union of mailfrom list of all those parents
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Table 24
InheritedMail Namespace Tags
Assignment Ruleset
n/a
InheritedMailReceivedLevel1 Y
Y
If immediate parent is email, mailreceived date of
that parent
InheritedMailReceivedLevel2 Y
Y
If immediate grandparent is email, mailreceived
date of that grandparent
InheritedMailReceivedLevel3 Y
Y
If object's lineage above 2 levels has email(s),
union of mailreceived dates of all those parents
InheritedMailSubjectLevel1
Y
Y
If immediate parent is email, mailsubject of that
parent
InheritedMailSubjectLevel2
Y
Y
If immediate grandparent is email, mailsubject of
that grandparent
InheritedMailSubjectLevel3
Y
Y
If object's lineage above 2 levels has email(s),
union of mailsubject of all those parents
InheritedMailToLevel1
Y
Y
If immediate parent is email, mailto list of that
parent
InheritedMailToLevel2
Y
Y
If immediate grandparent is email, mailto list of that
grandparent
InheritedMailToLevel3
Y
Y
If object's lineage above 2 levels has email(s),
union of mailto list of all those parents
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
The Default Schema and Metadata Tags
37
The Default Schema and Metadata Tags
IPTC Namespace
Table 25
Description
IPTC Namespace
Tags for IPTC properties of images
Service populating namespace Deep, reclassify-action, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 26
38
IPTC Namespace Tags
Tags
Saved in DB (reportable)
IPTCByline
Y
IPTCBylineTitle
Y
IPTCCaption
Y
IPTCCaptionWriter
Y
IPTCCategory
Y
IPTCCity
Y
IPTCCopyrightNotice
Y
IPTCCountry
Y
IPTCCredits
Y
IPTCDateCreated
Y
IPTCHeadline
Y
IPTCKeywords
Y
IPTCObjectName
Y
IPTCOriginalTransmissionReference
Y
IPTCSource
Y
IS1200 Metadata Reference Guide— v4.8.0
Indexed (Searchable)
Comments
The Default Schema and Metadata Tags
Table 26
IPTC Namespace Tags
Tags
Saved in DB (reportable)
IPTCSpecialInstructions
Y
IPTCState
Y
IPTCSupplementalCategories
Y
Indexed (Searchable)
Comments
Kazcollection Namespace
Table 27
Kazcollection Namespace
Description
Collection name namespace
Service populating namespace
Collection-with-source-fulltext-indexing, collection-target-indexing
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 28
Kazcollection Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
KazcollectionRuleName
Y
Y
Comments
List of collection name(s) associated with the object
(both source and targets)
The Default Schema and Metadata Tags
39
The Default Schema and Metadata Tags
Kazeon Namespace
Table 29
Kazeon Namespace
Description
Internal namespace (maintained for backward compatibility).
Service populating namespace
Extraction Ruleset
Assignment Ruleset
Table 30
40
Kazeon Namespace Tags
Tags
Saved in DB
(reportable)
KazeonAccountNo
Y
KazeonAutoMFG
Y
KazeonConfidential
Y
KazeonContracts
Y
KazeonExtDate
Y
KazeonHipaa
Y
KazeonHR
Y
Kazeoninternaluseonly
Y
KazeonIPRelated
Y
KazeonLegalDiscovery
Y
KazeonMFG
Y
KazeonName
Y
KazeonNpiType
Y
KazeonNpiValue
Y
KazeonPostalCode
Y
Y
KazeonPrice
Y
Y
KazeonRecordType
Y
KazeonRoutingNo
Y
IS1200 Metadata Reference Guide— v4.8.0
Indexed
(Searchable)
Y
Y
Y
Comments
The Default Schema and Metadata Tags
Table 30
Kazeon Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
KazeonSalesMarketing
Y
KazeonSECData
Y
KazeonSocialSecurityNumber
Y
Y
KazeonStockSymbol
Y
Y
KazeonTelephoneNumber
Y
Y
KazeonUKNpiType
Y
KazeonUKNpiValue
Y
KazeonUniversity
Y
KazeonUri
Y
Comments
Y
Legalapp Namespace
Note: The Legalapp namespace tags are only available with IS1200
installations such as ECS that include the eDiscovery Case Manager.
Table 31
Legalapp Namespace
Description
Legal application's per case object data.
Service populating namespace
Tagging during legal review
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 32
Legalapp Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
legalappCase
Y
Y
The casenum
legalappLastReviewedBy
Y
Y
The last user the document was reviewed by (per
case).
legalappLastReviewedDate
Y
Y
Stores the last review date (per case).
The Default Schema and Metadata Tags
41
The Default Schema and Metadata Tags
Table 32
Legalapp Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
legalappNotes
Y
Y
Notes the user entered while setting the legal hold.
legalappReviewedAs
Y
Y
The document's review status. Out of the box
ships with the following values
[None|Completed|pending|Deferred].
legalappReviewer
Y
Y
The reviewer assigned (per case).
legalappTag
Y
Y
The review tag assigned to the document (per
case). Out of the box ships with the following
values [Not
Relevant|Privileged|Escalate|Responsive].
Legal Namespace
Note: The Legal namespace tags are only available with IS1200 installations
such as ECS that include the eDiscovery Case Manager.
Table 33
Legal Namespace
Description
Legal hold related metadata attributes.
Service populating namespace
Extraction Ruleset
Assignment Ruleset
42
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Table 34
Legal Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
legalhold
Y
Y
legalhold_orig_acls
Y
Legalholdenforcefs
Y
LegalholdEnforcementReleaseDate
Y
legalholdexecutor
Y
Comments
[yes|no]. This field is multi valued, hence the
format of values per case are
legalapp.[casnum].[yes|no]. When set to yes
the objects is set on legal hold for the case
specified in the value.
The original ACL byte stream of the object
prior to legal hold.
Y
Stores 'true' if legal hold was enforced on the
repository for the object, else 'false. Values
[true|false].
The time legalhold was set on the physical
file.
Y
Stores the user (per case) that set legal hold
on the object.
legalholdmonth
legalholdnotes
Y
Stores the notes user entered while setting
the legal hold.
legalholdowner
Y
Stores the original owner of the object set on
legal hold. This is important because legal
hold can change the owner of the object.
LegalholdReleaseDate
Y
Stores the (per case) date when legal hold
was released.
LegalholdSetDate
Y
Stores the (per case) date when legal hold
was set.
legalholdtime
Y
Y
The time legal hold was set on the object.
legalholdtype
Y
Y
Stores the type of hold on the physical
object. Values [legal|security].
legalholdyear
The Default Schema and Metadata Tags
43
The Default Schema and Metadata Tags
LegalExport Namespace
Note: The LegalExport namespace tags are only available with IS1200
installations such as ECS that include the eDiscovery Case Manager.
Table 35
Legal Namespace
Description
Tags created after a successive Legal Export for files that were exported using
the Rolling Exports options.
Service populating namespace
Legal Export
Extraction Ruleset
Assignment Ruleset
Table 36
44
Legal Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable) Comments
LegalExportCaseIds
Y
Y
[yes|no]. Field is multi valued, hence the format of values per
case are legalapp.[casnum].[yes|no]. When set to yes the
objects have been exported for the case specified in the
value.
LegalExportJobIds
Y
Y
Field is multi valued, hence the format of values per case are
legalapp.[casnum].[jobID].
LegalExportTimes
Y
Y
The time object was Legally Exported.
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
MailDerived Namespace
Table 37
MailDerived Namespace
Description
Tags derived from mail properties
Service populating namespace
Deep, Reclassify-Action, Collection-with-source-fulltext-indexing,
Collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext(rule)
Assignment Ruleset
n/a
Table 38
MailDerived Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
MailDerivedDirection
Y
Y
MailDerivedDirectionInheritedLevel1
Y
Y
MailDerivedDirectionInheritedLevel2
Y
Y
MailDerivedDirectionInheritedLevel3
Y
Y
MailDerivedFromDomain
Y
Y
Senders mail domain
MailDerivedFromDomainInheritedLevel1
Y
Y
If immediate parent is email,
senders mail domain of parent
MailDerivedFromDomainInheritedLevel2
Y
Y
If immediate grandparent is email,
senders mail domain of parent
MailDerivedFromDomainInheritedLevel3
Y
Y
If any object in lineage is email,
union of senders mail domain of
all those objects
MailDerivedRecipientDomain
Y
Y
Receiver's mail domain
MailDerivedRecipientDomainInheritedLevel1
Y
Y
If immediate parent is email,
receiver's mail domain of parent
MailDerivedRecipientDomainInheritedLevel2
Y
Y
If immediate grandparent is email,
receiver's mail domain of parent
MailDerivedRecipientDomainInheritedLevel3
Y
Y
If any object in lineage is email,
union of receiver's mail domain of
all those objects
Comments
Direction of mail like 'outgoing',
'incoming' , 'internal' etc.
The Default Schema and Metadata Tags
45
The Default Schema and Metadata Tags
Mail Namespace
Table 39
Mail Namespace
Description
Extracted properties of mails are stored in this namespace.
Services that populate it:
Deep, Reclassify-Action, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 40
Mail Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Y
Y
Comments
MailAlternateRecipientAllowed
MailAttachment
MailAttachmentsCount
File/files sent along with email
attachment.
Number of attachments with the email.
MailAttrHidden
MailAttrReadonly
MailAttrSystem
Y
MailAutoForwarded
Y
MailBcc
Y
MailCategories
Y
MailCc
Y
Y
Members marked in the Bcc list.
Y
Members who are in the copy list of an
email.
MailCcme
MailClientSubmitTime
Sender name in the copy list.
Y
Date and timestamp of the email sent by
the sender.
MailCompany
MailConversationIndex
MailConversationTopic
46
IS1200 Metadata Reference Guide— v4.8.0
Y
Y
Subject of the mail.
The Default Schema and Metadata Tags
Table 40
Mail Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
MailCreationTime
Comments
Time when the mail was composed.
MailCreatorEntryid
MailCreatorName
Y
MailDate
Y
MailDeferredDeliveryTime
Y
Y
Date and timestamp of the mail
received.
MailDeleteAfterSubmit
MailEmail
Y
Y
MailEntryId
Internal ID of the mail.
MailExpires
Y
MailExpiryTime
Y
MailFlagsts
Y
MailFrom
Y
MailFullname
Y
MailHomephone
MailImportance
Status as to whether the mail has been
expired or not.
Y
Sender of the mail.
Full name of the sender.
Phone number of the sender.
Y
Importance state of the email.
MailInetMailOverrideFormat
MailInReplyTo
Y
MailInternetArticleNumber
MailInternetCpid
MailInternetMessageId
Y
Unique internet message ID associated
with the email.
MailJobtitle
The Default Schema and Metadata Tags
47
The Default Schema and Metadata Tags
Table 40
Mail Namespace Tags
Tags
Saved in DB
(reportable)
MailLastModified
Y
Indexed
(Searchable)
Comments
Deep Crawl
Exchange Server: Time when the object
was crawled
Standalone .msg files: Time when the
object was saved
Collection
Exchange Server: Time when the object
was collected
Standalone .msg files: Time when the
object was saved
Modification Time
Deep Crawl
Exchange Server: Actual mail
received/sent
Standalone .msg files: Time when the
object was saved
Collection
Exchange Server: Actual mail
received/sent
Standalone .msg files: Time when the
object was saved
MailLastModifierEntryid
MailLastModifierName
Y
Person who modified the mail last.
MailLatestDeliveryTime
Y
MailLocation
Y
MailMessageClass
Y
Y
MailMessageId
Y
Y
MailMessageLocaleId
Y
MailMessageCodepage
MailMessageSubmissionId
48
IS1200 Metadata Reference Guide— v4.8.0
Type of message such as:
'IPM.Note' (for emails),
'IPM.Appointment' (for calender items)
‘IPM.Note.ExShortcut” for email stubs
The Default Schema and Metadata Tags
Table 40
Mail Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
MailMsgEditorFormat
MailMsgflag
Y
Flag associated with the email.
MailNewsgroups
MailNormalizedSubject
MailNtSecurityDescriptor
Y
MailOriginatorDeliveryReportRequested
MailPriority
Y
Priority set for the email.
MailProfileConnectFlags
MailRcvdByFlags
MailRcvdRepresentingAddrtype
MailRcvdRepresentingEmailAddress
MailRcvdRepresentingEntryid
MailRcvdRepresentingFlags
MailRcvdRepresentingName
MailRcvdRepresentingSearchKey
MailReadReceiptRequested
MailReceived
Y
Y
Receiver of the email.
MailReceivedByAddrtype
MailReceivedByEmailAddress
MailReceivedByEntryid
MailReceivedByName
Y
MailReceivedBySearchKey
MailRecipientReassignmentProhibited
MailReferences
Y
MailReplyRequested
The Default Schema and Metadata Tags
49
The Default Schema and Metadata Tags
Table 40
Mail Namespace Tags
Tags
Saved in DB
(reportable)
MailReplyTime
Y
Indexed
(Searchable)
Comments
Size of the email.
MailReportTag
MailResponseRequested
MailRtfbody
MailRtfInSync
MailRtfSyncBodyCount
MailRtfSyncBodyCrc
MailRtfSyncBodyTag
MailRtfSyncPrefixCount
MailRtfSyncTrailingCount
MailSearchKey
MailSenderAddrtype
MailSenderEmailAddress
Y
MailSenderEntryid
MailSenderFlags
MailSenderName
Y
MailSenderSearchKey
MailSensitivity
Y
MailSentRepresentingAddrtype
MailSentRepresentingEMailAddress
MailSentRepresentingEntryid
MailSentRepresentingFlags
MailSentRepresentingSearchKey
50
MailSize
Y
Y
MailSubject
Y
Y
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Table 40
Mail Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
Y
Receiver of the email.
MailSubmittime
MailThreadIndex
Y
MailTo
Y
MailTransportMessageHeaders
MailTrustSender
MailUnknown
MailWebpage
MailWorkphone
The Default Schema and Metadata Tags
51
The Default Schema and Metadata Tags
MDB Namespace
Table 41
MDB Namespace
Description
Extracted properties of Access database ( saved in MDB files) are stored in this
namespace.
Services that populate it:
Deep, Reclassify-Action, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 42
MDB Namespace Tags
Tags
Saved in DB
(reportable)
MDBColumn
Y
MDBTable
Y
Indexed
(Searchable)
Comments
Objcommon Namespace
Table 43
Description
Metadata specific to the object.
Services that populate it:
Any classification service
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 44
52
Objcommon Namespace
Objcommon Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
ObjcommonMtime
Y
Y
mailreceive time for mail type objects
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
OriginalSource Namespace
Table 45
OriginalSource Namespace
Description
Metadata from the original source of the object's instance.
Services that populate it:
Any classification service (not all tags are populated with all services)
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 46
OriginalSource Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
OriginalsourceAdHocTag
Y
Y
OriginalsourceContainerLocation
Y
OriginalsourceCustodian
Y
Y
OriginalsourceDocId
Y
Y
OriginalsourceFinalized
Y
OriginalsourceLocation
Y
Comments
Y
Persistentnamespace Namespace
Table 47
Processingservice Namespace
Description
Services that populate it:
Collection and/or processing legalapp
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 48
Tags
Processingservice Namespace Tags
Saved in DB
(reportable)
PersistentNameSpaceLegalCaseNum Y
Indexed
(Searchable)
Comments
Y
Case numbers this object belongs to.
The Default Schema and Metadata Tags
53
The Default Schema and Metadata Tags
Processingservice Namespace
Table 49
Processingservice Namespace
Description
Tags that don't get erased with re-crawls, and are not assigned or userdefined.
Services that populate it:
In-place-processing
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 50
Processingservice Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Processingservicename
Y
Y
Comments
Retention Namespace
Table 51
Retention Namespace
Description
Describes the object retention.
Services that populate it:
Deep, Reclassify-Action, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing,
Retention.
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 52
Retention Namespace Tags
Tags
Saved in DB
(reportable)
Retentionclass
Y
Indexed
(Searchable) Comments
Retentionclassname
54
Retentiondate
Y
Set to the date for which the object will be set under
Retention.
Retentionlock
Y
Set to 'yes' if the object is set under Retention and is
locked.
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Table 52
Tags
Retention Namespace Tags
Saved in DB
(reportable)
Indexed
(Searchable) Comments
Retentionreportdate
Retentionsetdate
Y
Retentionsetuser
Y
Set to the date when the object was set under Retention.
Y
Set to the name of the user who put the object under
Retention.
The Default Schema and Metadata Tags
55
The Default Schema and Metadata Tags
System Namespace
Table 53
System Namespace
Description
System specific information of files are stored in this namespace.
Services that populate it:
Any classification service (not all tags are populated at all times)
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 54
System Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
SystemAtime
Y
Y
Atime of the file
SystemCasid
Y
Y
SystemCasidV
Y
Y
SystemCreationTime
Y
Y
SystemCTime
Y
Y
SystemEndVersionTime
Y
Y
SystemFileExtension
Y
Y
SystemFilepath
Y
Y
SystemFilerName
Y
Y
SystemFileSize
Y
Y
SystemFileType
Y
Y
SystemFullText
Y
Y
Y
Y
Y
Y
Actual file extension in the file system.
SystemFileName
SystemfulltextLimit
SystemGroupName
Systemlargeparsetimeout
SystemLastSeenTime
SystemmatchLimit
56
IS1200 Metadata Reference Guide— v4.8.0
Type of the file
The Default Schema and Metadata Tags
Table 54
System Namespace Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
Y
Y
Mtime of the file
SystemObjectName
Y
Y
SystemObjectType
Y
Y
SystemOwnerName
Y
Y
SystemPolicyGroups
Y
Y
SystemRetentionTime
Y
Y
SystemSnaplocked
Y
Y
SystemSnaplockTime
Y
Y
SystemSsHasBeenDeleted
Y
Y
SystemStartVersionTime
Y
Y
Y
Y
Y
Y
Tags
SystemMimeType
SystemMtime
SystemnoFragmentCD
Systemparsetimeout
SystemtextLimit
SystemTypeExtension
Extenstion depending on type of the file.
SystemUncPath
SystemUniqueDocumentID
The Default Schema and Metadata Tags
57
The Default Schema and Metadata Tags
Systemusertags Namespace
Table 55
Systemusertags Namespace
Description
Services that populate it:
NISHESH
Extraction Ruleset
Assignment Ruleset
Table 56
Systemusertags Namespace Tags
Tags
Saved in DB
(reportable)
SystemUsertagsDigestComposite
Y
Indexed
(Searchable)
Comments
Task Namespace
Table 57
Task Namespace
Description
Services that populate it:
Deep, Reclassify-Action, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 58
58
Task Namespace Tags
Tags
Saved in DB
(reportable)
TaskActualWork
Y
TaskBillingInformation
Y
TaskCompanies
Y
TaskDateCompleted
Y
TaskDueDate
Y
TaskMileage
Y
IS1200 Metadata Reference Guide— v4.8.0
Indexed
(Searchable)
Comments
The Default Schema and Metadata Tags
Table 58
Task Namespace Tags
Tags
Saved in DB
(reportable)
TaskOwner
Y
TaskPercentComplete
Y
TaskPriority
Y
TaskStartDate
Y
TaskStatus
Y
TaskSubject
Y
TaskTotalWork
Y
TaskUpdateList
Y
Indexed
(Searchable)
Comments
Y
The Default Schema and Metadata Tags
59
The Default Schema and Metadata Tags
Tiff Namespace
Table 59
Description
Tiff file information is stored in this namespace.
Services that populate it:
Deep, Reclassify-Action, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 60
60
Tiff Namespace
Tiff Namespace Tags
Tags
Saved in DB
(reportable)
TIFF_254
Y
TIFF_258
Y
TIFF_259
Y
TIFF_262
Y
TIFF_266
Y
TIFF_269
Y
TIFF_270
Y
TIFF_271
Y
TIFF_272
Y
TIFF_273
Y
TIFF_274
Y
TIFF_277
Y
TIFF_278
Y
TIFF_279
Y
TIFF_282
Y
TIFF_283
Y
TIFF_284
Y
IS1200 Metadata Reference Guide— v4.8.0
Indexed
(Searchable)
Comments
The Default Schema and Metadata Tags
Table 60
Tiff Namespace Tags
Tags
Saved in DB
(reportable)
TIFF_296
Y
TIFF_301
Y
TIFF_305
Y
TIFF_306
Y
TIFF_315
Y
TIFF_317
Y
TIFF_318
Y
TIFF_319
Y
TIFF_33432
Y
TIFF_529
Y
TIFF_532
Y
TIFFArtist
Y
TIFFCopyright
Y
TIFFDateTime
Y
TIFFImageDescription
Y
TIFFImageLength
Y
TIFFImageWidth
Y
TIFFMake
Y
TIFFModel
Y
TIFFSoftware
Y
Indexed
(Searchable)
Comments
Y
Y
The Default Schema and Metadata Tags
61
The Default Schema and Metadata Tags
Userdefined Namespace
Note: The Userdefined namespace tags are only available with IS1200
installations such as ECS that include the eDiscovery Case Manager.
Table 61
Userdefined Namespace
Description
Tags populated by users with a tagging service. These are retained across crawls.
Services that populate it:
Tagging
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 62
Tags
Userdefined Namespace Tags
Saved in DB
(reportable)
userdefineddefault
62
IS1200 Metadata Reference Guide— v4.8.0
Indexed
(Searchable)
Comments
Internal use.
The Default Schema and Metadata Tags
Userextracted Namespace
Table 63
Userextracted Namespace
Description
Tags created using extraction rules that are created in GUI by the users.
Services that populate it:
Extraction Ruleset
Assignment Ruleset
Table 64
Userextracted Namespace Tags
Saved in DB
(reportable)
Tags
Indexed
(Searchable)
userextracteddefault
Comments
Internal use.
Version Namespace
Table 65
Version Namespace
Description
Version details of the object
Services that populate it:
Deep, reclassify-action, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 66
Version Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
versionBaseObject
KazURL of base object
versionDate
Date when this version was created
versionId
Version Id of the object
versionName
Version Name
versionParentCasnum
Casnum of base object
The Default Schema and Metadata Tags
63
The Default Schema and Metadata Tags
Namespaces Populated by Rulesets
The metadata tags in the following namespaces are only
populatedwhen a deep classification is run and a specific ruleset
(either extracted or assignment) is specified with the classification.
See the Policies: Extraction and Assignment Rules chapter of the
IS1200 Web-Admin User and Configuration Guide for more details on
rulesets. The required ruleset(s) are noted in the Namespace tables.
64
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Amex Namespace
Table 67
Amex Namespace
Description
Identifies American Express Cards and reports the risk level in their document.
Service populating namespace
Deep, Reclassify-Action
Extraction Ruleset
AmEx
Assignment Ruleset
AmEx
Table 68
Amex Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Amexrisk
Y
Y
Comments
Reported as High, Low, Medium, Unknown depending on number of
occurrences of American Express Card numbers and a combination
of literals 'Confidential' or 'Sensitive' or 'Restricted' in the document.
Centera Namespace
Table 69
Centera Namespace
Description
Metadata of objects in Centera repository.
Service populating namespace
Reclassify, collection-target-indexing, copy-with-target-indexing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 70
Centera Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
centeraClipCreationTime
Y
Y
Creation time of clip in Centera.
centeraClipId
Y
Y
Clip Id assigned by Centera
centeraName
Y
Y
Clip name.
The Default Schema and Metadata Tags
65
The Default Schema and Metadata Tags
DinersClub Namespace
DinersClub Namespace
Table 71
Description
Identifies Diners Club Cards and reports their risk levels in the documents.
Service populating namespace
Deep, Reclassify-Action
Extraction Ruleset
DinersClub
Assignment Ruleset
DinersClub
Table 72
DinersClub Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Dinersclubrisk
Y
Y
Comments
Reported as High, Low, Medium, Unknown depending on
number of occurrences Diners Club Card numbers and a
combination of literals 'Confidential' or 'Sensitive' or 'Restricted'
in the document.
Discover Namespace
Discover Namespace
Table 73
66
Description
Identifies Discover Cards and reports the risk levels in the documents.
Service populating namespace
Deep, Reclassify-Action
Extraction Ruleset
Discover
Assignment Ruleset
Discover
Table 74
Discover Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
discoverrisk
Y
Y
IS1200 Metadata Reference Guide— v4.8.0
Comments
Reported as High, Low, Medium, Unknown depending on number
of occurrences Discover Card numbers and a combination of
literals 'Confidential' or 'Sensitive' or 'Restricted' in the document.
The Default Schema and Metadata Tags
EIN Namespace
EIN Namespace
Table 75
Description
Identifies EINs ( USA Employer Identification Number) and reports the risk levels
in the documents.
Service populating namespace
Deep, Reclassify-Action
Extraction Ruleset
EIN
Assignment Ruleset
EIN
EIN Namespace Tags
Table 76
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
einrisk
Y
Y
Comments
Reported as High, Low, Medium, Unknown depending on number of
occurrences EIN numbers and a combination of literals 'Confidential'
or 'Sensitive' or 'Restricted' or 'Employer Identification Number/No.' or
'EIN#' in the document.
Entity Namespace
Entity Namespace
Table 77
Description
Extracted Concepts/Entities.
Service populating namespace
Deep, reclassify-action, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
conceptfinder
Entity Namespace Tags
Table 78
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Entityaddress
Y
US street addresses roughly in street number, street, city,
state, zip format, or Internet addresses in abc@xyz.com form.
entitycity
Y
Name of a city, including abbreviations for major cities.
entitycompany
Y
Name of a company, organization, or corporation.
Comments
The Default Schema and Metadata Tags
67
The Default Schema and Metadata Tags
Entity Namespace Tags
Table 78
68
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
entityconcepts
Y
entitycountry
Y
Names of countries and abbreviations.
entitycurrency
Y
Quantities of world currency, and ranges of amounts of
currency.
entitydate
Y
Dates minimally composed of a number and month.
entityfacility
Y
Man-made structures, extracted as one of the following
sub-types:
BUILDGROUNDS- Names of architectural and civil
engineering structures, and outdoor spaces that are mainly
man-made or man-maintained. There is no distinction with
respect to their function, they could be civil or military facilities,
they could be used for work, entertainment, or monuments.
entityholiday
Y
Holidays and special days.
entitylanguage
Y
entitymeasure
Y
Any measurement, such as weight, volume, or length, in
English or metric units, including standard abbreviations of
measurement units.
entityorganization
Y
Government, legal, and service agencies, including non-profit
organizations, fine arts groups, and other associations and
institutions.
entitypeoples
Y
Names referring to identifiable groups of people based on
country, ethnicity, race, or religion.
entitypercent
Y
A percentage.
entityperson
Y
An individual specified by name.
entityphone
Y
Phone numbers in US ### ### #### format. International
phone numbers based on French, German, and Spanish
formats.
Y
Comments
Not populated.
entityplace_region Y
A geographical area larger than a city that captures a
significant land mass, such as a continent or a group of
countries
entityproduct
A product name, including software and service-oriented
products.
Y
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Entity Namespace Tags
Table 78
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
entityprop_misc
Y
A proper name that does not fall into any of the entity types
specified by the other entities.
entityssn
Y
Social security number, including Canadian Social Insurance
Numbers and French INSEE Numbers.
entitystate
Y
One of the fifty states of the United States, including standard
abbreviations and two-letter postal codes.
entityticker
Y
Company stock ticker symbols used on the stock exchange.
entitytime
Y
Designations of hours, minutes, and seconds.
entityvehicle
Y
Methods of transportation, extracted as one of the following
sub-types such as AIR, LAND, WATER.
Comments
The Default Schema and Metadata Tags
69
The Default Schema and Metadata Tags
GLBA Namespace
Table 79
Description
Identification of Consumers' Personal Financial Information
Service populating namespace
Deep, Reclassify-Action
Extraction Ruleset
GLBA
Assignment Ruleset
GLBA
Table 80
70
GLBA Namespace
GLBA Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
glbacountamex
Y
glbacountdinersclub
Y
glbacountein
Y
glbacountgenericcc
Y
glbacountitin
Y
glbacountjcb
Y
glbacountmastercard
Y
glbacountnin
Y
glbacountpan
Y
glbacountsin
Y
glbacountssn
Y
glbacountvisa
Y
Glbarisk
Y
glbatypeamex
Y
Updated to 'yes' if a document contains American Express
Card Number.
glbatypeconfidential
Y
Updated to 'yes' if a document contains literal 'Confidential'.
glbatypedinersclub
Y
Updated to 'yes' if a document contains Diners Club Card
Number.
Comments
Y
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Table 80
GLBA Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
glbatypeein
Y
Updated to 'number' or 'literal' or 'both' if a document
contains a literal 'EIN#' or 'Employer Identification Number'
or an EIN number or combination of both.
glbatypegenericcc
Y
Updated to 'yes' if a generic credit card number is found in
the document.
glbatypeinternaluse
Y
Updated to 'yes' if a document contains literal 'Internaluse'.
glbatypeitin
Y
Updated to 'number' or 'literal' or 'both' if a document
contains a literal 'Tax ID#' or 'Tax Identification Number/No.'
or an Tax ID number or combination of both.
glbatypejcb
Y
Updated to 'yes' if the document contains JCB Card
Number.
glbatypemastercard
Y
Updated to 'yes' if the document contains Master Card
Number.
glbatypenin
Y
Updated to 'yes' if the document contains UK National
Insurance Number.
glbatypepan
Y
Updated to 'yes' if the document contains India Permanent
Account Number.
glbatypeproprietary
Y
Updated to 'yes' if a document contains literal 'Properietary'.
glbatyperestricted
Y
Updated to 'yes' if a documented contains literal 'Restricted'.
glbatypesin
Y
Updated to 'yes' if the document contains Canada Social
Insurance Number.
glbatypessn
Y
Updated to 'yes' if the document contains USA Social
Security Number.
glbatypevisa
Y
glbaweight
Y
Comments
The Default Schema and Metadata Tags
71
The Default Schema and Metadata Tags
ITIN Namespace
Table 81
ITIN Namespace
Description
Identifies Tax Payer Identification Numbers and reports the risk levels in the
documents.
Service populating namespace
Deep, reclassify-action
Extraction Ruleset
ITIN
Assignment Ruleset
ITIN
Table 82
ITINNamespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
itinrisk
Y
Y
Comments
Reported as High, Low, Medium, Unknown depending on number of
occurrences ITIN numbers and a combination of literals 'Confidential' or
'Sensitive' or 'Restricted' or 'ITIN' or 'Tax Payer Identification Number/No'
in the document.
JCB Namespace
Table 83
72
JCB Namespace
Description
Identifies JCB Cards and reports the risk levels in the documents.
Service populating namespace
Deep, reclassify-action
Extraction Ruleset
JCB
Assignment Ruleset
JCB
Table 84
JCB Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable) Comments
jcbrisk
Y
Y
IS1200 Metadata Reference Guide— v4.8.0
Reported as High, Low, Medium, Unknown depending on number of
occurrences of JCB Card numbers and a combination of literals
'Confidential' or 'Sensitive' or 'Restricted' in the document.
The Default Schema and Metadata Tags
Master Namespace
Table 85
Master Namespace
Description
Identifies Master Cards and reports the risk levels in the documents.
Services that populate it:
Deep, Reclassify-Action
Extraction Ruleset
Master
Assignment Ruleset
Master
Table 86
Master Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
masterrisk
Y
Y
Comments
Reported as High, Low, Medium, Unknown depending on number of
occurrences of Master Card numbers and a combination of literals
'Confidential' or 'Sensitive' or 'Restricted' in the document.
NIN Namespace
Table 87
NIN Namespace
Description
Identifies UK National Insurance Numbers and reports the risk levels in the
documents.
Services that populate it:
Deep, Reclassify-Action
Extraction Ruleset
NIN
Assignment Ruleset
NIN
Table 88
NIN Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
ninrisk
Y
Y
Comments
Reported as High, Low, Medium, Unknown depending on number of
occurances of UK National Insurance numbers and a combination of
literals 'Confidential' or 'Sensitive' or 'Restricted' in the document.
The Default Schema and Metadata Tags
73
The Default Schema and Metadata Tags
NPI Namespace
Table 89
Description
Identifies Non Public Information in a given document and reports the value.
Note - This namespace is not populated. The namespaces.config does not contain this
namespace.
Services that populate it:
Deep, Reclassify-Action
Extraction Ruleset
NPI
Assignment Ruleset
NPI
Table 90
74
NPI Namespace
NPI Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
npitype
Y
The document to be identified as 'NonPublicInfo' or 'PublicInfo'
depending on the npivalue of the document. The npivalue is
described below.
npivalue
Y
The document has this value populated if it contains one of the
following:
American Express Card #
Discover Card #
Master Card #
Visa Card #
Diners Club Card #
Enroute Card #
JCB Card #
Social Security #
Literals 'Confidential' or 'Sensitive' or 'Proprietary'
Date of Birth
California Drivers License
Customer Account Number
IS1200 Metadata Reference Guide— v4.8.0
Comments
The Default Schema and Metadata Tags
PCI Namespace
Table 91
PCI Namespace
Description
This namespace is not populated. The namespaces.config and ldap do not contain this
namespace.
Services that populate it:
Deep, Reclassify-Action
Extraction Ruleset
PCI
Assignment Ruleset
PCI
Table 92
PCI Namespace Tags
Tags
Saved in DB
(reportable)
PciCountAmEx
Y
PciCountDinersClub
Y
PciCountEIN
Y
PciCountGenericCC
Y
PciCountITIN
Y
PciCountJCB
Y
PciCountMasterCard
Y
PciCountNIN
Y
PciCountPAN
Y
PciCountSIN
Y
PciCountSSN
Y
PciCountVisa
Y
PciRisk
Y
PciTypeAmEx
Y
PciTypeConfidential
Y
PciTypeDinersClub
Y
PciTypeEIN
Y
Indexed
(Searchable)
Comments
The Default Schema and Metadata Tags
75
The Default Schema and Metadata Tags
Table 92
76
PCI Namespace Tags
Tags
Saved in DB
(reportable)
PciTypeGenericCC
Y
PciTypeInternalUse
Y
PciTypeITIN
Y
PciTypeJCB
Y
PciTypeMasterCard
Y
PciTypeNIN
Y
PciTypePAN
Y
PciTypeProprietary
Y
PciTypeRestricted
Y
PciTypeSIN
Y
PciTypeSSN
Y
PciTypeVisa
Y
PciWeight
Y
IS1200 Metadata Reference Guide— v4.8.0
Indexed
(Searchable)
Comments
The Default Schema and Metadata Tags
SIN Namespace
Table 93
SIN Namespace
Description
Identifies Canada Social Insurance Numbers and reports the risk levels in the
documents.
Services that populate it:
Deep, Reclassify-Action
Extraction Ruleset
SIN
Assignment Ruleset
SIN
Table 94
SIN Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
sinrisk
Y
Y
Comments
Reported as High, Low, Medium, Unknown depending on number of
occurrences of Canada Social Insurance numbers and a combination of
literals 'Confidential' or 'Sensitive' or 'Restricted' in the document.
SSNCC Namespace
Table 95
SSNCC Namespace
Description
Identifies Social Security Numbers and Credit Card Numbers and reports the risk
levels in the documents.
Services that populate it:
Deep, Reclassify-Action
Extraction Ruleset
SSNCC
Assignment Ruleset
SSNCC
Table 96
SSNCC Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable) Comments
ssnccrisk
Y
Y
Reported as High, Low, Medium, Unknown depending on number of
occurrences of Social Security Number and Credit Card Numbers
and a combination of literals 'Confidential' or 'Sensitive' or 'Restricted'
or 'SSN#/SS#' or 'Social Security Number/No.' in the document.
The Default Schema and Metadata Tags
77
The Default Schema and Metadata Tags
SSN Namespace
Table 97
SSN Namespace
Description
Identies Social Security Numbers and reports the risk levels in the documents.
Services that populate it:
Deep, Reclassify-Action
Extraction Ruleset
SSN
Assignment Ruleset
SSN
Table 98
SSN Namespace Tags
Saved in DB
(reportable)
Tags
ssnrisk
Indexed
(Searchable)
Y
Comments
Reported as High, Low, Medium, Unknown depending on number of
occurrences of Social Security Number and a combination of literals
'Confidential' or 'Sensitive' or 'Restricted' or 'SSN#/SS#' or 'Social
Security Number/No.' in the document.
Visa Namespace
Table 99
Description
Identifies Visa Cards and reports the risk levels in the documents.
Services that populate it:
Deep, Reclassify-Action
Extraction Ruleset
Visa
Assignment Ruleset
Visa
Table 100
78
Visa Namespace
Visa Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable) Comments
visarisk
Y
Y
IS1200 Metadata Reference Guide— v4.8.0
Reported as High, Low, Medium, Unknown depending on number of
occurrences of Visa Card numbers and a combination of literals
'Confidential' or 'Sensitive' or 'Restricted' in the document.
The Default Schema and Metadata Tags
Namespaces Populated by Optional Module Connectors
The metadata tags in the following namespaces are only populated
when a specific Optional Module Connector license is installed and a
deep classification is run on a data repository accessed by that
optional module. See the Optional Modules section of the Introduction
chapter of the IS1200 Web-Admin User and Configuration Guide for
more details on optional modules. The name of the Namespace table
indicates the Optional Module Connector required to extract these
namespaces and tags.
The Default Schema and Metadata Tags
79
The Default Schema and Metadata Tags
Atmoscloud Namespace
Table 101
Atmoscloud Namespace
Description
Atmos Cloud information tags
Service populating namespace
Deep, reclassify, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 102
Atmoscloud Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
AtmosCloudGroup
Y
Y
Alias for Group id (GID) of the object
AtmosCloudObjectId
Y
Y
Alias for the Object id in Atmos
AtmosCloudObjectName
Y
Y
Alias for the name of the object (filename or
directory) in
Atmos
AtmosCloudOwner
Y
N
Alias for the User id (UID) of the owner of the object
AtmosCloudPolicyName
Y
Y
Alias for the name of the policy under which the
system stores an object.
AtmosCloudType
Y
Y
Alias for the type of object defined as follows:
• Regular: applicable for files or objects
• Directory: applicable for directories
Centera Namespace
Table 103
80
Centera Namespace
Description
Metadata of objects in Centera repository.
Service populating namespace
Reclassify, collection-target-indexing, copy-with-target-indexing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Table 104
Centera Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
centeraClipCreationTime
Y
Y
Creation time of clip in Centera.
centeraClipId
Y
Y
Clip Id assigned by Centera
centeraName
Y
Y
Clip name.
CSVC Documentum Namespace
Table 105
CSVC Documentum Namespace
Description
Metadata captured for objects in Documentum repository.
Service populating namespace
Deep, reclassify, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 106
CSVC Documentum Namespace Tags
Tag
Saved in DB
(Reportable)
Indexed
(Searchable)
CSVC_EMC_DocumentumIsUnderRetention
Y
N
Check if a particular document is under
retention or no.
CSVC_EMC_DocumentumIsOnHold
Y
N
Check if the document is on hold or no.
CSVC_EMC_DocumentumHold
Y
N
The hold value.
CSVC_EMC_DocumentumTitle
Y
Y
Title of the object. This is user-defined.
CSVC_EMC_DocumentumSubject
Y
Y
Subject of the object. This is user-defined.
CSVC_EMC_DocumentumAuthors
Y
Y
List of the authors for the object
CSVC_EMC_DocumentumKeywords
Y
Y
List of user-defined keywords for the object
CSVC_EMC_DocumentumApplicationType
Y
N
CSVC_EMC_DocumentumStatus
Y
N
Comments
The Default Schema and Metadata Tags
81
The Default Schema and Metadata Tags
Table 106
82
CSVC Documentum Namespace Tags
Tag
Saved in DB
(Reportable)
Indexed
(Searchable)
Comments
CSVC_EMC_DocumentumModifier
Y
Y
Name of the user who made last modification
CSVC_EMC_DocumentumIsHidden
Y
N
Check whether an object is hidden or no.
CSVC_EMC_DocumentumIsDeleted
Y
N
If the object is the root version of a version
tree, deleting the object sets this attribute to
TRUE.
CSVC_EMC_DocumentumArchive
Y
N
CSVC_EMC_DocumentumCompoundArchitectu
re
Y
N
CSVC_EMC_DocumentumLinkResolved
Y
N
CSVC_EMC_DocumentumReferenceCount
Y
N
CSVC_EMC_DocumentumHasFolder
Y
N
CSVC_EMC_DocumentumFolderId
Y
N
CSVC_EMC_DocumentumLinkCount
Y
N
CSVC_EMC_DocumentumLinkHighCount
Y
N
CSVC_EMC_DocumentumAssembledFromId
Y
N
CSVC_EMC_DocumentumFrznAssemblyCount
Y
N
CSVC_EMC_DocumentumHasFrznAssembly
Y
N
CSVC_EMC_DocumentumResolutionLabel
Y
N
CSVC_EMC_DocumentumIsvirtualDoc
Y
N
CSVC_EMC_DocumentumContentsId
Y
N
CSVC_EMC_DocumentumContentType
Y
N
File format in which to display the contents of
the object attached to the task. (Note that
this may be different than the content type
specified for the object.)
CSVC_EMC_DocumentumPageCount
Y
N
Number of content files associated with the
object.
IS1200 Metadata Reference Guide— v4.8.0
Folder ID
SysObject is a virtual document. If the value
is 1, the object is a virtual document. If the
value is 0, the object is not a virtual
document unless the r_link_cnt is greater
than 0.
The Default Schema and Metadata Tags
Table 106
CSVC Documentum Namespace Tags
Tag
Saved in DB
(Reportable)
Indexed
(Searchable)
CSVC_EMC_DocumentumFullText
Y
N
CSVC_EMC_DocumentumStorageType
Y
N
CSVC_EMC_DocumentumCabinetId
Y
N
ID of the cabinet
CSVC_EMC_DocumentumOwner
Y
Y
Name of the object’s owner. This can be a
user or group name.
CSVC_EMC_DocumentumOwnerPermit
Y
N
Object-level permission assigned to the
owner for this object.
CSVC_EMC_DocumentumGroup
Y
N
Group to which this object belongs.
CSVC_EMC_DocumentumGroupPermit
Y
N
CSVC_EMC_DocumentumWorldPermit
Y
N
CSVC_EMC_DocumentumAntecedentId
Y
N
CSVC_EMC_DocumentumChronicleId
Y
N
CSVC_EMC_DocumentumLatestFlag
Y
N
CSVC_EMC_DocumentumLockOwner
Y
N
CSVC_EMC_DocumentumLockDate
Y
N
CSVC_EMC_DocumentumLockMachine
Y
N
CSVC_EMC_DocumentumLogEntry
Y
N
CSVC_EMC_DocumentumBranchCount
Y
N
CSVC_EMC_DocumentumDirectDsc
Y
N
CSVC_EMC_DocumentumImmutableFlag
Y
N
CSVC_EMC_DocumentumFrozenFlag
Y
N
CSVC_EMC_DocumentumHasEvents
Y
N
CSVC_EMC_DocumentumAclDomain
Y
N
Identifies the domain of the ACL associated
with the object.
CSVC_EMC_DocumentumAclName
Y
N
The object name of the associated ACL.
CSVC_EMC_DocumentumSpecialApp
Y
N
Comments
Comments specified by the user.
The Default Schema and Metadata Tags
83
The Default Schema and Metadata Tags
Table 106
84
CSVC Documentum Namespace Tags
Tag
Saved in DB
(Reportable)
Indexed
(Searchable)
CSVC_EMC_DocumentumIsreference
Y
N
CSVC_EMC_DocumentumCreatorName
Y
Y
CSVC_EMC_DocumentumIspublic
Y
N
CSVC_EMC_DocumentumPolicyId
Y
N
CSVC_EMC_DocumentumResumeState
Y
N
CSVC_EMC_DocumentumCurrentState
Y
N
CSVC_EMC_DocumentumAliasSetId
Y
N
CSVC_EMC_DocumentumEffectiveDate
Y
N
CSVC_EMC_DocumentumExpirationDate
Y
N
CSVC_EMC_DocumentumPublishFormats
Y
N
CSVC_EMC_DocumentumEffectiveLabel
Y
N
CSVC_EMC_DocumentumEffectiveFlag
Y
N
CSVC_EMC_DocumentumCategory
Y
N
CSVC_EMC_DocumentumLanguageCode
Y
N
CSVC_EMC_DocumentumIstemplate
Y
N
CSVC_EMC_DocumentumControllingApp
Y
N
CSVC_EMC_DocumentumFullContentSize
Y
N
CSVC_EMC_DocumentumExtendedProperties
Y
N
CSVC_EMC_DocumentumIsSigned
Y
N
CSVC_EMC_DocumentumLastReviewDate
Y
N
CSVC_EMC_DocumentumRetainUntil
Y
Y
CSVC_EMC_DocumentumAspectName
Y
N
IS1200 Metadata Reference Guide— v4.8.0
Comments
Attributes are either:
• The value of the relation_name attribute
in a dm_relation object or subtype of a
dm_relation.
• Room ID
Most restrictive retention date among all
content associated with this object.
The Default Schema and Metadata Tags
Table 106
CSVC Documentum Namespace Tags
Tag
Saved in DB
(Reportable)
Indexed
(Searchable)
CSVC_EMC_DocumentumPartition
Y
N
CSVC_EMC_DocumentumIsreplica
Y
N
CSVC_EMC_DocumentumVStamp
Y
N
CSVC_EMC_DocumentumVersion
Y
Y
Version number (first version of version
label).
CSVC_EMC_DocumentumObjectID
Y
Y
Document ID assigned by DCTM
Comments
CSVC SharePoint Namespace
Table 107
Table 108
SharePoint Namespace
Description
Metadata captured for objects in SharePoint repository
Services that populate it:
Deep, Reclassify-Action,
collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing,
in-place-processing
Extraction Ruleset
n/a
Assignment Ruleset
n/a
CSVC SharePoint Namespace Tags
Tag
Saved in DB
(Reportable)
Indexed
(Searchable)
CSVC_EMC_SharePointIsLeafObject
Y
N
An object that is not a directory or a
folder.
CSVC_EMC_SharePointSize
Y
N
Content size
CSVC_EMC_SharePointIsUnderRetention
Y
N
Whether an object is under retention or
no.
CSVC_EMC_SharePointRetentionClass
Y
N
The name of the retention class.
Comments
The Default Schema and Metadata Tags
85
The Default Schema and Metadata Tags
Table 108
86
CSVC SharePoint Namespace Tags
Tag
Saved in DB
(Reportable)
Indexed
(Searchable)
Comments
CSVC_EMC_SharePointIsOnHold
Y
N
Whether an object is on hold or no.
CSVC_EMC_SharePointHold
Y
N
Provides the Hold value.
CSVC_EMC_SharePointAuthor
Y
Y
Name of the user who created the
document in SharePoint
CSVC_EMC_SharePointOwners
Y
N
List ofSharePoint owners.
CSVC_EMC_SharePointOwner
Y
Y
Name of the object’s owner. This can be
a user or group name.
CSVC_EMC_SharePointCreator
Y
Y
User ID of the form domain\userid
CSVC_EMC_SharePointModifier
Y
Y
Name of the user who made last
modification
CSVC_EMC_SharePointEditor
Y
Y
CSVC_EMC_SharePointAllowAnonymousAccess
Y
N
CSVC_EMC_SharePointDescription
Y
N
Description of the SharePoint object
CSVC_EMC_SharePointLocale
Y
N
Locale of the object.
CSVC_EMC_SharePointTitle
Y
N
Title of the object. This is user-defined.
CSVC_EMC_SharePointDisplayName
Y
N
Name displayed on the SharePoint
server.
CSVC_EMC_SharePointVersion
Y
Y
Version number of the document
CSVC_EMC_SharePointObjectID
Y
Y
Document ID assigned by SharePoint
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Directory Namespace
Directory Namespace
Table 109
Description
Namespace that populates up to first five directory names of a file path
Service populating namespace
Basic, Deep, Reclassify-Action
Extraction Ruleset
n/a
Assignment Ruleset
DirectoryReporting
Directory Namespace Tags
Table 110
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
directorydir1
Y
First directory in the file path (if it exists)
directorydir2
Y
Second directory in the file path (if it exists)
directorydir3
Y
Third directory in the file path (if it exists)
directorydir4
Y
Fourth directory in the file path (if it exists)
directorydir5
Y
Fifth directory in the file path (if it exists)
Comments
Domino Namespace
Domino Namespace
Table 111
Description
Metadata attributes related to Domino.
Service populating namespace
Deep, reclassify, collection-with-source-fulltext-indexing, in-place-processing
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Domino Namespace Tags
Table 112
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
DominoMailbox
Y
Y
The mail box of the domino user.
The Default Schema and Metadata Tags
87
The Default Schema and Metadata Tags
Dumpster Namespace
Table 113
Dumpster Namespace
Description
The dumpster information of an email object.
Service populating namespace
Deep, Reclassify-Action, collection-with-source-fulltext-indexing,
in-place-processing
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 114
Dumpster Namespace Tags
Saved in DB
(reportable)
Tags
Indexed
(Searchable)
dumpstermail
Comments
Values [yes|no]. The value is set to 'yes' when the object is
stored in the dumpster and vice versa.
EnterpriseVault Namespace
Table 115
Description
Metadata captured for objects in Enterprise Vault repository.
Service populating namespace
Deep, reclassify-action, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 116
88
EnterpriseVault Namespace
EnterpriseVault Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable) Comments
enterprisevaultAuthor
Y
Y
Author of item (Sender for e-mail
messages)
enterprisevaultLegalHolds
Y
Y
Legal Hold Id, if legal hold has been set for
the object
enterprisevaultOriginalLocation
Y
IS1200 Metadata Reference Guide— v4.8.0
Original object location or mailbox name
The Default Schema and Metadata Tags
Table 116
EnterpriseVault Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable) Comments
enterprisevaultRetentionCategoryId
Y
enterprisevaultTitle
Y
Y
Title in Enterprise Vault
enterprisevaultVaultname
Y
Y
Archive name in Enterprise Vault
Identifier of Retention Category in
Enterprise Vault
The Default Schema and Metadata Tags
89
The Default Schema and Metadata Tags
Exchange Namespace
Exchange Namespace
Table 117
Description
The metadata attributes related to Exchange.
Service populating namespace
Deep, reclassify-action, collection-with-source-fulltext-indexing,
in-place-processing
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 118
Exchange Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
Comments
ExchangeMailbox
Y
Y
The mail box of the exchange account.
NSF Namespace
Table 119
NSF Namespace
Description
Service populating namespace Deep, reclassify, collection-with-source-fulltext-indexing,
collection-target-indexing, copy-with-target-indexing, in-place-processing
Extraction Ruleset
fulltext (rule)
Assignment Ruleset
n/a
Table 120
90
NSF Namespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
NSFDocument
Y
Y
NSFISLooseDXL
Y
Y
IS1200 Metadata Reference Guide— v4.8.0
Comments
The Default Schema and Metadata Tags
Sourceonearchive Namespace
Table 121
SourceonearchiveNamespace
Description
Metadata captured for objects in SourceOne Archive repository
Services that populate it:
Deep, Reclassify-Action, collection-with-source-fulltext-indexing, in-place-processing
Extraction Ruleset
n/a
Assignment Ruleset
n/a
Table 122
SourceonearchiveNamespace Tags
Tags
Saved in DB
(reportable)
Indexed
(Searchable)
SourceOneArchiveFolderName
Y
Y
SourceOne Business Folder
Name
SourceOneArchiveMetaDataModificationTime
Y
N
Metadata Modification Time (for
Kazeon internal use)
SourceOneArchiveOwner
Y
Y
List of owners for archived
e-mails
SourceOneArchiveFileName
Y
Y
Filename of a SourceOne
archived object
SourceOneArchiveObjectType
Y
Y
Type of objects in SourceOne
archive
SourceOneArchiveOriginalFileLocation
Y
N
Location of file objects from
where it’s been archived in
SourceOne
SourceoneArchiveFileVersion
Y
N
File version of a Sharepoint
object
SourceoneArchiveOriginalOwner
Y
N
The intersection of owner filter
with all owners from SourecOne
archive.If no owner filter is
specified then the value will be
all owners belonging to an object
in SourceOne
Comments
The Default Schema and Metadata Tags
91
The Default Schema and Metadata Tags
Alphabetic Listing of Indexed Default Metadata Tags:
Not all default tags are automatically indexed, only those that contain
the key word “indexed”in the Schema, see “Types of Attributes for
‘set_schema’ CLI Command” on page 8 for details.
The following columns list all default metadata tags that contain the
“indexed” keyword.
Table 123
92
Alphabetic Listing of Indexed Default Metadata Tags
amexrisk
centeraClipCreationTime
centeraClipId
centeraName
ContactFullName
ContactNickname
detectedalternates
detectedlanguage
dinersclubrisk
discoverrisk
DocumentAuthor
DocumentCategory
DocumentCompany
DocumentCreationDate
DocumentDescription
DocumentEditor
DocumentLanguage
DocumentLastSavedBy
DocumentManager
DocumentOwner
DocumentProject
DocumentPublisher
DocumentSource
DocumentSubject
DocumentTitle
documentumAuthors
documentumKeywords
documentumOwnerName
documentumRetainUntil
documentumSubject
documentumTitle
DominoMailbox
dumpstermail
einrisk
enterprisevaultAuthor
enterprisevaultLegalHolds
enterprisevaultTitle
enterprisevaultVaultname
entitylanguage
EnvcommonMtime
EnvcommonRepositorytype
ExchangeMailbox
glbarisk
HierarchyDisplayObjectType
HierarchyErrorMessage
HierarchyFileName
HierarchyFolderName
InheritedMailBccLevel1
InheritedMailBccLevel2
InheritedMailBccLevel3
InheritedMailCcLevel1
InheritedMailCcLevel2
InheritedMailCcLevel3
InheritedMailFromLevel1
InheritedMailFromLevel2
InheritedMailFromLevel3
InheritedMailReceivedLevel
InheritedMailReceivedLevel2
InheritedMailReceivedLevel3
InheritedMailSubjectLevel1
InheritedMailSubjectLevel2
InheritedMailSubjectLevel3
InheritedMailToLevel1
IS1200 Metadata Reference Guide— v4.8.0
The Default Schema and Metadata Tags
Table 123
Alphabetic Listing of Indexed Default Metadata Tags
InheritedMailToLevel2
InheritedMailToLevel3
itinrisk
jcbrisk
KazcollectionRuleName
KazeonConfidential
KazeonExtDate
Kazeoninternaluseonly
KazeonPostalCode
KazeonPrice
KazeonSocialSecurityNumber
KazeonStockSymbol
KazeonTelephoneNumber
KazeonUri
legalappCase
legalappLastReviewedBy
legalappLastReviewedDate
legalappNotes
legalappReviewedAs
legalappReviewer
legalappTag
legalholdlegalholdenforcefs
legalholdexecutor
legalholdtime
legalholdtype
MailAttachment
MailBcc
MailCc
MailConversationTopic
MailDate
MailDerivedDirection
MailDerivedDirectionInheritedLevel1
MailDerivedDirectionInheritedLeve
l2
MailDerivedDirectionInheritedLevel3
MailDerivedFromDomain
MailDerivedFromDomainInheritedLevel2
MailDerivedFromDomainInheritedLevel3
MailDerivedRecipientDomain
MailDerivedRecipientDomainInheritedLevel1
MailDerivedRecipientDomainInheritedLevel2
MailDerivedRecipientDomainInher
itedLevel3
MailEmail
MailFrom
MailMessageClass
MailMessageId
MailReceived
MailSize
MailSubject
MailTo
masterrisk
ninrisk
ObjcommonMtime
OriginalsourceAdHocTag
OriginalsourceCustodian
OriginalsourceDocId
OriginalsourceLocation
PersistentNameSpaceLegalCaseNum
processingservicename
retentionsetusersharepointAuthor
sharepointCreatedBy
sharepointEditorsharepointModifiedBysinrisk
SourceOneArchiveFolderNamess
nccrisk
ssnrisk
SystemAtime
SystemCasid
SysemFullText
SystemGroupName
SystemLastSeenTime
SystemCasidV
SystemCreationTime
SystemCTime
SystemEndVersionTime
SystemFileExtension
SystemFilepath
The Default Schema and Metadata Tags
93
The Default Schema and Metadata Tags
Table 123
Alphabetic Listing of Indexed Default Metadata Tags
SystemFilerName
SystemFileSize
SystemFileType
SystemMtime
SystemObjectName
SystemObjectType
SystemOwnerName
SystemPolicyGroups
SystemRetentionTime
SystemSnaplocked
SystemSnaplockTime
SystemSsHasBeenDeleted
SystemStartVersionTime
SystemTypeExtension
SystemUniqueDocumentID
TaskSubject
TIFFArtist
TIFFImageDescription
visarisk
94
IS1200 Metadata Reference Guide— v4.8.0
3
Metadata Mapping
Data repositories that the IS1200 accesses using and Optional Module
Connector maintain unique server-specific metadata beyond the
standard file metadata maintained by NFS and CIFS servers.
Additionally, some of these servers also allow users and applications
to define and maintain custom metadata. This chapter explains how
to set up mapping files that allow the IS1200 to capture and retrieve
the standard server-specific, as well as the user or application defined
metadata in the standard IS1200 metadata repositories.
Topics include:
◆
◆
◆
◆
◆
◆
◆
Background .........................................................................................
Creating a Mapping File to Capture OMR Custom Attributes ...
Identifying the OMR Custom Attributes........................................
Identifying and Creating the IS1200 Metadata Tags to Map To ..
Obtaining the Mapping Template from the IS1200 .......................
Editing and Saving the Mapping File .............................................
Mapping File Naming and Syntax ..................................................
Metadata Mapping
96
97
97
97
98
98
99
95
Metadata Mapping
Background
All IS1200 installations can register, classify, as well as search and
report on NFS and CIFS data repositories. If the appropriate Optional
Module license is installed, and properly setup and configured, the
IS1200 may also work with a variety of other servers, or data
repositories. Examples include, Microsoft Exchange or SharePoint
servers, EMC Centera or Documentum servers, Lotus Domino, etc. In
this guide, these Optional Module Repositories (servers), are referred
to as OMR.
Some OMR the IS1200 can work with save a pre-defined, but
server-specific, set of metadata for each file they store. While this
metadata is often unique to the server type, it is standard for that server,
and the IS1200 automatically captures this standard server-specific
metadata by default once the appropriate Optional Module license is
installed, and the module setup and configuration is completed. For
these servers, the Optional Module or Connector user guide that
describes them, also contains a section that lists the standard
server-specific metadata automatically classified for that server.
Additionally, some of these OMR allow users or applications to
define additional custom metadata, or attributes, for the files they
store. For example, SharePoint users can use site columns or column
properties to create new SharePoint metadata or custom properties.
See your Microsoft SharePoint Server User Guide for more details.
This server-specific custom metadata may also be automatically
collected during Kazeon classifications by creating a metadata mapping
file. The mapping file allows the custom metadata to be indexed in
the IS1200 search schema, and allows users to search registered OMR
for this custom metadata using the Web-Search application.
A template for the metadata mapping file is provided on all standard
IS1200 installations. Once modified, and saved with the correct
mapping filename, the IS1200 automatically uses the mapping file to
extract the custom metadata during classifications of OMR.
The mapping file lists the names of all OMR custom-defined
metadata you want collected classified and associates each with a
Kazeon metadata field defined in the Metadata Schema. See “The
Metadata Schema and Tag Management” on page 1 for details on
adding custom metadata fields and namespaces to the IS1200
Metadata Schema. Additionally, the mapping file can define how to
96
IS1200 Metadata Reference Guide— v4.8.0
Metadata Mapping
reverse the process when copying or moving files to an OMR
repository (i.e. it can specify what IS1200 metadata to copy into what
OMR custom metadata fields.)
The following sections describe how to create a mapping file. Once a
mapping file is created and copied to the IS1200, OMR custom
metadata is automatically collected and indexed during subsequent
IS1200 classifications.
Creating a Mapping File to Capture OMR Custom Attributes
The following general steps are required to create a mapping file:
1. Identify the OMR metadata to be captured during IS1200
classifications.
2. Identify the IS1200 metadata tags each OMR metadata attribute
will be mapped to.
3. Obtain the Kazeon IS1200 mapping file template from your
IS1200 server.
4. Edit a copy of the template, to add the appropriate mappings, and
then save it on the IS1200.
When saved with an appropriate mapping file name, the IS1200
automatically begins using the mapping file for all subsequent
classifications.
Identifying the OMR Custom Attributes
The list of standard and custom OMR-specific metadata is usually
defined when the OMR Connector is installed, specifically, when the
recommended configuration lists for that OMR are filled out as part
of the OMR installation and configuration process. See the
appropriate OMR connector user guide for it’s configuration list.
If this list was not made, contact your OMR administrator for a list of
custom attributes—and their OMR names—for your OMR server.
Identifying and Creating the IS1200 Metadata Tags to Map To
Each OMR metadata attribute must have a specific IS1200 metadata
tag to map to. If the IS1200 metadata tags do not already exist, they
must be created.
Metadata Mapping
97
Metadata Mapping
Make a list of the OMR metadata attributes you want to extract, and
then identify the IS1200 metadata tag to map it to.
◆
If the IS1200 metadata tags do no already exist, create them using
the procedures described in “The Metadata Schema and Tag
Management” on page 1.
◆
Make sure the field type of each Kazeon metadata tag matches the
OMR metadata type that will be mapped to it.
◆
If necessary, create IS1200 namespaces to contain the new IS1200
metadata tags, see the procedures described in the “The
Metadata Schema and Tag Management” on page 1.
Obtaining the Mapping Template from the IS1200
A template for creating a new mapping file is automatically saved to
your IS1200 server when the IS1200 software is installed. To access
this file:
1. Logon to the IS1200
2. Move a copy of the file:
/opt/openkaz/config/repository_tag_map_template.xm
to someplace you can edit it.
Note: DO NOT edit the original template file. Edit a copy.
Editing and Saving the Mapping File
Open the template file copy obtained in the step above and edit it to
add the mappings. When the edits are finished, save it as:
/opt/openkaz/config/sharepoint_custom_map.xml.
For multi-node clusters, this file must be saved on all cluster nodes.
Edit your template file as shown in the example below, and keeping
in mind the syntax described in the following section.
Example:
To extract Sharepoint custom attributes ‘sharePointProp1’ and
‘sharePointProp2’ during a classification and map them to IS1200
metadata tags ‘tag1’in namespace ‘Kazeon’ and ‘tag2’ in
namespace ‘custom’.
98
IS1200 Metadata Reference Guide— v4.8.0
Metadata Mapping
And, during copies from an IS1200 registered repository to a
SharePoint repository, to copy IS1200 metadata values with the tag
‘KazeonTag1’ and ‘CustomTag4’ to the SharePoint metadata attributes
‘prop3’ and ‘prop4’,
Unless, ‘CustomTag4’ was not applied to a file, then set it to default
value of ‘this-is-default’
<MetadataMap>
<Maps RepositoryType = "sharepoint" Operation = "crawl">
<Map RepositoryTagName = "sharepointProp1"
RepositoryDataType = "Text"
KazeonTagName = "kazeontag1"
multivalued = "no" />
<Map RepositoryTagName = " sharepointProp2"
RepositoryDataType = "Text"
KazeonTagName = "customtag2"
multivalued = "no" />
</Maps>
<!-- Mapping used during copy to repository (operation = "copy") -->
<Maps RepositoryType = "sharepoint" Operation = "copy">
<Map RepositoryTagName = "prop3"
KazeonTagName = "KazeonTag3"
<Map RepositoryTagName = "prop4"
KazeonTagName = "CustomTag4"
RepositoryDataType = "Text"
<Map RepositoryTagName = "prop5"
/>
defaultValue = "this-is-default" />
KazeonTagName = "kazeontag5"
RepositoryDataType = "Integer"
multivalued = "no" />
</Maps>
</MetadataMap>
Mapping File Naming and Syntax
When creating a custom mapping file, the filename should be:
/opt/openkaz/config/<OMR_Name>_custom_map.xml
where <OMR_Name> is the name of the OMR server type.
For examples:
For SharePoint:
/opt/openkaz/config/sharepoint_custom_map.xml
For Documentum:
/opt/openkaz/config/documentum_custom_map.xml
The custom mapping file can be validated using:
Metadata Mapping
99
Metadata Mapping
/opt/openkaz/bin/repomdmap <map-file-name>
For example:
/opt/openkaz/bin/repomdmap/opt/openkaz/config/sharepoint
_custom_map.xml
Use the following syntax, when creating a mapping file.
Description of XML tags and attributes:
================================================
Attributes of 'Maps'
=================================
1. RepositoryType :
(required)
'sharepoint' - for SharePoint
'documentum' - for Documentum
2.
Operation:
(required)
Possible values:
a) crawl
b) copy
Attributes of 'Map'
=================================
1. RepositoryTagName :
(required)
This is the name of attribute in repository
(SharePoint column name, Documentum attribute)
2. KazeonTagName :
(required)
3. DefaultValue: (optional)
This value will be used in copy operation, if KazeonTag is
not available for the object
4. RepositoryDataType:
(optional)
Valid values:
a) Text
b) Integer
c) DateTime
100
IS1200 Metadata Reference Guide— v4.8.0
Metadata Mapping
d) Boolean
e) Decimal
If not specified, default is 'Text'
5. multivalued: (optional)
Indicates that repository tag is multi valued tag
Possible values:
a)
yes
: if this is multivalued attribute
b)
no
: if this is single valued attribute
Default: 'no'
Default Connector Metadata Mappings
The following tables list the default mappings used between the
IS1200 and various connector-accessed repositories (such as Centera,
SharePoint, etc.) when coping data from an IS1200 data repository to
a connector-accessed data repository. The tables show what metadata
fields from the source repository are copied to what metadata fields
on the target repository.
For example, in Table 126, “Centera Default Metadata Mappings,” on
page 104 below, when doing a copy to a Centera repository, if you
read across any row in the table (for example the first row, atime):
◆
The first column specifies the metadata field on the target (in this
case a Centera metadata repository) the source metadata will be
copied to, and
◆
Columns NFS (3rd) - EV (10th) tell you what metadata field from
a particular source (specified by the column heading) will be
copied into that target metadata field.
Metadata Mapping
101
Metadata Mapping
NFS Default Metadata Mappings
Table 124
NFS Default Metadata Mappings
IS1200 Metadata Creation on copy/collection into NFS repository
Source Repository IS1200 Tags or Sources
Target IS1200
Tags
102
NFS
CIFS
Centera
Documentu
m
Exchange
Sharepoint
Domino
EV
atime
atime
atime
atime
atime
atime
atime
atime
atime
mtime
mtime
mtime
mtime
mtime
mtime
mtime
mtime
amtime
ctime
Set by
system.
Captured
in
metadata
ctime
N/A
N/A
N/A
N/A
N/A
N/A
N/A
creationtime
Not
Applicable
creationtime
N/A
N/A
N/A
N/A
N/A
N/A
N/A
owner
owner
owner (uid)
owner
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
group
group
group (gid)
group
Not Preserved
Not Preserved
Not Preserved
b
Not Preserved
OriginalSource
Tags
OriginalSource OriginalSource
Tags
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
IS1200 Metadata Reference Guide— v4.8.0
Metadata Mapping
CIFS Default Metadata Mappings
Table 125
CIFS Default Metadata Mappings
IS1200 Metadata Creation on copy/collection into CIFS repository
Source Repository IS1200 Tags or Sources
Target IS1200
Tags
NFS
CIFS
Centera
Documentum
Exchange
Sharepoint
Domino
EV
atime
atime
atime
atime
atime
atime
atime
atime
atime
mtime
mtime
mtime
mtime
mtime
mtime
mtime
mtime
mtime
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
creationtime
Not Preserved
Not Preserved
Not Preserved
creation time
Not Preserved
archive time
ctime
Set by
system.
Captured in
metadata
creationtime
owner
Same as
object
owner
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
group
Same as
object
group
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
cifs owner
UID
cifs owner
Not Preserved
Not Preserved
Mailbox User
Sharepoint
owner
MailBox User
Not Preserved
cifs group
GUI
cifs owner
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
OriginalSource
Tags
OriginalSource OriginalSource
Tags
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
Metadata Mapping
103
Metadata Mapping
Centera Default Metadata Mappings
Centera Default Metadata Mappings
Table 126
IS1200 Metadata Creation on copy/collection into Centera repository
Source Repository IS1200 Tags or Sources
Target IS1200
Tags
CIFS
Centera
Documentum
Exchange
Sharepoint
Domino
EV
atime
Copied
from source
object
atime
atime
atime
atime
atime
atime
atime
atime
mtime
Copied
from source
object
mtime
mtime
mtime
mtime
mtime
mtime
mtime
mtime
ctime
Copied
from source
object
ctime
ctime
ctime
ctime
ctime
ctime
ctime
ctime
creationtime
Copied
from source
object
creationtime
creationtime
creationtime
creationtime
creationtime
creationtime
creationtime
creationtime
owner
root (don't
use)
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
group
root (don't
use)
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
cifs owner
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
cifs group
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
OriginalSource OriginalSource
Tags
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
Assigned by
Centera
Assigned by
Centera
Assigned by
Centera
Assigned by
Centera
Assigned by
Centera
Assigned by
Centera
Assigned by
Centera
OriginalSource
Tags
centeraClipId
104
NFS
Preserved
Assigned by
Centera
IS1200 Metadata Reference Guide— v4.8.0
Metadata Mapping
Table 126
Centera Default Metadata Mappings
IS1200 Metadata Creation on copy/collection into Centera repository
atime
Copied
from source
object
atime
atime
atime
atime
atime
atime
atime
atime
mtime
Copied
from source
object
mtime
mtime
mtime
mtime
mtime
mtime
mtime
mtime
ctime
Copied
from source
object
ctime
ctime
ctime
ctime
ctime
ctime
ctime
ctime
Metadata Mapping
105
Metadata Mapping
Enterprise Vault (EV) Default Metadata Mappings
Enterprise Vault (EV) Default Metadata Mappings
Table 127
IS1200 Metadata Creation on copy/collection into EV repository
Source Repository IS1200 Tags or Sources
Target IS1200
Tags
106
NFS
CIFS
Centera
Documentum
Exchange
Sharepoint
Domino
EV
atime
Set to
Not Preserved
archive time
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
mtime
Source
Object's
mtime is
preserved
mtime
mtime
mtime
mtime
mtime
mtime
mtime
mtime
ctime
Archive
Time
assigned by
EV
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
creationtime
Archive
Time
assigned by
EV
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
owner
root (don't
use)
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
group
root (don't
use)
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
OriginalSource
Tags
Preserved
OriginalSource OriginalSource
Tags
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
enterprisevault
RetentionCateg
oryId
Selected by
user
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
IS1200 Metadata Reference Guide— v4.8.0
Metadata Mapping
Table 127
Enterprise Vault (EV) Default Metadata Mappings
IS1200 Metadata Creation on copy/collection into EV repository
enterprisevaultL
egalHolds
Holde Id (if
applicable)
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
enterprisevaultA Owner of
uthor
Source
Object
owner
owner
owner
owner
owner
owner
owner
owner
enterprisevaultT
itle
File name
File name
File name
File name
File name
File name
File name
File name
enterprisevault
Directory of
OriginalLocation Source File
Directory
name
Directory
name
Directory
name
Directory name
Directory name Directory
name
Directory name Directory
name
enterprisevaultV Selected by
aultname
user
N/A
N/A
N/A
N/A
N/A
N/A
Source File
Name
N/A
N/A
Metadata Mapping
107
Metadata Mapping
SharePoint Default Metadata Mappings
Table 128
SharePoint Default Metadata Mappings
IS1200 Metadata Creation on copy/collection into Sharepoint repository
Source Repository IS1200 Tags or Sources
Documentu
m
Exchange
Sharepoint
Domino
EV
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Object
creation
time in
SharePoint
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
owner
User-id
used for
repository
registration
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
group
id used for
repository
registration
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
OriginalSource Tags
Preserved
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
Target IS1200 Tags
108
Action
NFS
CIFS
atime
Object
creation
time in
SharePoint
Not Preserved
Not Preserved
mtime
Object
modifictaion
time in
SharePoint
Not Preserved
ctime
Object
creation
time in
SharePoint
creationtime
IS1200 Metadata Reference Guide— v4.8.0
Centera
Metadata Mapping
Table 128
SharePoint Default Metadata Mappings
IS1200 Metadata Creation on copy/collection into Sharepoint repository
sharepointURL
Assigned by
SharePoint
N/A
N/A
N/A
N/A
N/A
Not Preserved
N/A
N/A
sharepointVersion
Assigned by
SharePoint
N/A
N/A
N/A
N/A
N/A
Not Preserved
N/A
N/A
sharepointCheckoutBy
Empty
N/A
N/A
N/A
N/A
N/A
Not Preserved
N/A
N/A
sharepointModifiedBy
id used for
repository
registration
N/A
N/A
N/A
N/A
N/A
Not Preserved
N/A
N/A
sharepointCreatedBy
id used for
repository
registration
N/A
N/A
N/A
N/A
N/A
Not Preserved
N/A
N/A
sharepointAuthor
id used for
repository
registration
N/A
N/A
N/A
N/A
N/A
Not Preserved
N/A
N/A
sharepointEditor
id used for
repository
registration
N/A
N/A
N/A
N/A
N/A
Not Preserved
N/A
N/A
sharepointMimeType
Assigned by
SharePoint
N/A
N/A
N/A
N/A
N/A
Not Preserved
N/A
N/A
Metadata Mapping
109
Metadata Mapping
Documentum Default Metadata Mappings
Table 129
Documentum Default Metadata Mappings
IS1200 Metadata Creation on copy/collection into Documentum repository
Source Repository IS1200 Tags or Sources
Target IS1200 Tags
110
Action
NFS
CIFS
Exchange
Sharepoint
Domino
EV
atime (Not preserved)
Object
creation time
in
Documentum
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
mtime (Not preserved)
Object
creation time
in
Documentum
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
ctime (Not preserved)
Object
creation time
in
Documentum
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
creationtime(Not
preserved)
Object
creation time
in
Documentum
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
owner (Not preserved)
User-id used
for repository
registration
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
group (Not preserved)
groupid of
suer used for
repository
registration or
Unknown
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
Not Preserved
cifs owner
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
N/A
N/A
cifs group
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
N/A
N/A
IS1200 Metadata Reference Guide— v4.8.0
Centera Documentum
Metadata Mapping
Table 129
Documentum Default Metadata Mappings
IS1200 Metadata Creation on copy/collection into Documentum repository
OriginalSource Tags
Preserved
from source
repository
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
OriginalSource
Tags
documentumAclDomain
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumAclName
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumAuthors
User-id used
for repository
registration
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumContentType
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumCreatorName
User-id used
for repository
registration
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumDeleted
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumGroupName
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumKeywords
Empty
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumLogEntry
Empty
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumMimeType
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumModifiedBy
User-id used
for repository
registration
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
Metadata Mapping
111
Metadata Mapping
Table 129
Documentum Default Metadata Mappings
IS1200 Metadata Creation on copy/collection into Documentum repository
112
documentumObjectId
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumObjectType
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumOwnerName
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumOwnerPermit
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumRetainerID
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumRetainUntil
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumSubject
Empty
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumTitle
Empty
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumVersionLabel
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
documentumVirtualDoc
Assigned by
Documentum
N/A
N/A
N/A
Not Preserved
N/A
N/A
N/A
N/A
IS1200 Metadata Reference Guide— v4.8.0
Metadata Mapping
Metadata Mapping
113
Metadata Mapping
114
IS1200 Metadata Reference Guide— v4.8.0
4
Legal Export Default Tags
This chapter describes the IS1200 metadata fields that are exported,
by default, during an Actionable Services Legal Export operation.
Topics include:
◆
◆
◆
Legal Export Tags Default profile.................................................. 116
Post Legal Export Tagging for Rolling Exports ........................... 118
Rolling Export Metadata Tags........................................................ 118
Legal Export Default Tags
115
Legal Export Default Tags
Legal Export Tags Default profile
The following table lists the IS1200 Schema fields exported using the
default export template for Concordance and Lextranet export. The
table applies only to versions IS1200 software v4.4.0 and greater.
Note: Modification of these output fields can only be performed by EMC
Professional Services.
Table 130
116
Default Kazeon Metadata Fields Exported During Concordance Legal
Export
Concordance
Tag Name
IS1200 Source Metadata Tag
Tag Type Name
Description
ObjMTime
Date*
ObjcommonMtime
Object common Mtime
ResposType
Text
EnvcommonRepositorytype
Repository Type
EnvMTime
Date*
EnvcommonMtime
Environment common Mtime
Fldrname
Text
HierarchyFolderName
Hierarchy Folder Name
Filename
Text
HierarchyFileName
Hierarchy File Name
FileType
Text
FileType
File Type
Filepath
Text
Filepath
File Path
FileSize
Text
FileSize
File Size
Group
Text
GroupName
Group Name
Owner
Text
OwnerName
Owner Name
ObjName
Text
ObjectName
Object Name
ObjType
Text
ObjectType
Object Type
FileExt
Text
FileExtension
File extension, the actual system object file extension
TypeExt
Text
TypeExtension
File true type extension, the programmatically derived file
extension, may differ from the FileExt field
OrigsrcCust
Text
OriginalsourceCustodian
Original source custodian, reflects the original file/object
custodian. May be overridden during processing using
custodian mapping
IS1200 Metadata Reference Guide— v4.8.0
Legal Export Default Tags
Table 130
Default Kazeon Metadata Fields Exported During Concordance Legal
Export
Concordance
Tag Name
IS1200 Source Metadata Tag
Tag Type Name
OrigsrcLoc
Text
OriginalsourceLocation
Original Source location, reflects the first full filepath the object
was found in
OrigsrcCLoc
Text
OriginalsourceContainerlocation
Origianal Source Container Location. For objects found in
containers during processing, reflects the container path
OrigsrcDoId
Text
OriginalsourceDocId
Original source document ID
ATime
Date*
Atime
Access time, reflects the last file access time
MTime
Date*
Mtime
Modified Time, reflects the last file modification time
CTime
Date*
Ctime
Metadata change time
CrtTime
Date*
Creation Time
File creation time
legalRvwer
Text
legalappReviewer
Legal reviewer assigned to this file
legalTag
Text
legalappTag
Legal case review tag
RvwdAs
Text
legalappReviewedAs
legalNotes
Text
legalappNotes
Standard legal review notes of this file
LastRvwdBy
Text
legalappLastReviewedBy
File last reviewed by
LastRvwdDate
Text
legalappLastReviewedDate
File last reviewed date
Description
*Default date format is "yyyy/mm/dd".
Legal Export Default Tags
117
Legal Export Default Tags
Post Legal Export Tagging for Rolling Exports
After any successful Legal Export operation, where an active-case
was selected and the Rolling Export options were used, a tagging job is
run after the legal export completes to update the exported file’s
source metadata with the export jobID, legal case number, and export
time.
See the Legal Exports: Rolling Exports heading of the Actionable Services
sections of the IS1200 Web-Search User Guide or
IS1200 eDiscovery Case Manager Administrators and Supervisors Guide
for more background on Rolling Exports. See “LegalExport
Namespace” on page 44 for descriptions of the metadata tags that are
updated.
Rolling Export Metadata Tags
The Rolling Export option Mark Exported Objects adds special case tags
to the exported file’s metadata in their source index. The tags record
what case and job the files were exported under. Once applied, these
tags appear in review filters.
The two new metadata tag names are:
◆
LegalExportCaseIds - which identifies whether the object has
been exported
◆
LegalExportJobIds - which identifies the export job ids
For example, the following metadata tag/values might be searched
for:
LegalExportCaseIds=case.1.yes, case.2.yes
LegalExportJobIds=case.1.job.20, case.2.job.21
118
IS1200 Metadata Reference Guide— v4.8.0
A
NSF Metadata Tags
This appendix describes how Lotus NSF Metadata is Mapped to
IS1200 Tags.
Topics include:
◆
How NSF Metadata is Mapped to IS1200 Tags ........................... 120
NSF Metadata Tags
119
NSF Metadata Tags
How NSF Metadata is Mapped to IS1200 Tags
The following table shows how Lotus metadata is mapped to IS1200
metadata.
Table 131
Lotus Email Metadata Mappings
Lotus notes fields
EML Fields per RFC822
IS1200 eMail Search
Template Fields
Created: 02/25/2010 03:30:56 PM PST
ctime
Modified: 02/25/2010 03:31:37 PM PST
mtime
Accessed: 02/25/2010 03:31:37 PM PST
atime
DeliveredDate:
PostedDate: 02/25/2010 03:31:37 PM PST
Date (Inbox other folder items
)
Email received
Date ( For Sent Items )
$Revisions:
RouteTimes:
Principal: CN=akiko4/O=kazeon
$langPrincipal:
$altPrincipal:
InetSendTo: .
InetCopyTo: .
InetBlindCopyTo: .
$StorageTo: 1
$StorageCc: 1
$StorageBcc: 1
$Mailer: Lotus Notes Release 6.5 September 26, 2003
$MessageID: <OF6A9B442F.1FF44B1FON882576D5.00812CF4-882576D5.00813D1D@LocalDomain>
Message-ID
Message-ID
From
From
Recipients: CN=akiko4/O=kazeon@kazeon
MailOptions: 0
SaveOptions: 1
Form: Memo
From: CN=Administrator/O=kazeon
120
IS1200 Metadata Reference Guide— v4.8.0
NSF Metadata Tags
Table 131
Lotus Email Metadata Mappings
Lotus notes fields
AltFrom: CN=Administrator/O=Kazeon
EML Fields per RFC822
IS1200 eMail Search
Template Fields
Sender
Logo: stdNotesLtr0
useApplet: True
DefaultMailSaveOptions: 1
Query_String:
ExpandPersonalGroups: 1
tmpImp:
Sign:
Encrypt:
Encrypted
SendTo: CN=akiko4/O=kazeon@kazeon
To
To
CopyTo: CN=akiko5/O=kazeon@kazeon
CC
Cc
BlindCopyTo: CN=akssach5/O=kazeon@kazeon
BCC
Bcc
Subject
Subject
Subject: test cc, bcc
Body:
Everything after 1st null is
body
wBody:
EnterSendTo: akiko4
EnterCopyTo: akiko5
EnterBlindCopyTo: akiko6
$UpdatedBy: CN=Administrator/O=kazeon
NSF Metadata Tags
121
NSF Metadata Tags
122
IS1200 Metadata Reference Guide— v4.8.0
B
Using DICOM Tags
This appendix provides reference information useful when extracting
DICOM properties as extended attributes.
Topics include:
◆
◆
◆
◆
◆
Using DICOM File Attributes as Metadata.................................. 124
Enabling DICOM File Recognition................................................ 124
Selecting the DICOM Properties to Extract.................................. 125
Adding DICOM File Attributes to the Search Schema............... 125
DICOM Properties That Can Be Extracted As Extended Attributes
126
123
Using DICOM File Attributes as Metadata
DICOM files contain hundreds of standard file attributes that are
useful in searches.
Starting with version 3.1 Hotfix 3, recognition of DICOM files is OFF
by default and must be specifically enabled when desired. Even when
recognition is enabled, only the file-type DICOM is extracted unless
specific DICOM properties are selected for extraction using extraction
rules and certain configuration file settings.
The IS1200 only searches DICOM file headers for their attributes, it
does not open or parse the actual image data.
Enabling DICOM File Recognition
DICOM file processing (recognition) is optional, and OFF by default.
As such, DICOM files are considered unknown-type files.
To enable recognition and handling of DICOM files,
remove the # from the beginning of the "#handleDicomFiles=1" line
in
/opt/openkaz/config/parser.config:
# If set (to 1 or true), then DICOM file
handling is enabled. If
# not set, files will not be checked for DICOM
filetype, nor will
# DICOM metadata be extracted (they will be
treated as UNKNOWN).
#handleDicomFiles=1
Do this on each node of the cluster. Normally, selecting what
attributes are processed is done using extraction rules, but since
initial file recognition is done during basic classification (when
extraction rules do not apply), DICOM file recognition must be
controlled through configuration files.
124
IS1200 Metadata Reference Guide— v4.8.0
Selecting the DICOM Properties to Extract
Once recognition is enabled, do the following to select the DICOM
properities to extract.
Then, do the following to setup DICOM file attribute classification:
Edit the file /opt/openkaz/config/parser.config to set
skipProperities=FALSE.
Edit the file /opt/openkaz/config/parser.config on
each node to uncomment and set:
DicomProperties=<list_of_DicomProperties_to_cl
assify>
The list should be separated by commas, for example:
DicomProperties=DICOMPatientsName,DICOMPatient
ID,DICOMStudyDate
to collect only the three Dicom properties in the list above.
Edit the Search Index to add the desired Dicom attributes, see the
following section for details.
Adding DICOM File Attributes to the Search Schema
The IS1200 can extract most of the standard DICOM file attributes as
metadata. To make these attributes searchable, each attribute you
want to search by must be added to the Search Index, and then a deep
classification must be run. For example, to be able to search by the
DICOM tag DICOMTableTopEccentricAxisDistance, enter
the following in the CLI:
set schema DICOMTable.TopEccentricAxisDistance
attributes string,indexed
and then run a deep classification.
After the classification finishes, the tag
DICOMTableTopEccentricAxisDistance will be available
in the standard search index.
125
DICOM Properties That Can Be Extracted As Extended Attributes
The following is a list of all DICOM tags that can be added to the search index:
126
DICOMAccessionNumber
DICOMAffectedSOPClassUID
DICOMAcquisitionContextDescription
DICOMAffectedSOPInstanceUID
DICOMAcquisitionContextSequence
DICOMAirKermaRateReferenceDate
DICOMAcquisitionDate
DICOMAirKermaRateReferenceTime
DICOMAcquisitionDeviceProcessingCode
DICOMAnatomicRegionModifierSequence
DICOMAcquisitionDeviceProcessingDescription
DICOMAnatomicRegionSequence
DICOMAcquisitionGroupLength
DICOMAnatomicStructureSpaceorRegionSequence
DICOMAcquisitionMatrix
DICOMAngioFlag
DICOMAcquisitionNumber
DICOMAngularPosition
DICOMAcquisitionsinStudy
DICOMAngularStep
DICOMAcquisitionStartCondition
DICOMAngularViewVector
DICOMAcquisitionStartConditionData
DICOMAnnotationContentSequence
DICOMAcquisitionTerminationCondition
DICOMAnnotationDisplayFormatID
DICOMAcquisitionTerminationConditionData
DICOMAnnotationFlag
DICOMAcquisitionTime
DICOMAnnotationPosition
DICOMActionTypeID
DICOMAnodeTargetMaterial
DICOMActiveSourceDiameter
DICOMApplicableFrameRange
DICOMActiveSourceLength
DICOMApplicationSetupManufacturer
DICOMActualFrameDuration
DICOMApplicationSetupName
DICOMActualHumanPerformersSequence
DICOMApplicationSetupNumber
DICOMAdditionalDrugSequence
DICOMApplicationSetupSequence
DICOMAdditionalPatientHistory
DICOMApplicationSetupType
DICOMAdministrationRouteCodeSequence
DICOMApplicatorDescription
DICOMAdmissionID
DICOMApplicatorID
DICOMAdmittingDate
DICOMApplicatorSequence
DICOMAdmittingDiagnosesDescription
DICOMApplicatorType
DICOMAdmittingDiagnosisCodeSequence
DICOMApprovalStatus
DICOMAdmittingTime
DICOMAttenuationCorrectionMethod
IS1200 Metadata Reference Guide— v4.8.0
DICOMAttributeIdentifierList
DICOMBitsStored
DICOMAudioComments
DICOMBlockData
DICOMAudioSampleData
DICOMBlockDivergence
DICOMAudioSampleFormat
DICOMBlockName
DICOMAudioType
DICOMBlockNumber
DICOMAveragePulseWidth
DICOMBlockNumberofPoints
DICOMAxialAcceptance
DICOMBlockSequence
DICOMAxialMash
DICOMBlockThickness
DICOMAxisLabels
DICOMBlockTransmission
DICOMAxisUnits
DICOMBlockTrayID
DICOMBasicColorImageSequence
DICOMBlockType
DICOMBasicGrayscaleImageSequence
DICOMBluePaletteColorLookupTableData
DICOMBeamDescription
DICOMBluePaletteColorLookupTableDescriptor
DICOMBeamDose
DICOMBodyPartExamined
DICOMBeamDoseSpecificationPoint
DICOMBodyPartThickness
DICOMBeamLimitingDeviceAngle
DICOMBorderDensity
DICOMBeamLimitingDeviceAngleTolerance
DICOMBrachyAccessoryDeviceID
DICOMBeamLimitingDevicePositionSequence
DICOMBrachyAccessoryDeviceName
DICOMBeamLimitingDevicePositionTolerance
DICOMBrachyAccessoryDeviceNominalThickness
DICOMBeamLimitingDeviceRotationDirection
DICOMBrachyAccessoryDeviceNominalTransmissi
on
DICOMBeamLimitingDeviceSequence
DICOMBeamLimitingDeviceToleranceSequence
DICOMBeamMeterset
DICOMBeamName
DICOMBeamNumber
DICOMBeamSequence
DICOMBeamType
DICOMBeatRejectionFlag
DICOMBillingItemSequence
DICOMBillingProcedureStepSequence
DICOMBillingSuppliesandDevicesSequence
DICOMBiPlaneAcquisitionSequence
DICOMBrachyAccessoryDeviceNumber
DICOMBrachyAccessoryDeviceSequence
DICOMBrachyAccessoryDeviceType
DICOMBrachyApplicationSetupDose
DICOMBrachyApplicationSetupDoseSpecificationP
oint
DICOMBrachyControlPointSequence
DICOMBrachyReferencedDoseReferenceSequence
DICOMBrachyTreatmentTechnique
DICOMBrachyTreatmentType
DICOMBranchofService
DICOMBurnedInAnnotation
DICOMBitsAllocated
127
DICOMCalibrationDataSequence
DICOMColumns
DICOMCalibrationImage
DICOMCommandField
DICOMCardiacNumberofImages
DICOMCommentsonRadiationDose
DICOMCassetteOrientation
DICOMCommentsonthePerformedProcedureSteps
DICOMCassetteSize
DICOMCommentsontheScheduledProcedureStep
DICOMCenterofCircularCollimator
DICOMCompensatorColumns
DICOMCenterofCircularShutter
DICOMCompensatorID
DICOMCenterofRotationOffset
DICOMCompensatorNumber
DICOMChannelLength
DICOMCompensatorPixelSpacing
DICOMChannelNumber
DICOMCompensatorPosition
DICOMChannelSequence
DICOMCompensatorRows
DICOMChannelShieldID
DICOMCompensatorSequence
DICOMChannelShieldName
DICOMCompensatorThicknessData
DICOMChannelShieldNominalThickness
DICOMCompensatorTransmissionData
DICOMChannelShieldNominalTransmission
DICOMCompletionFlag
DICOMChannelShieldNumber
DICOMCompletionFlagDescription
DICOMChannelShieldSequence
DICOMCompressionForce
DICOMChannelTotalTime
DICOMConceptCodeSequence
DICOMCineRate
DICOMConceptNameCodeSequence
DICOMCodeMeaning
DICOMConfidentialityCode
DICOMCodeValue
DICOMConfidentialityConstraintonPatientDataDes
cription
DICOMCodingSchemeDesignator
DICOMCoincidenceWindowWidth
DICOMCollationFlag
DICOMCollimatorgridName
DICOMCollimatorLeftVerticalEdge
DICOMCollimatorLowerHorizontalEdge
DICOMCollimatorRightVerticalEdge
DICOMCollimatorShape
DICOMCollimatorType
DICOMCollimatorUpperHorizontalEdge
DICOMColorImagePrintingFlag
DICOMColumnAngulation
128
IS1200 Metadata Reference Guide— v4.8.0
DICOMConfigurationInformation
DICOMConstraintWeight
DICOMContentSequence
DICOMContentTemplateSequence
DICOMContinuityOfContent
DICOMContourData
DICOMContourGeometricType
DICOMContourImageSequence
DICOMContourOffsetVector
DICOMContourSequence
DICOMContourSlabThickness
DICOMContrastAllergies
DICOMCumulativeMetersetWeight
DICOMContrastBolusAdministrationRouteSequenc
e
DICOMCumulativeTimeWeight
DICOMContrastBolusAgent
DICOMCurrentPatientLocation
DICOMContrastBolusAgentSequence
DICOMCurrentRequestedProcedureEvidenceSeque
nce
DICOMContrastBolusIngredient
DICOMCurveDataDescriptor
DICOMContrastBolusIngredientConcentration
DICOMCurveDataOW
DICOMContrastBolusRoute
DICOMCurveDate
DICOMContrastBolusStartTime
DICOMCurveDescription
DICOMContrastBolusStopTime
DICOMCurveDimensions
DICOMContrastBolusTotalDose
DICOMCurveLabel
DICOMContrastBolusVolume
DICOMCurveNumber
DICOMContrastFlowDurations
DICOMCurveRange
DICOMContrastFlowRates
DICOMCurveTime
DICOMContrastFrameAveraging
DICOMDataCollectionDiameter
DICOMControlPoint3DPosition
DICOMDataInformationSequence
DICOMControlPointIndex
DICOMDataSetTrailingPadding
DICOMControlPointRelativePosition
DICOMDataSetType
DICOMControlPointSequence
DICOMDataValueRepresentation
DICOMConversionType
DICOMDate
DICOMConvolutionKernel
DICOMDateofLastCalibration
DICOMCoordinateStartValue
DICOMDateOfLastDetectorCalibration
DICOMCoordinateStepValue
DICOMDateofSecondaryCapture
DICOMCorrectedImage
DICOMDateTime
DICOMCountRate
DICOMdBdt
DICOMCountryofResidence
DICOMDeadTimeCorrectionFlag
DICOMCountsAccumulated
DICOMDeadTimeFactor
DICOMCountsIncluded
DICOMDecayCorrection
DICOMCountsSource
DICOMDecayFactor
DICOMCranialThermalIndex
DICOMDeliveryMaximumDose
DICOMCreationDate
DICOMDeliveryWarningDose
DICOMCreationTime
DICOMDepthofScanField
DICOMCumulativeDoseReferenceCoefficient
DICOMDerivationDescription
129
130
DICOMDestinationAE
DICOMDischargeDate
DICOMDetectorActivationOffsetFromExposure
DICOMDischargeDiagnosisCodeSequence
DICOMDetectorActiveDimensions
DICOMDischargeDiagnosisDescription
DICOMDetectorActiveOringin
DICOMDischargeTime
DICOMDetectorActiveShape
DICOMDistanceSourcetoDetector
DICOMDetectorActiveTime
DICOMDistanceSourcetoEntrance
DICOMDetectorBinning
DICOMDistanceSourcetoPatient
DICOMDetectorConditionsNominalFlag
DICOMDistanceSourcetoSupport
DICOMDetectorConfiguration
DICOMDistributionAddress
DICOMDetectorDescription
DICOMDistributionName
DICOMDetectorElementPhysicalSize
DICOMDopplerCorrectionAngle
DICOMDetectorElementSize
DICOMDopplerSampleVolumeXPosition
DICOMDetectorElementSpacing
DICOMDopplerSampleVolumeYPosition
DICOMDetectorID
DICOMDoseCalibrationFactor
DICOMDetectorInformationSequence
DICOMDoseComment
DICOMDetectorLinesofResponseUsed
DICOMDoseGridScaling
DICOMDetectorMode
DICOMDoseRateSet
DICOMDetectorPrimaryAngle
DICOMDoseReferenceDescription
DICOMDetectorSecondaryAngle
DICOMDoseReferenceNumber
DICOMDetectorTemperature
DICOMDoseReferencePointCoordinates
DICOMDetectorTimeSinceLastExposure
DICOMDoseReferenceSequence
DICOMDetectorType
DICOMDoseReferenceStructureType
DICOMDetectorVector
DICOMDoseReferenceType
DICOMDeviceDescription
DICOMDoseSummationType
DICOMDeviceDiameter
DICOMDoseType
DICOMDeviceDiameterUnits
DICOMDoseUnits
DICOMDeviceLength
DICOMDoseValue
DICOMDeviceSequence
DICOMDVHData
DICOMDeviceSerialNumber
DICOMDVHDoseScaling
DICOMDeviceVolume
DICOMDVHMaximumDose
DICOMDigitalImageFormatAcquired
DICOMDVHMeanDose
DICOMDirectoryRecordSequence
DICOMDVHMinimumDose
DICOMDirectoryRecordType
DICOMDVHNormalizationDoseValue
IS1200 Metadata Reference Guide— v4.8.0
DICOMDVHNormalizationPoint
DICOMExposureControlModeDescription
DICOMDVHNumberofBins
DICOMExposureinuAs
DICOMDVHReferencedROISequence
DICOMExposureSequence
DICOMDVHROIContributionType
DICOMExposuresOnDetectorSinceLastCalibration
DICOMDVHSequence
DICOMExposuresOnDetectorSinceManufactured
DICOMDVHType
DICOMExposuresonPlate
DICOMDVHVolumeUnits
DICOMExposureStatus
DICOMEchoNumbers
DICOMExposureTime
DICOMEchoTime
DICOMFailedSOPInstanceUIDList
DICOMEchoTrainLength
DICOMFailedSOPSequence
DICOMEffectiveSeriesDuration
DICOMFailureReason
DICOMEmptyImageDensity
DICOMFieldofViewDimensions
DICOMEndCumulativeMetersetWeight
DICOMFieldOfViewHorizontalFlip
DICOMEnergyWindowInformationSequence
DICOMFieldOfViewOrigin
DICOMEnergyWindowLowerLimit
DICOMFieldOfViewRotation
DICOMEnergyWindowName
DICOMFieldofViewShape
DICOMEnergyWindowNumber
DICOMFileInformationGroupLength
DICOMEnergyWindowRangeSequence
DICOMFileMetaInformationVersion
DICOMEnergyWindowUpperLimit
DICOMFilesetConsistencyFlag
DICOMEnergyWindowVector
DICOMFilesetDescriptorFileID
DICOMEntranceDose
DICOMFilesetID
DICOMErrorComment
DICOMFillerOrderNumberORImagingServiceRequ
est
DICOMErrorID
DICOMEstimatedRadiographicMagnificationFactor
DICOMEthnicGroup
DICOMEventElapsedTimes
DICOMEventTimerNames
DICOMEventTypeID
DICOMExecutionStatus
DICOMExecutionStatusInfo
DICOMExposedArea
DICOMExposure
DICOMFillerOrderNumberORImagingServiceRequ
est
DICOMFillerOrderNumberProcedure
DICOMFilmBoxContentSequence
DICOMFilmConsumptionSequence
DICOMFilmDestination
DICOMFilmOrientation
DICOMFilmSessionLabel
DICOMFilmSizeID
DICOMFilterMaterial
DICOMExposureControlMode
131
132
DICOMFilterThicknessMaximum
DICOMGantryDetectorSlew
DICOMFilterThicknessMinimum
DICOMGantryDetectorTilt
DICOMFilterType
DICOMGantryRotationDirection
DICOMFinalCumulativeMetersetWeight
DICOMGatedInformationSequence
DICOMFinalCumulativeTimeWeight
DICOMGeneratorPower
DICOMFixationDeviceDescription
DICOMGraphicData
DICOMFixationDeviceLabel
DICOMGraphicType
DICOMFixationDevicePosition
DICOMGreenPaletteColorLookupTableData
DICOMFixationDeviceSequence
DICOMGreenPaletteColorLookupTableDescriptor
DICOMFixationDeviceType
DICOMGrid
DICOMFlipAngle
DICOMGridAbsorbingMaterial
DICOMFocalDistance
DICOMGridAspectRatio
DICOMFocalSpots
DICOMGridFocalDistance
DICOMFocusDepth
DICOMGridFrameOffsetVector
DICOMFractionGroupNumber
DICOMGridPeriod
DICOMFractionGroupSequence
DICOMGridPitch
DICOMFractionNumber
DICOMGridSpacingMaterial
DICOMFractionPattern
DICOMGridThickness
DICOMFrameDelay
DICOMHalfValueLayer
DICOMFrameIncrementPointer
DICOMHardcopyCreationDeviceID
DICOMFrameNumbersofInterest
DICOMHardcopyDeviceManufacturer
DICOMFrameofReferenceRelationshipSequence
DICOMHardcopyDeviceSoftwareVersion
DICOMFrameofReferenceTransformationComment
DICOMHardcopyDevManufactModelName
DICOMFrameofReferenceTransformationMatrix
DICOMHeartRate
DICOMFrameofReferenceTransformationType
DICOMHighBit
DICOMFrameofReferenceUID
DICOMHighRRValue
DICOMFrameReferenceTime
DICOMHistogramBinWidth
DICOMFramesofInterestDescription
DICOMHistogramData
DICOMFrameTime
DICOMHistogramExplanation
DICOMFrameTimeVector
DICOMHistogramFirstBinValue
DICOMFramingType
DICOMHistogramLastBinValue
DICOMGantryAngle
DICOMHistogramNumberOfBins
DICOMGantryAngleTolerance
DICOMHistogramSequence
IS1200 Metadata Reference Guide— v4.8.0
DICOMHumanPerformerCodeSequence
DICOMImagingFrequency
DICOMHumanPerformersName
DICOMImagingServiceRequestComments
DICOMHumanPerformersOrganization
DICOMImplantPresent
DICOMIconImageSequence
DICOMImplementationClassUID
DICOMIdenticalDocumentsSequence
DICOMImplementationVersionName
DICOMIdentifyingGroupLength
DICOMImpressions
DICOMIllumination
DICOMInstanceCreationDate
DICOMImageAreaDoseProduct
DICOMInstanceCreationTime
DICOMImageBoxContentSequence
DICOMInstanceCreatorUID
DICOMImageBoxPresentationLUTFlag
DICOMInstanceNumber
DICOMImageComments
DICOMInstitutionAddress
DICOMImageContentDate
DICOMInstitutionalDepartmentName
DICOMImageContentTime
DICOMInstitutionCodeSequence
DICOMImageDisplayFormat
DICOMInstitutionName
DICOMImagedNucleus
DICOMIntensifierSize
DICOMImageFrameOrigin
DICOMIntermarkerDistance
DICOMImageID
DICOMInterpretationApprovalDate
DICOMImageIndex
DICOMInterpretationApprovalTime
DICOMImageLaterality
DICOMInterpretationApproverSequence
DICOMImageOrientationPatient
DICOMInterpretationAuthor
DICOMImageOverlayBoxContentSequence
DICOMInterpretationDiagnosisCodeSequence
DICOMImageOverlayFlag
DICOMInterpretationDiagnosisDescription
DICOMImagePlanePixelSpacing
DICOMInterpretationID
DICOMImagePosition
DICOMInterpretationIDIssuer
DICOMImagePositionPatient
DICOMInterpretationRecordedDate
DICOMImagePresentationGroupLength
DICOMInterpretationRecordedTime
DICOMImagerPixelSpacing
DICOMInterpretationRecorder
DICOMImagesinAcquisition
DICOMInterpretationStatusID
DICOMImageTransformationMatrix
DICOMInterpretationText
DICOMImageTranslationVector
DICOMInterpretationTranscriber
DICOMImageType
DICOMInterpretationTranscriptionDate
DICOMImagingDeviceSpecificAcquisitionParamete
rs
DICOMInterpretationTranscriptionTime
DICOMInterpretationTypeID
133
134
DICOMIntervalsAcquired
DICOMManufacturer
DICOMIntervalsRejected
DICOMManufacturersModelName
DICOMInterventionalStatus
DICOMMaskFrameNumbers
DICOMInterventionalTherapySequence
DICOMMaskOperation
DICOMInterventionDrugCodeSequence
DICOMMaskOperationExplanation
DICOMInterventionDrugDose
DICOMMaskPointers
DICOMInterventionDrugInformationSequence
DICOMMaskSubpixelShift
DICOMInterventionDrugName
DICOMMaskSubtractionSequence
DICOMInterventionDrugStartTime
DICOMMaterialID
DICOMInterventionDrugStopTime
DICOMMaxDensity
DICOMInversionTime
DICOMMaximumCoordinateValue
DICOMIsocenterPosition
DICOMMeasuredValueSequence
DICOMIssueDateofImagingServiceRequest
DICOMMeasurementUnitsCodeSequence
DICOMIssuerofAdmissionID
DICOMMeasuringUnitsSequence
DICOMIssuerofPatientID
DICOMMechanicalIndex
DICOMIssueTimeofImagingServiceRequest
DICOMMediaStorageSOPClassUID
DICOMKVP
DICOMMediaStorageSOPInstanceUID
DICOMLargestImagePixelValue
DICOMMedicalAlerts
DICOMLargestImagePixelValueinPlane
DICOMMedicalRecordLocator
DICOMLargestPixelValueinSeries
DICOMMediumType
DICOMLastMenstrualDate
DICOMMemoryAllocation
DICOMLaterality
DICOMMessageID
DICOMLeafJawPositions
DICOMMessageIDBeingRespondedTo
DICOMLeafPositionBoundaries
DICOMMetersetExposure
DICOMLookupTableNumber
DICOMMilitaryRank
DICOMLossyImageCompression
DICOMMinDensity
DICOMLossyImageCompressionRatio
DICOMMinimumCoordinateValue
DICOMLowRRValue
DICOMModalitiesinStudy
DICOMLUTDataUSor
DICOMModality
DICOMLUTDescriptor
DICOMModalityLUTSequence
DICOMLUTExplanation
DICOMModalityLUTType
DICOMMagneticFieldStrength
DICOMMoveDestination
DICOMMagnificationType
DICOMMoveOriginatorApplicationEntityTitle
IS1200 Metadata Reference Guide— v4.8.0
DICOMMoveOriginatorMessageID
DICOMNumberofPatientRelatedSeries
DICOMMRAcquisitionType
DICOMNumberofPatientRelatedStudies
DICOMMRDRDirectoryRecordOffset
DICOMNumberofPhaseEncodingSteps
DICOMNameofPhysiciansReadingStudy
DICOMNumberofPhases
DICOMNamesofIntendedRecipientsofResults
DICOMNumberofPoints
DICOMNominalBeamEnergy
DICOMNumberofPulses
DICOMNominalInterval
DICOMNumberofReferences
DICOMNominalPriorDose
DICOMNumberofRemainingSuboperations
DICOMNormalizationPoint
DICOMNumberofRotations
DICOMNumberofAverages
DICOMNumberofRRIntervals
DICOMNumberofBeams
DICOMNumberofSamples
DICOMNumberofBlocks
DICOMNumberofSeriesRelatedImages
DICOMNumberofBoli
DICOMNumberofSlices
DICOMNumberofBrachyApplicationSetups
DICOMNumberofStages
DICOMNumberofChannels
DICOMNumberofStudyRelatedImages
DICOMNumberofCompensators
DICOMNumberofStudyRelatedSeries
DICOMNumberofCompletedSuboperations
DICOMNumberofTableBreakPoints
DICOMNumberofContourPoints
DICOMNumberofTableEntries
DICOMNumberofControlPoints
DICOMNumberofTemporalPositions
DICOMNumberofCopies
DICOMNumberofTimeSlices
DICOMNumberofDetectors
DICOMNumberofTimeSlots
DICOMNumberofEnergyWindows
DICOMNumberOfTomoSynthesisSourceImages
DICOMNumberofEventTimers
DICOMNumberofTriggersinPhase
DICOMNumberofFailedSuboperations
DICOMNumberofViewsinStage
DICOMNumberofFilms
DICOMNumberofWarningSuboperations
DICOMNumberofFractionsPerDay
DICOMNumberofWedges
DICOMNumberofFractionsPlanned
DICOMNumericValue
DICOMNumberofFrames
DICOMObservationDateTime
DICOMNumberofFramesinOverlay
DICOMObservationNumber
DICOMNumberofFramesinPhase
DICOMOccupation
DICOMNumberofFramesinRotation
DICOMOffendingElement
DICOMNumberofLeafJawPairs
DICOMOffsetofReferencedLowerLevelDirectoryEnt
ity
DICOMNumberofPatientRelatedImages
135
DICOMOffsetoftheFirstDirectoryRecordoftheRootD
irectoryEntity
DICOMOffsetoftheLastDirectoryRecordoftheRootD
irectoryEntity
DICOMOffsetoftheNextDirectoryRecord
DICOMOperatorsName
DICOMOrderCallbackPhoneNumber
DICOMOrderEnteredBy
DICOMOrderEnterersLocation
DICOMOrganatRiskFullvolumeDose
DICOMOrganatRiskLimitDose
DICOMOrganatRiskMaximumDose
DICOMOrganatRiskOverdoseVolumeFraction
DICOMOrganDose
DICOMOrganExposed
DICOMOriginalImageSequence
DICOMOriginator
DICOMOtherPatientIDs
DICOMOtherPatientNames
DICOMOtherStudyNumbers
DICOMOutputPower
DICOMOverlayBitPosition
DICOMOverlayBitsAllocated
DICOMOverlayColumns
DICOMOverlayData
DICOMOverlayDate
DICOMOverlayDescription
DICOMOverlayForegroundDensity
DICOMOverlayLabel
DICOMOverlayMagnificationType
DICOMOverlayMode
DICOMOverlayNumber
DICOMOverlayOrigin
136
IS1200 Metadata Reference Guide— v4.8.0
DICOMOverlayPlaneOrigin
DICOMOverlayPlanes
DICOMOverlayRows
DICOMOverlaySmoothingType
DICOMOverlaySubtype
DICOMOverlayTime
DICOMOverlayType
DICOMOwnerID
DICOMPaletteColorLookupTableUID
DICOMPatientAdditionalPosition
DICOMPatientComments
DICOMPatientGantryRelationshipCodeSequence
DICOMPatientGroupLength
DICOMPatientID
DICOMPatientOrientation
DICOMPatientOrientationCodeSequence
DICOMPatientOrientationModifierCodeSequence
DICOMPatientOtherEvidenceSequence
DICOMPatientPosition
DICOMPatientsAddress
DICOMPatientsAge
DICOMPatientsBirthDate
DICOMPatientsBirthName
DICOMPatientsBirthTime
DICOMPatientSetupNumber
DICOMPatientSetupSequence
DICOMPatientsInstitutionResidence
DICOMPatientsInsurancePlanCodeSequence
DICOMPatientsMothersBirthName
DICOMPatientsName
DICOMPatientsPrimaryLanguageCodeSequence
DICOMPatientsPrimaryLanguageModifierCodeSeq
uence
DICOMPatientsReligiousPreference
DICOMPersonName
DICOMPatientsSex
DICOMPhaseDelay
DICOMPatientsSize
DICOMPhaseEncodingDirection
DICOMPatientState
DICOMPhaseInformationSequence
DICOMPatientsTelephoneNumbers
DICOMPhaseVector
DICOMPatientSupportAngle
DICOMPhosphorType
DICOMPatientSupportAngleTolerance
DICOMPhotometricInterpretation
DICOMPatientSupportRotationDirection
DICOMPhototimerSetting
DICOMPatientsWeight
DICOMPhysicalDeltaX
DICOMPatientTransportArrangements
DICOMPhysicalDeltaY
DICOMPauseBetweenFrames
DICOMPhysicalUnitsXDirection
DICOMPercentPhaseFieldofView
DICOMPhysicalUnitsYDirection
DICOMPercentSampling
DICOMPhysicianApprovingInterpretation
DICOMPerformedActionItemSequence
DICOMPhysiciansofRecord
DICOMPerformedLocation
DICOMPixelAspectRatio
DICOMPerformedProcedureStepDescription
DICOMPixelBandwidth
DICOMPerformedProcedureStepEndDate
DICOMPixelComponentDataType
DICOMPerformedProcedureStepEndTime
DICOMPixelComponentMask
DICOMPerformedProcedureStepID
DICOMPixelComponentOrganization
DICOMPerformedProcedureStepStartDate
DICOMPixelComponentPhysicalUnits
DICOMPerformedProcedureStepStartTime
DICOMPixelComponentRangeStart
DICOMPerformedProcedureStepStatus
DICOMPixelComponentRangeStop
DICOMPerformedProcedureTypeDescription
DICOMPixelData
DICOMPerformedProcessingApplicationsCodeSeq
uence
DICOMPixelDataGroupLength
DICOMPerformedSeriesSequence
DICOMPerformedStationAETitle
DICOMPerformedstationGeographicLocationCode
sequence
DICOMPerformedStationName
DICOMPerformedStationNameCodeSequence
DICOMPerformingPhysiciansName
DICOMPerformProcedureCodeSequence
DICOMPixelIntensityRelationship
DICOMPixelIntensityRelationshipSign
DICOMPixelPaddingValue
DICOMPixelRepresentation
DICOMPixelSpacing
DICOMPlacerOrderNumberORImagingServiceReq
uest
DICOMPlacerOrderNumberORImagingServiceReq
uest
137
DICOMPlacerOrderNumberProcedure
DICOMPrinterStatusInfo
DICOMPlanarConfiguration
DICOMPrintJobDescriptionSequence
DICOMPlanes
DICOMPrintJobID
DICOMPlannedVerificationImageSequence
DICOMPrintManagementCapabilitiesSequence
DICOMPlateID
DICOMPrintPriority
DICOMPlateType
DICOMPrintQueueID
DICOMPolarity
DICOMPriority
DICOMPositionerMotion
DICOMPrivateInformation
DICOMPositionerPrimaryAngle
DICOMPrivateInformationCreatorUID
DICOMPositionerPrimaryAngleIncrement
DICOMPrivateRecordUID
DICOMPositionerSecondaryAngle
DICOMPrivateSchemeCreatorUID
DICOMPositionerSecondaryAngleIncrement
DICOMProcedureCodeSequence
DICOMPositionerType
DICOMProcessingFunction
DICOMPositionReferenceIndicator
DICOMProjectionEponymousNameCodeSequence
DICOMPostprocessingFunction
DICOMProposedStudySequence
DICOMPredecessorDocumentsSequence
DICOMProtocolName
DICOMPreferredPlaybackSequencing
DICOMPulseRepetitionFrequency
DICOMPregnancyStatus
DICOMPulseRepetitionInterval
DICOMPreMedication
DICOMPVCRejection
DICOMPrescriptionDescription
DICOMQualityControlImage
DICOMPresentationIntentType
DICOMQuantity
DICOMPresentationLUTContentSequence
DICOMQuantitySequence
DICOMPresentationLUTFlag
DICOMQueryRetrieveLevel
DICOMPresentationLUTSequence
DICOMQueueStatus
DICOMPresentationLUTShape
DICOMRadialPosition
DICOMPrimaryAnatomicStructureModifierSequen
ce
DICOMRadiationMachineName
DICOMPrimaryAnatomicStructureSequence
DICOMPrimaryDosimeterUnit
DICOMPrimaryPromptsCountsAccumulated
DICOMPrinterCharacteristicsSequence
DICOMPrinterName
DICOMPrinterStatus
138
IS1200 Metadata Reference Guide— v4.8.0
DICOMRadiationMachineSAD
DICOMRadiationMachineSSD
DICOMRadiationMode
DICOMRadiationSetting
DICOMRadiationType
DICOMRadionuclideCodeSequence
DICOMRadionuclideHalfLife
DICOMRadionuclidePositronFraction
DICOMRadionuclideTotalDose
DICOMRadiopharmaceutical
DICOMRadiopharmaceuticalCodeSequence
DICOMRadiopharmaceuticalInformationSequence
DICOMRadiopharmaceuticalRoute
DICOMRadiopharmaceuticalSpecificActivity
DICOMRadiopharmaceuticalStartTime
DICOMRadiopharmaceuticalStopTime
DICOMRadiopharmaceuticalVolume
DICOMRadiusofCircularCollimator
DICOMRadiusofCircularShutter
DICOMRandomsCorrectionMethod
DICOMReasonforStudy
DICOMReasonfortheImagingServiceRequest
DICOMReasonfortheRequestedProcedure
DICOMReceivingCoil
DICOMRecognitionCode
DICOMRecommendedDisplayFrameRate
DICOMRecommendedViewingMode
DICOMReconstructionDiameter
DICOMReconstructionMethod
DICOMRecordInuseFlag
DICOMRectificationType
DICOMRedPaletteColorLookupTableData
DICOMRedPaletteColorLookupTableDescriptor
DICOMReferenceAirKermaRate
DICOMReferencedBasicAnnotationBoxSequence
DICOMReferencedBeamNumber
DICOMReferencedBeamSequence
DICOMReferencedBlockNumber
DICOMReferencedBolusSequence
DICOMReferencedBrachyApplicationSetupNumbe
r
DICOMReferencedBrachyApplicationSetupSequenc
e
DICOMReferencedCompensatorNumber
DICOMReferencedContentItemIdentifier
DICOMReferencedControlPointIndex
DICOMReferencedCurveSequence
DICOMReferencedDateTime
DICOMReferencedDoseReferenceNumber
DICOMReferencedDoseReferenceSequence
DICOMReferencedDoseSequence
DICOMReferencedFileID
DICOMReferencedFilmBoxSequence
DICOMReferencedFilmSessionSequence
DICOMReferencedFractionGroupNumber
DICOMReferencedFractionGroupSequence
DICOMReferencedFrameNumber
DICOMReferencedFrameNumbers
DICOMReferencedFrameofReferenceSequence
DICOMReferencedFrameofReferenceUID
DICOMReferencedImageBoxSequence
DICOMReferencedImageOverlayBoxSequence
DICOMReferencedImageSequence
DICOMReferencedInterpretationSequence
DICOMReferencedOverlayGroup
DICOMReferencedOverlayPlaneGroups
DICOMReferencedOverlayPlaneSequence
DICOMReferencedOverlaySequence
DICOMReferencedOverlaySequence
DICOMReferencedPatientAliasSequence
DICOMReferencedPatientSequence
DICOMReferencedPatientSetupNumber
139
DICOMReferencedPresentationLUTSequence
DICOMReferencePixelPhysicalValueY
DICOMReferencedPrintJobSequence
DICOMReferencePixelX0
DICOMReferencedProcedureStepSequence
DICOMReferencePixelY0
DICOMReferencedReferenceImageNumber
DICOMReferencetoRecordedSound
DICOMReferencedReferenceImageSequence
DICOMReferringPhysiciansAddress
DICOMReferencedRequestSequence
DICOMReferringPhysiciansName
DICOMReferencedResultsSequence
DICOMReferringPhysiciansTelephoneNumbers
DICOMReferencedROINumber
DICOMReflectedAmbientLight
DICOMReferencedRTPlanSequence
DICOMRegionDataType
DICOMReferencedSamplePositions
DICOMRegionFlags
DICOMReferencedSeriesSequence
DICOMRegionLocationMaxX1
DICOMReferencedSOPClassUID
DICOMRegionLocationMaxY1
DICOMReferencedSOPClassUIDinFile
DICOMRegionLocationMinX0
DICOMReferencedSOPInstanceUID
DICOMRegionLocationMinY0
DICOMReferencedSOPInstanceUIDinFile
DICOMRegionofResidence
DICOMReferencedSOPSequence
DICOMRegionSpatialFormat
DICOMReferencedSourceNumber
DICOMRelatedFrameofReferenceUID
DICOMReferencedStandaloneSOPInstanceSequenc
e
DICOMRelatedRTROIObservationsSequence
DICOMReferencedStoredPrintSequence
DICOMReferencedStructureSetSequence
DICOMReferencedStudyComponentSequence
DICOMReferencedStudySequence
DICOMReferencedTimeOffsets
DICOMReferencedToleranceTableNumber
DICOMReferencedTransferSyntaxUIDinFile
DICOMReferencedVerificationImageSequence
DICOMReferencedVisitSequence
DICOMReferencedVOILUTBoxSequence
DICOMReferencedWaveformChannels
DICOMReferencedWedgeNumber
DICOMReferenceImageNumber
DICOMReferencePixelPhysicalValueX
140
IS1200 Metadata Reference Guide— v4.8.0
DICOMRelationshipGroupLength
DICOMRelationshipType
DICOMRelativeXrayExposure
DICOMRepeatFractionCycleLength
DICOMRepetitionTime
DICOMReportedValuesOrigin
DICOMReportingPriority
DICOMRepresentativeFrameNumber
DICOMReprojectionMethod
DICOMRequestAttributesSequence
DICOMRequestedContrastAgent
DICOMRequestedImageSize
DICOMRequestedProcedureCodeSequence
DICOMRequestedProcedureCodeSequence
DICOMRequestedProcedureComments
DICOMRequestedProcedureDescription
DICOMROIPhysicalPropertiesSequence
DICOMRequestedProcedureDescription
DICOMROIPhysicalProperty
DICOMRequestedProcedureID
DICOMROIPhysicalPropertyValue
DICOMRequestedProcedureLocation
DICOMROIStandardDeviation
DICOMRequestedProcedurePriority
DICOMROIVolume
DICOMRequestedSOPClassUID
DICOMRotationDirection
DICOMRequestedSOPInstanceUID
DICOMRotationInformationSequence
DICOMRequestingPhysician
DICOMRotationVector
DICOMRequestingService
DICOMRouteofAdmissions
DICOMRescaleIntercept
DICOMRows
DICOMRescaleSlope
DICOMRRIntervalVector
DICOMRescaleType
DICOMRTBeamLimitingDeviceType
DICOMResidualSyringeCounts
DICOMRTDoseROISequence
DICOMResultsComments
DICOMRTImageDescription
DICOMResultsDistributionListSequence
DICOMRTImageLabel
DICOMResultsID
DICOMRTImageName
DICOMResultsIDIssuer
DICOMRTImageOrientation
DICOMRetrieveAETitle
DICOMRTImagePlane
DICOMReviewDate
DICOMRTImagePosition
DICOMReviewerName
DICOMRTImageSID
DICOMReviewTime
DICOMRTPlanDate
DICOMROIArea
DICOMRTPlanDescription
DICOMROIContourSequence
DICOMRTPlanGeometry
DICOMROIDescription
DICOMRTPlanLabel
DICOMROIDisplayColor
DICOMRTPlanName
DICOMROIGenerationAlgorithm
DICOMRTPlanRelationship
DICOMROIGenerationDescription
DICOMRTPlanTime
DICOMROIInterpreter
DICOMRTReferencedSeriesSequence
DICOMROIMean
DICOMRTReferencedStudySequence
DICOMROIName
DICOMRTRelatedROISequence
DICOMROINumber
DICOMRTROIIdentificationCodeSequence
DICOMROIObservationDescription
DICOMRTROIInterpretedType
DICOMROIObservationLabel
DICOMRTROIObservationsSequence
141
DICOMRTROIRelationship
DICOMScheduledStudyStartDate
DICOMRWavePointer
DICOMScheduledStudyStartTime
DICOMSampleRate
DICOMScheduledStudyStopDate
DICOMSamplesperPixel
DICOMScheduledStudyStopTime
DICOMSAR
DICOMSecondaryCaptureDeviceID
DICOMScanArc
DICOMSecondaryCaptureDeviceManufacturer
DICOMScanLength
DICOMSecondaryCaptureDeviceManufacturersMo
delName
DICOMScanningSequence
DICOMScanOptions
DICOMScanVelocity
DICOMScatterCorrectionMethod
DICOMScatterFractionFactor
DICOMScheduledActionItemCodeSequence
DICOMScheduledAdmissionDate
DICOMScheduledAdmissionTime
142
DICOMSecondaryCaptureDeviceSoftwareVersions
DICOMSecondaryCountsAccumulated
DICOMSecondaryCountsType
DICOMSegmentedBluePaletteColorLookupTableDa
ta
DICOMSegmentedGreenPaletteColorLookupTable
Data
DICOMScheduledDischargeDate
DICOMSegmentedRedPaletteColorLookupTableDa
ta
DICOMScheduledDischargeTime
DICOMSensitivity
DICOMScheduledPatientInstitutionResidence
DICOMSequenceName
DICOMScheduledPerformingPhysiciansName
DICOMSequenceofUltrasoundRegions
DICOMScheduledProcedureStepDescription
DICOMSequenceVariant
DICOMScheduledProcedureStepEndDate
DICOMSeriesDate
DICOMScheduledProcedureStepEndTime
DICOMSeriesDescription
DICOMScheduledProcedureStepID
DICOMSeriesInstanceUID
DICOMScheduledProcedureStepLocation
DICOMSeriesinStudy
DICOMScheduledProcedureStepSequence
DICOMSeriesNumber
DICOMScheduledProcedureStepStartDate
DICOMSeriesTime
DICOMScheduledProcedureStepStartTime
DICOMSeriesType
DICOMScheduledProcedureStepStatus
DICOMSetupDeviceDescription
DICOMScheduledStationAETitle
DICOMSetupDeviceLabel
DICOMScheduledStationName
DICOMSetupDeviceParameter
DICOMScheduledStepAttributesSequence
DICOMSetupDeviceSequence
DICOMScheduledStudyLocation
DICOMSetupDeviceType
DICOMScheduledStudyLocationAETitles
DICOMSetupReferenceDescription
IS1200 Metadata Reference Guide— v4.8.0
DICOMSetupTechnique
DICOMSourceApplicatorName
DICOMSetupTechniqueDescription
DICOMSourceApplicatorNumber
DICOMShieldingDeviceDescription
DICOMSourceApplicatorStepSize
DICOMShieldingDeviceLabel
DICOMSourceApplicatorType
DICOMShieldingDevicePosition
DICOMSourceApplicatorWallNominalThickness
DICOMShieldingDeviceSequence
DICOMSourceApplicatorWallNominalTransmissio
n
DICOMShieldingDeviceType
DICOMShutterLeftVerticalEdge
DICOMShutterLowerHorizontalEdge
DICOMShutterRightVerticalEdge
DICOMShutterShape
DICOMShutterUpperHorizontalEdge
DICOMSkipBeats
DICOMSlantAngle
DICOMSliceLocation
DICOMSliceSensitivityFactor
DICOMSliceThickness
DICOMSliceVector
DICOMSmallestImagePixelValue
DICOMSmallestImagePixelValueinPlane
DICOMSmallestPixelValueinSeries
DICOMSmokingStatus
DICOMSmoothingType
DICOMSoftTissuefocusThermalIndex
DICOMSoftTissuesurfaceThermalIndex
DICOMSoftTissueThermalIndex
DICOMSoftwareVersion
DICOMSOPClassUID
DICOMSOPInstanceUID
DICOMSourceApplicationEntityTitle
DICOMSourceApplicatorID
DICOMSourceApplicatorLength
DICOMSourceApplicatorManufacturer
DICOMSourceAxisDistance
DICOMSourceEncapsulationNominalThickness
DICOMSourceEncapsulationNominalTransmission
DICOMSourceImageSequence
DICOMSourceIsotopeHalfLife
DICOMSourceIsotopeName
DICOMSourceManufacturer
DICOMSourceMovementType
DICOMSourceNumber
DICOMSourceSequence
DICOMSourcetoBeamLimitingDeviceDistance
DICOMSourcetoBlockTrayDistance
DICOMSourcetoCompensatorTrayDistance
DICOMSourcetoReferenceObjectDistance
DICOMSourcetoSurfaceDistance
DICOMSourcetoWedgeTrayDistance
DICOMSourceType
DICOMSpacingBetweenSlices
DICOMSpatialResolution
DICOMSpecialNeeds
DICOMSpecificCharacterSet
DICOMSpecificCharacterSetofFilesetDescriptorFile
DICOMStageName
DICOMStageNumber
DICOMStartAngle
DICOMStartCumulativeMetersetWeight
143
144
DICOMStartTrim
DICOMTableAngle
DICOMStationName
DICOMTableHeight
DICOMStatus
DICOMTableLateralIncrement
DICOMSteeringAngle
DICOMTableLongitudinalIncrement
DICOMStopTrim
DICOMTableMotion
DICOMStorageMediaFilesetID
DICOMTableofParameterValues
DICOMStorageMediaFilesetUID
DICOMTableofPixelValues
DICOMStructureSetDate
DICOMTableofXBreakPoints
DICOMStructureSetDescription
DICOMTableofYBreakPoints
DICOMStructureSetLabel
DICOMTableTopEccentricAngle
DICOMStructureSetName
DICOMTableTopEccentricAngleTolerance
DICOMStructureSetROISequence
DICOMTableTopEccentricAxisDistance
DICOMStructureSetTime
DICOMTableTopEccentricRotationDirection
DICOMStudyArrivalDate
DICOMTableTopLateralPosition
DICOMStudyArrivalTime
DICOMTableTopLateralPositionTolerance
DICOMStudyComments
DICOMTableTopLateralSetupDisplacement
DICOMStudyCompletionDate
DICOMTableTopLongitudinalPosition
DICOMStudyCompletionTime
DICOMTableTopLongitudinalPositionTolerance
DICOMStudyComponentStatusID
DICOMTableTopLongitudinalSetupDisplacement
DICOMStudyDate
DICOMTableTopVerticalPosition
DICOMStudyDescription
DICOMTableTopVerticalPositionTolerance
DICOMStudyID
DICOMTableTopVerticalSetupDisplacement
DICOMStudyIDIssuer
DICOMTableTraverse
DICOMStudyInstanceUID
DICOMTableType
DICOMStudyPriorityID
DICOMTableVerticalIncrement
DICOMStudyReadDate
DICOMTargetMaximumDose
DICOMStudyReadTime
DICOMTargetMinimumDose
DICOMStudyStatusID
DICOMTargetPrescriptionDose
DICOMStudyTime
DICOMTargetUnderdoseVolumeFraction
DICOMStudyVerifiedDate
DICOMTemplateExtensionCreatorUID
DICOMStudyVerifiedTime
DICOMTemplateExtensionFlag
DICOMSurfaceEntryPoint
DICOMTemplateExtensionOrganizationUID
DICOMSyringeCounts
DICOMTemplateIdentifier
IS1200 Metadata Reference Guide— v4.8.0
DICOMTemplateLocalVersion
DICOMTomoTime
DICOMTemplateName
DICOMTomoType
DICOMTemplateNumber
DICOMTopicAuthor
DICOMTemplateType
DICOMTopicKeyWords
DICOMTemplateVersion
DICOMTopicSubject
DICOMTemporalPositionIdentifier
DICOMTopicTitle
DICOMTemporalRangeType
DICOMTotalBlockTrayFactor
DICOMTemporalResolution
DICOMTotalCompensatorTrayFactor
DICOMTextString
DICOMTotalNumberofExposures
DICOMTextValue
DICOMTotalReferenceAirKerma
DICOMTherapyDescription
DICOMTotalTime
DICOMTherapyType
DICOMTotalTimeofFluoroscopy
DICOMThermalIndex
DICOMTransactionUID
DICOMThresholdDensity
DICOMTransducerData
DICOMTIDOffset
DICOMTransducerFrequency
DICOMTime
DICOMTransducerOrientationModifierSequence
DICOMTimeofLastCalibration
DICOMTransducerOrientationSequence
DICOMTimeOfLastDetectorCalibration
DICOMTransducerPositionModifierSequence
DICOMTimeofSecondaryCapture
DICOMTransducerPositionSequence
DICOMTimeSliceVector
DICOMTransducerType
DICOMTimeSlotInformationSequence
DICOMTransferSyntaxUID
DICOMTimeSlotTime
DICOMTransferTubeLength
DICOMTimeSlotVector
DICOMTransferTubeNumber
DICOMTMLinePositionX0
DICOMTransmittingCoil
DICOMTMLinePositionX1
DICOMTransverseMash
DICOMTMLinePositionY0
DICOMTreatmentDeliveryType
DICOMTMLinePositionY1
DICOMTreatmentIntent
DICOMToleranceTableLabel
DICOMTreatmentMachineName
DICOMToleranceTableNumber
DICOMTreatmentMachineSequence
DICOMToleranceTableSequence
DICOMTreatmentProtocols
DICOMTomoAngle
DICOMTreatmentSites
DICOMTomoClass
DICOMTriggerSourceorType
DICOMTomoLayerHeight
DICOMTriggerTime
145
DICOMTriggerVector
DICOMWedgePosition
DICOMTriggerWindow
DICOMWedgePositionSequence
DICOMTrim
DICOMWedgeSequence
DICOMTypeofData
DICOMWedgeType
DICOMTypeofDetectorMotion
DICOMWholeBodyTechnique
DICOMTypeofFilters
DICOMWindowCenter
DICOMUID
DICOMWindowCenterWidthExplanation
DICOMUltrasoundColorDataPresent
DICOMWindowWidth
DICOMUnits
DICOMXFocusCenter
DICOMValueType
DICOMXRayImageReceptorAngle
DICOMVariableFlipAngleFlag
DICOMXRayOutput
DICOMVerificationDateTime
DICOMXrayTubeCurrent
DICOMVerificationFlag
DICOMYFocusCenter
DICOMVerifyingObserverIdentificationCodeSeque
nce
DICOMZoomCenter
DICOMVerifyingObserverName
DICOMVerifyingObserverSequence
DICOMVerifyingOrganization
DICOMVerticesofthePolygonalCollimator
DICOMVerticesofthePolygonalShutter
DICOMVideoImageFormatAcquired
DICOMViewCodeSequence
DICOMViewModifierCodeSequence
DICOMViewNumber
DICOMViewPosition
DICOMVisitComments
DICOMVisitStatusID
DICOMVOILUTSequence
DICOMWedgeAngle
DICOMWedgeFactor
DICOMWedgeID
DICOMWedgeNumber
DICOMWedgeOrientation
146
IS1200 Metadata Reference Guide— v4.8.0
DICOMZoomFactor
Glossary
This glossary contains terms related to disk storage subsystems,
networks, file management, and eDiscovery. Many of these terms are
used in this manual.
A
active case
In eDiscovery situations, a company may have more than one legal
issue (case) in progress at a time. Often it is advantageous to limit job
or search scope to just one case. When the user interface scope is
limited to a particular single case, that case is the active case.
Active Directory (AD)
A technology created by Microsoft that provides a variety of network
services, including: LDAP-like directory services, Kerberos-based
authentication, and DNS-based naming and other network
information.
Actions,
Actionable Services
Access Control List
(ACL)
Services such as copy, move, delete, tagging, and so on, that can be
applied to search and report results and allow the IS1200 to be an
effective file management tool for registered repositories.
A file system level data file that specifies how users or groups may
access resources on a computer or network, like an application, file or
printer, and the rights they have to it, for example read access, write
access, and so forth. For more information on how the IS1200 may use
ACLs, see the Controlling ACL Checking section of the Configuration
Files and Utilities appendix of any IS1200 User Guide for details.
147
Glossary
Advanced Search
Agents
Assignment Rules
A search made from the IS1200 Advanced Search link. Allows
searching for extracted metadata by tag-value pairs, and allows
multiple variable and boolean searches.
See “connectors” on page 151.
An assignment rule is a type of classification rule. It tags files with
metadata and assigns files to policy groups. Assignment rules are
contained in Assignment Rule Sets (ASRs). See the Policies:
Classification, Extraction and Assignment Rules chapter of the any
IS1200 User Guide for more details.
Auditing
A service that allows the IS1200 to record all system events according
to who did what, when, and the event result. This data is especially
useful to Legal Service Providers when providing an audit trail for
responsive data produced during eDiscovery. Complete details are
available in the Auditing and Data Verification chapter of any IS1200
User Guide for details.
Authorization Rule
A policy rule that filters search results to ensure that the assigned files
can only be viewed by authorized users. IS1200 authorization policies
may be used to add additional levels of security to the Access Control
Lists (ACLs) for file objects found in registered data repositories. See
the Policy Groups: Authorization Policies chapter of any IS1200 User
Guide for more details.
Authentication
The process of identifying users based on user name and password to
ensure that only authorized users can access the IS1200.
B
Basic Search
A search made from the Search page using only the Search field.
Searches only the content found in the fullText field populated
during classifications.
C
CAS Device
CASID
148
EMC’s Content Addressed Storage (CAS) devices are cluster-able
archival devices that host archival business file content such as email,
office productivity files (like word processing and spreadsheet files),
images, and other file documents.
A unique IS1200 ID for each classified file that the system generates
during basic classification.
Glossary
Centera Server
The EMC Centera server is a networked storage system specifically
designed to store and provide fast, easy access to fixed content
(information in its final form). It is a CAS device providing long-term
retention and assured integrity designed to store and manage data
that require or have legally mandated retention periods, for example
medical records and files relevant to legal matters.
Celerra Server
An EMC server designed to store and manage archival data. The
Celerra File Level Retention (FLR) server also allows enforcing
enterprise or governmental retention policies.
checkpoints,
checkpointing
Checkpoints and checkpointing allow IS1200 jobs and services to
resume more efficiently if the job or service is paused or stopped
before it completes. Basically, the IS1200 records “bookmarks” about
what file or object was last processed. This allows the IS1200 to skip
to the bookmark—the checkpoint—when the job or service is
resumed, and avoid reprocessing all the files and objects already
processed.
However, checkpoints are not set for every file accessed, instead most
jobs divide file processing into “batches” and the checkpoints
indicate where batches started. Consequently, when a job restarts at a
checkpoint, some objects may be reprocessed again and—in cases
such as a 'Copy' service with 'enable-versioning' option
selected—duplicate versioned files will be created on the target
repository when those objects are reprocessed.
Classification Rule
Classification Service
Rules that the system implements during data classification to extract
metadata, tag files, and assign files to policy groups. The two types of
classification rules are extraction rules and assignment rules.
Sometimes called a “crawl”. An IS1200 service that accesses
job-specified registered repositories and extracts and records their
metadata to later facilitate comprehensive and cross-repository
searches. Classifications extract metadata according to extraction
rules, compute digests for all objects, and assigns files to policy
groups according to assignment rules. See “Assignment Rules” on
page 148, “Extraction Rules” on page 155, “Hash Values” on
page 156, and “Policy Groups” on page 160 for more details.
Classifications may be “full”, every object in the specified repositories
is parsed and its metadata repopulated in the indexes and databases,
or they may be “differential”, see “Differential Classifications” on
page 153 of more details.
149
Glossary
Cluster
CAS
Content Addressable
Storage
CSV
Comma Separated
Values
A set of IS1200 appliance nodes working as a unit. A cluster can
contain a maximum of four nodes. A cluster can be used to control
other clusters, see “Information Center Server” on page 157 for
details.
Rather than address data objects by a file name, at a physical location,
a CAS device uses a content address (hash-code identifiers) based on
file contents to store file objects in a flat file system that maximizes
storage efficiency. This returns a unique identifier (Content Address)
used to store and retrieve data objects.
A file type used to transfer data between applications such as
databases and spreadsheets.
CLI
Command Line
Interface
The CLI is a traditional command line interface that allows direct
communications with the IS1200 “backend” using a the set of
commands defined in the IS1200 Command Line Interface Reference
Guide.
Concepts Search
The standard IS1200 software supports keyword exploration.
However, in the initial stages of the legal discovery process (often
called eDiscovery), keyword search alone may not be as concise or as
time-efficient as required by standard legal timetables.
Concepts augments standard keyword searching by automatically
suggesting filters based on the results of a current search. By default it
looks for concepts based on persons, countries, noun groups,
organizations, company names, and products.
Concepts Search is an optional module that requires an additional
license key for each IS1200 cluster node. See the IS1200 Concepts
Search User and Configuration Guide for complete details.
conceptfinder Ruleset
The conceptfinder ruleset is an assignment ruleset that extracts the
concepts listed in the Review/Analysis Results Grouping Concepts pane,
which is only available when a valid Concepts license is installed on
the IS1200. The conceptfinder ruleset must be used in deep
classifications to get the best results in Review/Analysis from the
Concepts heading of the Results Grouping pane.
The ConceptFinder_DWF assignment ruleset combines both the
conceptfinder ruleset and the DocsWithoutFullText ruleset. See
“DocsWithoutFullText Assignment Ruleset” on page 154 for more
details.
150
Glossary
connectors
Connectors are IS1200 optional modules that allow an IS1200 to work
with repository types beyond the standard CIFS and NFS
repositories. See “optional modules” on page 160 for more details.
Optional module connectors require separate licenses to be purchased
and installed on all nodes of an IS1200 cluster. For a complete list of
optional modules available, see the Introduction chapter of any IS1200
User Guide.
Some connectors, such as the Microsoft Exchange Server Connector,
require agents. Agents are additional server platforms, usually
Windows servers, that provide the additional CPU cycles and
network staging the IS1200 needs to work with the repository types
they connect to.
All connectors have their own user guides which can be accessed from
the Kazeon Documentation link on the IS1200 Manager page
(https://<yourIS1200Name>/manager).
Container file/object
A file (object) that contains other files (sub-objects), such as a ZIP,
TAR, JAR, and PST or NSF files. The container file is often called the
“parent” and the contained objects are called “children”. Container
objects should not be confused with files that have embedded objects,
such as Microsoft Word files that have embedded charts or graphics
(OLE).
Custodian
A legal term used by Legal Service Providers (LSP) and other legal
personnel to describe the owners or responsible parties for electronic
documents pertinent (responsive) to a legal matter.
D
Data
Datamap
A file of any type and size such as a short email, a word processor
document, or a large spreadsheet.
A report that lists the electronic storage locations of all possible
sources of relevant ESI. This can include standard file servers,
groupware servers, email servers—and their backup and archive
systems—as well as custodian’s desktop and laptop computers.
Data-Mount
The NFS file system that is accessed by the IS1200 to parse data and
extract metadata.
Data Server
The file server that exports an NFS or CIFS file system so that the
IS1200 can classify data on the file system to create metadata.
151
Glossary
Data-Share
The CIFS file system to be accessed by the IS1200 to extract metadata.
Data Repository
A networked file system registered with the IS1200 so it can be
classified, searched, and reported on. Data repositories created on the
IS1200 itself (sometimes called localdatafs) are strongly
discouraged!
Data Verification
Builds on Auditing and is only available when system auditing is
enabled. For job services like Actionable Services Copy or Move,
Legal Hold Copy, and Single Step Collections, Data Verification
generates an audit trail proving that files were not altered during
these actions. This is especially valuable in eDiscovery situations.
Complete details are available in the Auditing and Data Verification
chapter of any IS1200 User Guide
Deduplication
A process that identifies file or email object and sub-object duplicates
based on their digest values (See “Digest Values” on page 153 for
details).
In the 4.7.0 and prior versions of the IS1200 software, deduplication
was only available for export actions (Actionable Services such as
Download, Legal Export, and Copy). This allowed exporting only the
unique files and email objects from a set of search results. With IS1200
version 4.8.0, deduplication's functionality is expanded and is
automatically applied during case collections and processing to allow
displaying deduplicated search results. Note that when deduplication is
applied to display of search results, duplicates are only suppressed
from display, however duplicates are physically removed from
exported file sets.
Deduplication is available only in the ECS version of IS1200 and is
applicable only in case context.
DeDuplication view is configurable as deduplication and
non-deduplication view. This allows to view whether any object has
got duplicates in search results and the duplicate of the Original (in
the search results).
Besides the automatic deduplication of collections and processing,
deduplication may also be started manually from the IS1200's case
dashboard.
152
Glossary
Deduplication reports describing how a particular job or service
applied deduplication are available. The reports can be accessed from
the IS1200 case dashboard as well as from web search. Reports can list
all results, only unique (deduplicated) results, or percentages of
unique and duplicates.
Reduplication is a process that allows the duplicates of unique files to
be identified so tagging processes can apply metadata tags to the
unique files as well as all its copies. Legal Tags reduplication can be
done after documents are added to the case.
Differential
Classifications
Differential classifications do not re-classify all file objects in the
selected repositories. Instead, they examine the metadata from
previous crawls, and if there is no previous metadata (indicating the
object is new since the last classification) or the metadata has changed
(based on atime, or mtime changes), then the object is parsed and its
metadata re-populated in the database.
Note: System classification configuration settings default to using mtime to
determine if files have changed for differential classifications. If atime is
desired instead, see the Using atimes for Differential Crawls section of the
Configuration Files and Utilities appendix of any IS1200 User Guide for details
on resetting the default to atime.
Additionally, atime may be applied only to selected classifications by
initiating them from the Command Line Interface, see the add service
deep-classification command and the crawl-atime-check-enabled
option in the IS1200 Command Line Interface Reference Guide for details.
Digest Values
Digests are numerical values calculated based on file and email
content and are unique for all unique objects. Digest values allow file
objects to be compared very quickly. Digests are calculated during
basic and deep classifications or during collections or processing
when indexing is enabled.
Digests are calculated differently for standard files, emails, and
container objects. For standard files, a physical digest is computed for
the entire file much like a hash value.
For email objects, just the subject, the message content (including
attachments), and certain specific addresses are combined and an
email digest value is calculated from the combination. Container
objects, like ZIP or PST files, and their sub-objects have digests
calculated both as complete objects and as individual sub-objects.
153
Glossary
Note: Calculating email digests requires access to the email object's fullText
and only classifications that include the fullText rule can produce email
digests. Emails classified without the fullText rule receive the same physical
digest that other files do. Consequently, identical emails on different
repositories, one classified with and one without the fullText rule, will not be
identified as duplicates.
Domino Sever (Lotus)
Domino XML
Language (DXL)
DocsWithoutFullText
Assignment Ruleset
A Lotus server providing groupware solutions and storage.
A Lotus version of eXtensible Markup Language (XML) used to
import and export Lotus email files.
Some file objects, such as graphics files (examples are.jpeg, .gif, or
.bmp files) contain no text, and hence will have no fullText
extracted by the FullTextRuleset, see “fullText” on page 156 for more
details. In legal cases, these files may still contain responsive
information, but not textual information that can be located by text
searches. The DocsWithoutFulltext assignment rules identifies these
files and adds the metadata tag and value
“DocWithoutFulltext=true” to all files that contain no searchable
text. This allows these files to be easily searched for later, and
inspected for legal responsiveness by non-search methods.
The ConceptFinder_DWF assignment ruleset combines both the
DocsWithoutFullText ruleset with the conceptfinder ruleset. See
“conceptfinder Ruleset” on page 150 for more details.
Note: Parent file objects that don’t contain text (such as .zip, .tar, and .pst files)
are not tagged with the DocWithoutFulltext tag.
Documentum Sever
(EMC)
The EMC Documentum server manages business content including
documents, photos, video, medical images, e-mail, Web pages, fixed
content, XML-tagged documents, and so on. The Documentum core
is a repository that stores content securely under compliance rules
and appears as a unified environment, even though content may
reside on multiple servers and physical storage devices within a
distributed environment.
E
eDiscovery
154
The process of reviewing electronic files to determine their relevances
and responsiveness to a legal matter or case.
Glossary
eDiscovery Case
Manager
An IS1200 tab that facilitates eDiscovery for Legal Service Providers.
Electronic Discovery
Reference Model
(EDRM)
The EDRM was a Project created to provide standards and guidelines
for the electronic discovery market. The model defines a common,
flexible and extensible framework for the development, selection,
evaluation and use of electronic discovery products and services.
Enterprise Vault
eth1, eth2
Extended Attributes
Extraction Rules
Exchange Server
(Microsoft)
A Symantec networked repository for archived email.
Most IS1200 platforms require two ethernet connections for proper
deployment. These connections are called eth1 and eth2, must each
have unique IP addresses, and must be GigaBit, or 1GB/sec or faster,
connections. Additionally, all network segments between eth1 and all
registered metadata and data repositories must be gigabit
eth1 is used to communicate between the IS1200 and its registered
repositories. The IS1200 hostname should be DNS mapped to the eth1
IP address.
eth2 must be connected to a private network between the IS1200
nodes and is used to coordinate and balance system wide operations.
eth2 IP address should not be DNS mapped.
User-defined keywords that are extracted during data classification.
Extraction rules are a type of classification rule. They extract
user-defined keywords (custom metadata) to add to the metadata file.
Extraction rules are grouped into Extraction Rule Sets (ERSs). See the
Policies: Classification, Extraction and Assignment Rules chapter of any
IS1200 User Guide for more details.
A Microsoft server designed to store and manage email.
F
Federation
Federation Server
Filer
A defined group of member-clusters on a Federation server that can
be managed, searched, and reported on as a group. Member-clusters
are referred to as Federated clusters.
A single-node IS1200 server, with a Federation license, that allows
consolidated searching and reporting of up to eight Federated
member-clusters of its defined Federation.
A file server that exports its file systems using NFS or CIFS protocol.
155
Glossary
fullText
fullText is the “content” portion of a file, for example this is the textual
content of word processing files and the message body of emails.
fulltext is an extraction rule that is used to save file textual content as
metadata to the Search Index during classifications. It saves up to 10
megabytes of content by default. This default may be changed, but it
is not recommended. Fulltext extraction is required by
Review/Analysis for the Previewer pane to work and to generate
Concepts in the Results Grouping pane.
fulltext, is extracted differently for container objects and sub-objects, and
for files with embedded objects.
Container objects (such as ZIP or PST files) and their sub-objects
are classified individually and the fulltext of the parent container
file, and for each child sub-object, is extracted and added to the
relevant metadata repository separately.
Files with embedded objects (such as a Microsoft Word file with and
embedded spreadsheet), are classified together. The fulltext of the
embedded object is included in the fulltext of its parent object and
not collected separately.
For more details on fullText, see Chapter 1 of the IS1200 Metadata
Reference Guide.
G
Groupware
Collaborative software designed to help people involved in common
tasks achieve their goals. Incorporates services such as email,
calendaring, text chat, wiki, web-sharing, document control, and
advanced search.
H
Hash Values
Hash values are used to compare one file with another for duplicates.
An extremely simplified description of hashing is that the numeric
values of all bytes in a file are added into a grand total. The chances of
two different files yielding the same result (hash value) are remotely
small, so hash values can be used to identify duplicate files, or
compare files with the same name to decide if they have been
modified.
156
Glossary
Computing hash on an entire file is called a full-hash, and computing
hash on a portion of the file is called a partial-hash. A “partial hash”
may also be used to increase classification speed and “hashing” can
be turned on, or off to increase classification speed.
I
identity
A single entry in the Identity Vault database. The identity contains a
single username and password that the IS1200 can retrieve when it
needs to access a registered data or metadata repository or other
server like and authentication service.
Identity Vault
An encrypted database of usernames and passwords the IS1200 uses
to store the credentials used to access registered data repositories,
send email notifications, and work with authentication services.
Information Center
Server
The standard IS1200 server offers clustering as a scalable solution for
classifying, searching, and reporting on registered network
repositories. While clustering is ideal for scaling to large numbers of
files on a LAN, it is not a viable solution for WANs. Enterprises with
multiple IS1200 clusters deployed, or IS1200 clusters deployed in
remote offices need the ability to setup and manage unified reports
and searches across all their clusters. The IS1200 Information Center
server provides this solution.
Each Federation server supports one federation. A Federation may
have up to eight clusters (with four nodes each) included in it. Once a
federation is established, it becomes a central management point
allowing classifications, search, and reports to be setup or managed
on all the federations members from the Information Center server.
See the IS1200 Information Center User and Configuration Guide for
complete details.
Intelligent Platform
Management
Interface (IPMI)
IS1200 clusters may contain more than one node. Normally each node
communicates with the others to share information and workload.
The IS1200 appliance includes an Intelligent Platform Management
Interface (IPMI) to shut down nodes when individual nodes or
software errors would degrade the overall cluster performance. The
IPMI is an autonomous micro-controller—installed in all cluster
nodes—used by the cluster’s “leader” node to power down nodes
with errors or performance problems. The IPMI requires its own
unique IP address, but communicates over the eth1 port, see “eth1,
eth2” on page 155 for more details.
157
Glossary
K
Kazeon EVAgent
An IS1200 service, installed on the Enterprise Vault server, that allows
the IS1200 to directly open and access Enterprise Vault email for
classification services.
Kaz-mount
The NFS file system that is the IS1200 metadata repository. on which
the IS1200 stores metadata.
Kazeon Query
Language (KQL)
A programming language used in classification and assignment rules
to identify files that should receive specified metadata tags.
KQL Reserved Words
The KQL language reserves the following words. Consequently, they
are not allowed to be searched for, or used as tags or aliases.
"ADD", "ALL", "ALTER", "AND", "ANY", "AS", "ASC", "AVG",
"BETWEEN", "BY", "CASCADE", "CHECK", "COLUMN", "COUNT",
"DESC", "DISTINCT", "ESCAPE", "EXISTS", "FROM", "FULL",
"GRANT", "GROUP", "HAVING", "IN", "INTO", "IS", "JOIN", "KEY",
"LEFT", "LIKE", "MAX", "MIN", "NOT", "NULL", "ON", "OR",
"ORDER", "OUTER", "REVOKE", "RIGHT", "SELECT", "SET", "SUM",
"UNION", "UNIQUE", "UPDATE", "VALUES", "VIEW", "WHERE"
Kaz-server
The file server where the metadata repository is located.
Kaz-share
The CIFS file system on which the IS1200 stores metadata.
Kaz Schema
Defines the set of metadata fields used to build a Search Index for
registered data repositories (file systems).
L
Legal Hold
Files placed on legal hold are either copied to a secure secondary
location where they can preserved for later use, or are locked in their
original locations against further change until a legal matter is
resolved.
Legal Service Provider
(LSP)
A lawyer or trained legal professional that provides legal services for
a fee.
Local
localdatafs
158
Refers to the local resources (usually the metadata repository) of the
Federation server.
A data repository created on the IS1200 itself. This practice is not
recommended.
Glossary
localkazfs
Logging rule
A metadata repository created on the IS1200 itself. This practice is not
recommended.
Logging rules audit user actions on files such as file access, creation,
modification, and deletion.
M
Manifest Reports
Manifests are reports that summarize the results of an IS1200 job or
service. Manifests are produced for Collections (from either
Administration or the Case Mgmt) and for some Actionable Services.
Collection Manifests summarize what files were, or were not
collected during a collection. Actionable Service Manifests reconcile
Actionable Services object-counts with the search result object-counts
they are performed on because processes such as deduplication can
result in the two counts not matching. The reports details the count of
differences and the reasons for the differences. For more information,
see Manifests in the IS1200 Web-Search User Guide.
Note: Collection manifests are available ONLY for collections done from
v4.6.0 or later, earlier versions did not generate collection manifests.
Member-cluster
Metadata
Metadata Repository
Any of the clusters registered to a particular Federation.
Data about data. Metadata is used to search for information and to
create reports. Metadata can be file system or custom metadata that
the IS1200 extracts from files during classification. File system
metadata includes file type, and file path extracted during basic
classification. Custom metadata is generated during deep
classification.
A registered repository the IS1200 uses exclusively to record the
metadata extracted during classification services on the registered
data repository the metadata repository is mapped to.
The primary metadata repository is the host of the repository
registration database, the report results database, Environment
Discovery job results, Auditing and Data Verification databases, and
miscellaneous databases the cluster requires for routine operation.
Collectively these are called the Cluster Data Base.
Metadata repositories created on the IS1200 itself (sometimes called
localkazfs) are strongly discouraged!
159
Glossary
N
Namespaces
IS1200 software, versions 4.0 and higher, organize metadata fields
into hierarchy defined by namespaces. Namespaces group similar sets
of tags, for example all the file level tags such as FileType, FileSize,
aTime, and cTime are grouped together in the System namespace. See
the IS1200 Metadata Reference Guide for complete details.
Network File System
(NFS)
A protocol used primarily by Unix based computers for accessing
computer systems and filers over the internet.
Network Information
System (NIS)
A network naming, administration, and authentication system for
smaller networks that was developed by Sun Microsystems and is
used primarily by Unix systems.
Node
Notes Storage File
(NSF)
A single IS1200 appliance.
A standardized storage file format used by Lotus to store email,
attachments, notes, calendars, and so on.
O
optional modules
The standard IS1200 license provides a default set of features that
allows the IS1200 to register, classify, and search and report on CIFS
and NFS data repositories. Optional modules are additional software
licenses that can add further capabilities, such as being able to work
with repository types other than CIFS and NFS, or providing
Concepts Search capabilities, or applying legal hold. Some optional
modules require connectors, see “connectors” on page 151 for more
details. For a complete list of available optional modules, see the
Introduction chapter of any IS1200 User Guide.
P
160
PEA Files
A Pool Entry Authorization (PEA) file is generated by the Centera
server administrator. A PEA file defines what applications and users
can perform read, write, delete, query, copy, or hold operations for
Centera objects.
Policy Groups
Associates one or more authorization rule and logging rule with one
or more files to protect information and audit user actions on files.
Glossary
PST Files
Personal STorage files are generally used by email programs like
Microsoft Outlook to store user email locally. PST files are also called
“composite” files, because they are packages meant to efficiently
store a number of smaller related files. Another example of a
composite file is a ZIP storage file
R
Retention
Roles
The process of enforcing corporate or legal standards for how long
certain kinds of files must be preserved for access. Examples of
retained files include files responsive to legal matters and medical
records.
All IS1200 users have a role, either admin, auditor, or end-user. If a
legal license is installed, there may also be legaladmin,
legalsupervisor, legalreviewer, or a custodian. Roles
determines what parts of the IS1200 interface may be seen, and how
much of search and report results are displayed.
S
Search Analytics
Pre-Processing
Search Analytics Pre-processing was introduced in release 4.5.0 to
minimize search results display time and improve the overall
efficiency of eDiscovery culling. Analytics Pre-processing is an
integral, automatic, post-processing job performed after any job that
modifies the Search Index. Analytics Pre-processing trades an
increased post-job indexing period for significantly reduced search
results display times after the affected jobs complete.
A variety of jobs requires Search Index changes and therefore require
Analytics Pre-processing. These include Collections, Classifications,
Delete, and Tagging jobs. The time required by Analytics
Pre-processing is determined primarily by the number of objects in
the affected data repository, the number of distinct analytic (result
filter grouping) attributes (such as custodians, mail senders, mail
recipients, sender domains, recipient domains and so on.), and the
read/write performance of the metadata repository associated with
the data repository.
Additionally, once any Analytics Pre-processing job is launched, all
subsequent Analytics Pre-processing jobs (that might be required by
other concurrent jobs-in-progress) wait for the current Analytic
Pre-processing job to finish. However, before beginning any Analytics
Pre-processing job for a particular data repository, the IS1200 checks
161
Glossary
all other jobs-in-progress for that repository to see if they might also
require Analytics Pre-processing. If other jobs are found, the IS1200
waits for all these jobs to finish in order to launch a single Analytics
Pre-processing job for all the jobs that affected the Search Index for
that data repository.
Therefore, there are two best practices suggested for scheduling jobs
that affect the Search Index:
•
Schedule large classifications or collections such that both they,
and the Analytics Pre-Processing they require, can both fully
complete before starting any other job. This allows the IS1200 to
most efficiently schedule the required processing resources. Large
jobs are those that affect data repositories with tens of thousands
of objects or terabytes of data.
•
Schedule small jobs (such as incremental collections, or
post-search tagging operations) to run concurrently so the IS1200
can identify their common Analytics Pre-processing requirements
and group them into a single job.
Note: IS1200’s that are upgraded to v4.5.0 may need some additional
configuration to make the most efficient use of Analytics Pre-Processing. See
the Configuring the IS1200 To Use Proactive Indexing section of the Configuration
Files and Utilities appendix of any IS1200 User Guide for complete details.
Search Index
SharePoint Sever
(Microsoft)
snippets
An IS1200 database that stores and indexes the file content metadata
(including extended attributes, and fullText) for standard and custom
user-defined metadata produced by extraction rules during
classifications.
A Microsoft server in the groupware category.
A snippet is a sub-set of a document’s actual content. Snippets are
only displayed if they are enabled in Review/Analysis Preferences, and
only in Paragraph View immediately under the first line of the result
listing.
After a keyword search completes, result snippets are created as
small standard size chunks of data taken from the text surrounding a
search query hit. For example, if a search is made for “medicine”, the
snippet will contain about 300 bytes of the text surrounding the
paragraph where the word “medicine” was found. If multiple search
162
Glossary
hits are found, the most relevant hit is used to create the snippet. For
searches made without keywords, snippets are simply the first 300
bytes of file text.
Snippet size is configurable, see the Configuration Files and Utilities
appendix of any IS1200 User Guide for details on setting snippet size.
In all cases, snippets are taken from the result file’s fullText.
SourceOne Archive
Server (EMC)
The EMC SourceOne server is a comprehensive, policy-based system
that automatically collects, organizes, indexes and retains messages
and associated attachments and stores them in designated archives
connected to shared storage. EMC SourceOne provides indexed
searching that works with both EMC storage and other brands such
as IBM or NetApp.
Special Characters
The IS1200 supports alphanumeric ASCII and UTF-8 characters.
Non-alphanumeric ASCII characters are defined as Special Characters
and include the following:
‘“-_\/!@#$%^&*+={}[]()<>|:;,.?~`
Special characters are not universally supported in the IS1200
interfaces. The following limitations must be noted:
Search Queries and Special Character, Special characters pose a
searching challenge. Because the IS1200 tokenization removes special
characters from indexed text as it is classified, special characters are
never entered into the IS1200 metadata indexes. Consequently,
special characters may not be directly searched for. For more details
see Tokenisation and Stemming in the IS1200 Web-Search User Guide.
While special characters may not be directly searched for, the text
they are included in can be searched. For example, the string
"-ACME-" is tokenized on the hyphens and recorded in the metadata
only as "ACME". Consequently, searching for the string with the
hyphens (-) will NOT work. However, you can search for “?ACME?”
(using the question mark wildcard) which gives the result as
“!ACME!”, “@ACME.”, and so on. See the IS1200 Web-Search User
Guide for more details on wildcards.
Note: The question mark character ( ? ) may not be searched for in filepaths,
even when escaped. This exception is limited to filepath searches only.
163
Glossary
AD login names and NIS login names support only alphanumeric
ASCII and UTF-8 characters, they do NOT support following special
characters:
'"-_\/!@#$%^&*+={}[]()<>|:;,.?~`
However, in Active Directory (AD), registered users may have both an
AD login name and a display name. For example, John Smith may have
the AD login name “jsmith” and the display name “John Smith”.
When new legal supervisors or reviewers are created in the Case
Mgmt using the AD lookup button, they take the display name, not the
login name, and the display name may contain special characters as
described below.
Legal Supervisor Names and Legal Reviewer Names only,
support:
'-_!@#$%^&*+={}[]()|:;,.?~`
do NOT support: " \ / < >
Custodian Names only,
support:
'"-_!@# %^&*+={}[]()|:;,.?~`
do NOT support:
\/<>$
Case Names, Legal Export Profile Names, Repository Names,
Rule Names, and Policy Names only,
support:
_ (underscore)
do NOT support: " - \ / ! @ # $ % ^ & * + = { } [ ] ( ) < > | : ; , . ? ~ `
Email IDs which are used in Legal Hold notification and
Acknowledgements, Search filters, Collection filters and so on,
support:
'-_!#$%^&{}:;,.?~`
do NOT support: " \ / @ * + = [ ] ( ) | < >
Mail Domain Names DO NOT support any special characters.
File names/ Directory names in source and destination file names
only,
support:
'-_!@^+={}[]()<>;,.~
do NOT support: " \ / # $ % & * | : ? `
Tag Names only,
support:
_ (underscore)
do NOT support: ' " - \ / ! @ # $ % ^ & * + = { } [ ] ( ) < > | : ; , . ? ~ `
164
Glossary
Tag Values only,
support:
'-_\/!@#$%^&*+={}[]()<>|:;,.?~`
do NOT support: " (double quote)
Rules definitions, special characters must be “escaped” before they
may be used in rule definitions. To escape a character use a \ before
the character.
Search technology uses reserved words, stop words, special
characters, tokenizers, and so on. These are common to almost ALL
search technologies and not just a Kazeon search engine
manifestation. One major reason for such implementation is that if all
the characters and the words are indexed regardless of any semantics,
your search index has a potential to increase beyond any manageable
size since the occurrence of said categories of tokens is so common.
Besides, there is not much value in indexing stop words (as, the, or,
and so on.) and tokenizers (@ , . - and so on.). The omission of such
characters from your search query is just a part of the optimization.
For example, when you “search” for (1+1):2, the characters “(”, “+”,
“)”, and “:” have special meaning in search - the parentheses are used
to specify grouping, the plus is used to specify inclusive terms in a
query, and the colon is using to separate tag from value as in
"filepath:*". In order to use these in your query, you need to escape
them with a backslash, as follows:
\(1\+1\)\:2
However, the escaping does not mean the characters are now a part of
your query. It only means that those characters are not interpreted by
search with special semantics. This query is preprocessed to drop
those characters from the final query which appears as follows when
it is actually executed by the search engine:
fulltext:"1 1 2"
This means that we are searching for a 1 followed by a 1 which is
again followed by a 2 such that there are no other valid indexable
search tokens between the three numbers. The results may match
1-1+2
1:1:2
1-1-2 and so on.
However, they will not match
165
Glossary
1:3:1:2
1-43+1:2 and so on.
Hence to search for (1+1):2, use the following query:
\(1\+1\)\:2
stop words
Stop words consist of the most commonly used words in sentences,
such as “a”, “an”, “the”, and ”and”. If indexed individually, they
would consume excessive amount of metadata storage space, and
consequently are not individually indexed.
If stop words are used in a search query, they are ignored unless they
are parts of quoted phrases. The table below lists all stop words:
Table 132Stop Words
166
a
an
and
are
as
at
be
but
by
for
if
in
into
is
it
not
of
on
or
such
that
the
their
then
there
these
they
this
to
was
will
with
Stemming
Stemming is a search technique designed to increase search efficiency
and broaden relevant search hits. When stemming is used, fullText
indexing first attempts to identify each word’s “stem”, and then
indexes words by their stems. For example, the words “connected”,
“connecting”, and “connectable” all share the same stem and are
indexed under “connect”. Search query criteria are automatically
stemmed, and so querying “connected” returns all instances where
“connect”, “connected”, and “connecting” are used. Nouns like
“connector” are not stemmed. Stemming is ON by default but may be
disabled.
stubs
Stubs are created by many file archiving applications, most notably
email archiving systems. When stubbing is used, and a file object is
moved to archival storage, a “stub” is left behind on the original file
system that points to the archived file’s new location. Thereafter, if a
user attempts to open the archived file from the original filer, the stub
allows that filer to retrieve the archived file and return it to the user
transparently (as if it were still on the original filer).
Glossary
Stubs may be searched for using the metadata field
“mailMessageClass”. For example, use the search query
“mailMessageClass:IPM.Note.ExShortcut” to find email message
stubs.
sub-objects
A file found inside a “container object”, see “Container file/object”
on page 151 for more details. A container file is often called the
“parent” and the contained sub-objects are called “children”.
Sub-objects should not be confused with embedded files such as OLE
objects, for example spreadsheets or graphics embedded in a
Microsoft Word file. Note however, an email message may be a
container object, if it “contains” attachments, or a simple
non-container object but still have a graphic embedded in its body.
T
Tags
The names of metadata fields. Tags are always associated with a
value. For example, the metadata tag “filename” for any given file is
always followed by a value (a text string) containing the actual
filename.
Tokenization
Tokenization is an IS1200 classification procedure that breaks word
strings into “tokens” for better search results. During classifications,
Numbers, AlphaNums, HostNames and EmailAddresses (in
fullText) are tokenized similar to alpha only strings. With
tokenization, the stings “www.kazeon.com”, “fred@kazeon.com”,
and “11,22,333,44” are tokenized into separate words yielding;
“www”,”kazeon”, and “com”; “fred”, “kazeon”, and “com”; and
“11”, “22”, “333”, and “444”. This allows searching for “kazeon” and
getting all email addresses that contain the domain name, while.
U
UTF-8
Unicode Transformation Format - 8, is an 8-bit coding scheme for
digitally representing both the standard western alphabet (Aa-Zz)
and its punctuation characters, and non-western word characters
such as the glyhps found in the Chinese, Japanese, and Korean
languages. UTF-8 encodes all its characters as 8-bit bytes (or octets).
The first 128 UTF-8 characters are identical to the first 128 ASCII
characters and require only one byte each. Non-western languages
are coded using one to four octets each. UTF-8 can encode all of the
1,112,064 code points in the Unicode character set that covers the
majority of languages in use around the world.
167
Glossary
W
Web-Admin
An IS1200 web application used by IT personnel to administer the
server itself, and when the IS1200 is used to help administer other IT
resources. Administration is the preferred interface for administering
the server.
Web-Reports
An IS1200 web application that provides advanced reporting
capabilities based on IS1200 metadata.
Web-Search
An IS1200 web application that provides basic, advanced, and
specialized email searches against IS1200 metadata.
X
XML
eXtensible Markup
Language
168
A file type that uses the XML language to define and describe data
that can be transferred between applications like databases and
spreadsheets.