Custom Fields

Introduction
Types of Custom Fields
The Difference between Single-Value and Multiple-Value Custom Fields.
Single-Value Custom Fields
Multiple-Value Custom Fields
Aggregation of Multiple-Value Numeric Custom Fields
Supported Import Formats
How to Import Data to Custom Fields
How to Import Data to Single-Value Custom Fields
How to Import Data to Multiple-Value Custom Fields
Advanced Settings: Aggregation of Multiple-Value Numeric Custom Fields
Patent Family Level: Example Table with “Patent Family” as Grouping
Portfolio Level: Example Table with “Owner” as Grouping
Patent Family Level: Example Table Grouped by the Attribute “Patent Family”
Portfolio Level: Example Table Grouped by the Attribute “Owner”

Introduction

Custom fields allow you to insert your own data into PatentSight and to analyze groups of patent families predefined by you. However, in contrast to tags, custom fields not only support mapping of text information but also mapping of numeric information to patent families – all you need to do is to import such information into PatentSight.

With custom fields, you can map your own text and numeric values to patent families. You can display these values in charts and tables in PatentSight and use them along with PatentSight indicators.

Types of Custom Fields

Depending on your use case, you can select between three types of custom fields:

Text

The custom field type “text” allows you to map text information to patent families. (e.g., technology classification, products, responsible attorneys, business units etc.).

Numeric

The custom field type “numeric” allows you to map numeric information to patent families (e.g., internal scores, licensing revenue, R&D expenses, prosecution costs etc.).

Notes

The default custom field “notes” is a pre-defined single-value text custom field that allows you to enter a comment on each patent family available in the PatentSight. “Notes” are displayed in the Result List and visible for and editable by all users in the same account (i.e., you and all other users in your account).

When creating a text or numeric custom field, you need to select between single-value and multiple-value:

• Single-value custom fields allow you to map only one value per custom field to the same patent family.
• Multiple-value custom fields allow you to map one or more values per custom field to the same patent family.

The Difference between Single-Value and Multiple-Value Custom Fields.

Single-Value Custom Fields

Single-value custom fields allow you to map only one value per custom field to the same patent family. Single-value custom fields are best used in the following cases:

• You are working with the same patent family definition as used in PatentSight.
• You want to map exactly one numeric or text value per custom field to one patent family.

Example:

Each of the patent families P1 to P3 is internally categorized into exactly one internal technology (text, single-value). Moreover, in an internal valuation, each of the patent families P1 to P3 receives exactly one score (numeric, single-value).

Multiple-Value Custom Fields

Multiple-value custom fields allow you to map multiple values per custom field to the same patent family. Multiple-value custom fields are best used in the following cases:

• You are working on the document level.
• You are using a different patent family definition than PatentSight.
• You want to map one or more numeric or text values per Custom Field to the same patent family.

Example:

The patent family P1 belongs to multiple sub-technologies (text, multiple-value). Moreover, each of the documents D1 to D3, which all belong to the patent family P1, generate a licensing income (numeric, multiple-value).

Aggregation of Multiple-Value Numeric Custom Fields

Patent families are the smallest unit for analysis available in the PatentSight. Therefore, when importing multiple-value numeric Custom Fields, values are aggregated within patent families in the following cases:

• Within the same custom field, More than one value is mapped to the same patent family.

• Within the same custom field, one or more values are mapped to documents that belong to the same patent family.

When analyzing patent portfolios, the values are aggregated across patent families. This applies for both multiple-value and single-value numeric Custom Fields.

The default aggregation method within families and across families is the average (AVG). However, you can choose your preferred aggregation method independently for each step. The following five aggregation options are available:

• AVG (average)
• SUM (sum)
• MIN (minimum value)
• MAX (maximum value)
• LIST (list of all values)

In the below example, the sum is used as aggregation method within families on family level and the average is used as aggregation method across families on portfolio level.

Supported Import Formats

Zeros (“0”) and Empty Cells

Zeros are counted as the numeric value “0”. Empty cells with no value are ignored. This influences some of the aggregation methods within and across families.

Zeros

Empty Cells

Negative Values

Custom fields support the import of negative values, which can also be displayed in charts.

Decimal and Thousand Separators

Custom fields support the import of numeric values with decimal or thousand separators.

Important:

Before importing values with decimal or thousand separators, please make sure that you have the same language settings in your data file and in your browser

Non-Latin Characters

Non-Latin characters are supported. You can import text custom fields written for example in Chinese, Japanese, or Korean.

Letter Case

Custom fields are case-insensitive. This means that no differentiation is made between uppercase (capital) letters and lowercase (small) letters.

Tip:

For details regarding supported patent number formats that can be used for importing Custom Fields, please consult the article → “Importable Number Format.”

How to Import Data to Custom Fields

Custom fields are used to map information to patent families. Therefore, the first column in any data file used to import custom fields must contain the numbers of the patent documents you plan to map information to. Any subsequent columns should contain the information (= values) that you want to map to the patent families.

Depending on the kind of information imported, you can choose between numeric and text custom fields. Depending on the number of values you want to map to one patent family within one custom field, you can choose between single-value and multiple-value custom fields.

	Download the sample data used in “How to Import Data to Single-Value Custom Fields” (Excel format)
	Download the sample data used “How to Import Data to Multiple-Value Custom Fields” (Excel format)

How to Import Data to Single-Value Custom Fields

To map information to patent families using custom fields, you first need to prepare a spreadsheet or a similarly formatted document (e.g., MS Excel) with the information you want to import. To get started, you can also use the sample data provided in this guide.

The column titles in the top row of your spreadsheet can be used as the names of the custom fields created.

	Publication Numbers: The first column of your data file must contain the publication numbers of the documents or patent family representatives which you want to map information to.
	Single-Value text column field "Internal Technology" In this example, column B contains text information that is used to create a single-value text column field. Each cell may contain more than one word. However, only one text value may be mapped to the same patent family.
	In this example, column C contains numeric information that is used to create a single-value custom field. Each cell may contain only one numeric value. Only one numeric value may be mapped to the same patent family.
	Single-value text Custom Field "Notes" In this example, Column D is called "Notes." Notes is a predefined single-value text custom field that allows you to add comments to each patent family. Entries added to the custom field "Notes" are displayed in the Result List and can be seen and edited by all users in your account.

Important:

When importing single-value custom fields, each patent family may exist only once in your list!

1.　In your data file, select the information you want to import and copy it (“Ctrl + C”).

2.　In PatentSight, select “Import Data to Custom Field” under “Import” in the main toolbar.

3.　Paste (“Ctrl + V”) the information copied from your data file into the import dialog box and click on the “Proceed” button.

	Verify the publication numbers that you have pasted. Note: Alternative to pasting, you can select “Open from file” or drag and drop your data file into the import dialog box in the previous step. However, for these alternative import  options, your file must not contain any empty rows above or empty columns to the left of your data columns.
	Click on the X icon to delete the pasted information.
	Click on the info icon for more information on supported formats.
	Under “Separator” you can select your preferred type of separator depending on your import file. Valid separators are commas (“,”), semicolons (“;”), tab stops, spaces (“ “), and vertical bars (“|”).

4.　If your import includes numbers that could not be matched, click on “Edit Matching” to verify and edit such numbers.

5. After having edited ambiguous or not matched publication numbers, click on the “Proceed” button to confirm your changes and to move on.

	Select one or more options to display matched, ambiguous, and/or not matched number.
	Verify the information of matched numbers, including the row from your data file.
	Click on the download icon to export the list of matched, ambiguous and/or not matched numbers.
	To edit ambiguously matched or not matched numbers, click on the respective number, enter any corrections, and confirm by clicking out or pressing the Enter key.

6.　In this step, you can create new custom fields, add data to existing custom fields, overwrite data in existing custom fields, or ignore columns with redundant data.

	The column with the publication numbers is recognized under “Patent Family.”
	Each further column from your data file is recognized as one custom field.
	“Notes” is recognized as the pre-defined single-value text custom field “Notes.”
	Click on “Manage Custom Fields” to access and manage existing custom fields.

7.　To create a new custom field, click on “Select Custom Field“ and select “Create New Custom Field.”

8.　Define the settings of the new custom field and click on “Save” to confirm.

	The column title from your data file is automatically used as the name of the custom field. You can edit the name if necessary.
	Under “Type,” select “Text” if your column contains text values and “Single-Value” if your data file contains each patent family only once.
	Optional: Under “Advance Settings,” check “Only Allow Predefined Input Values” to enter a set of predefined input values for this custom field.
	Optional: Open “Description” to enter a text to be displayed as a tooltip when you use this custom field as a measure, attribute, or search field.
	Optional: Open “Sharing Settings” to grant other users in your account access to the custom field

9.  If you have selected “Only Allow Predefined Input Values”, any values that do not meet the predefined criteria will be highlighted in red as wrong input. To correct such values, click into the cell and select one of the pre-defined input values. Alternatively, select “Ignore” to ignore this row (i.e., no value will be mapped to this patent family).

10.　Move on to the next column, click on “Select Custom Field” and select “Create New Custom Field”.

11.Define the settings of the new custom field and click on the “Save” button to confirm.

12. To finalize the custom field import, click on the “Proceed” button.

13.　You can use the custom fields created in the search panel, in charts, and in tables

	Text and numeric Custom Fields can be used as search fields in the search panel
	Text and numeric Custom Fields can be used as groupings in charts and tables
	Numeric Custom Fields can be used as measures in charts and tables.

How to Import Data to Multiple-Value Custom Fields

To map information to patent families using custom fields, you first need to prepare a spreadsheet or a similarly formatted document (e.g., MS Excel) with the information you want to import. To get started, you can also use the sample data provided in this guide.
The column titles in the top row of your spreadsheet can be used as the names of the custom fields created.

	Publication Numbers The first column of your data file must contain the publication numbers of the documents or patent family representatives which you want to map information to.
	Multiple-value text custom field In this example, column B contains text information that is used to create a multiple-value text custom field. Each cell may contain one or more terms. More than one value may be mapped to the same patent family.
	Ignore (redundant information) In this example, column C contains document numbers that relate to the values in column D. Since this is redundant information, you may ignore this column.
	Multiple-value text Custom Field In this example, column D contains numeric information that is used to create a multiple-value numeric custom field. Each cell may contain only one numeric value. More than one numeric value may be mapped to the same patent family.

Important:

When importing multiple-value custom fields, each patent family may exist more than once in your list. You can also list different documents belonging to the same family. However, all information will be aggregated on the patent family level.

1.　In your data file, select the information you want to import and copy it (“Ctrl + C”).

2.　In PatentSight, select “Import Data to Custom Field” under “Import” in the main toolbar.

3.　Paste (“Ctrl + V”) the information copied from your data file into the import dialog box and click on the “Proceed” button to move on.

	Verify the publication numbers that you have pasted.
	Click on the X icon to delete the pasted information.
	Click on the info icon for more information on the supported formats.
	Under “Separator” you can select your preferred type of separator depending on your import file. Valid separators are commas (“,”), semicolons (“;”), tab stops, spaces (“ “), and vertical bars (“|”).

4.　If your import includes publication numbers that could not be matched, click on “Edit Matching” to verify and edit such numbers.

5.　After having edited ambiguous and not matched publication numbers, click on the “Proceed” button to confirm your changes and to move on.

	Select one or more options to display matched, ambiguous, and/or not matched number.
	Verify the information of matched numbers, including the row from your data file.
	Click on the download icon to export the list of matched, ambiguous and/or not matched numbers.
	To edit ambiguously matched or not matched numbers, click on the respective number, enter any corrections, and confirm by clicking out or pressing the Enter key.

6.　In this step, you can create new custom fields, add data to existing custom fields, overwrite data in existing custom fields, or ignore columns with redundant data.

	The column with the publication numbers is recognized under “Patent Family”.
	Each further column from your data file is recognized as one custom field.
	Click on “Manage Custom Fields” to access and manage existing custom fields.

7.　To create a new custom field, click on “Select Custom Field“ and select “Create New Custom Field.”

8.　Define the settings of the new custom field and click on the “Save” button to confirm.

	The column title from your data file is automatically used as the name of the custom field. You can edit the name if necessary.
	Under “Type,” select “Text” if your column contains text values and “Multiple-Value” if your data file contains each patent family only once.
	Optional: Under “Advance Settings,” check “Only Allow Predefined Input Values” to enter a set of predefined input values for this custom field.
	Optional: Open “Description” to enter a text that will be displayed as a tooltip when you use this custom field as a measure, attribute, or search field.
	Optional: Open “Sharing Settings” to grant other users in your account access to the custom field.

9.　Move on to the next column, click on “Select Custom Field” and select “Ignore” to ignore the data.

Note: The “Ignore” option allows you to omit all columns do not contain information intended for the creation of custom fields. Therefore, you do not have to delete such information from your data file.

10.　Move on to the next column, click on “Select Custom Field,” and select “Create new Custom Field.”

11.　Define the settings of the new custom field and click on the “Save” button to confirm.

	The column title from your data file is automatically used as the name of the custom field. You can edit the name if necessary. Note: The same name cannot be used more than once. This also applies to the use of the same custom field name by different users in the same account.
	Under “Type,” select “Numeric” if your column contains numeric values and “Multiple-Value” to map one or more values to the same patent family.
	Optional: Under “Advanced Settings,” check “Allow Different Aggregation Methods Within Families and Across Families” to allow different aggregation methods within families (patent family level) and across families (portfolio level). If left unchecked, the aggregation method that you select on the portfolio level in charts or tables will always be adapted as the aggregation method on the patent family level.
	Optional: Open “Description” to enter a text that will be displayed as a tooltip when you use this custom field as a measure, attribute, or search field.
	Optional: Open “Sharing Settings” to grant other users in your account access to the custom field.

Advanced Settings: Aggregation of Multiple-Value Numeric Custom Fields

This example illustrates how numeric values are aggregated if different aggregation methods within families and across families are forbidden or and if different aggregation methods within families and across families are allowed. Within the multiple-value numeric custom field “Score”, the patent families P1 and P2, which belong to Company A, are mapped to the following values:
• The values “-1” and “5” are mapped to the patent family P1.
• The values “-5” and “1” are mapped to the patent family P2.
Case 1) Different aggregation methods within and across families are forbidden. The values are aggregated using the same aggregation method on both levels.

Patent Family Level: Example Table with “Patent Family” as Grouping

Portfolio Level: Example Table with “Owner” as Grouping

Case 2: Different aggregation methods within and across families are allowed. “MAX” is the aggregation method within families.

Patent Family Level: Example Table Grouped by the Attribute “Patent Family”

Portfolio Level: Example Table Grouped by the Attribute “Owner”

12.　To finalize the custom field import, click on the “Proceed” button.

13.　You can use the custom fields created in the search panel, in charts, and in tables 

	Text and numeric custom fields can be used as search fields in the search panel.
	Numeric custom fields can be used as measures in charts and tables.
	Text and numeric custom fields can be used as attributes in charts and tables.