Custom Fields
Custom fields are additional fields along with the regular patent fields. You can create a number of custom fields for capturing relevant context specific or company specific information to support even more complex patent workflows in organizations for each record in a project. This is useful when you have additional business context data such as Department/Market/Custom Score/Internal Code/Attorney comments and other items you would like to save and manage per record.
For each project custom field names and their types have to be created first. When you are creating a new project, you have option to import the category schema and custom field types from an existing project. So once you have defined custom field names and their types, you can reuse them in other projects.
There are eight main types of custom fields. You can create "any number of custom fields using these custom field types. After you define the custom fields for the project, you can either fill up the data for them manually or you can import their values using the "Additional Field import" tab in Add Records option. Finally custom fields can be used for filtering and charting just like any other Biblio field.
In spilt view on the result page you can view and edit the Custom fields .

In Detail view of the records you can view Custom fields as an independent Tab

The eight main types of custom fields are described in the table below:
Types of Custom Fields | Custom Fields: Sub Types | Description |
Short Text (255 characters) |
Dropdown; Multivalued
|
Useful for all comment and any other type of data
|
Text (65535 characters)
| Useful for all comment and any other type of data | |
Numeric (Integer) | Dropdown; Multivalued. These two can further be assigned "Is Range" type of custom field. |
e.g., Internal code
|
Numeric (Decimal) | Dropdown; Multivalued. These two can further be assigned "Is Range" type of custom field. | e.g., Science Quotient with values between 0.0 to 1.0 with 1.0 being maximum science quotient and 0.0 being minimum |
Check box | e.g., Has this record been licensed or not | |
Yes/No Option
|
| Useful for Yes/ No type of questions. E.g., Is this record collaborated with University or not |
Date | e.g., Review date or SPC expiry date | |
Attachment | Useful to add attachment to any record present within a project. E.g., Word/Excel/PDF/Images/PPT | |
Table | Useful to hold relational multi-values data per record |
To add a new custom field
- On the Project screen, click the Project Settings tab.
- Click the Custom Field Settings tab.
- Add/ Edit Custom Field Menu will be displayed.
- Select type of custom field from the mentioned list.
- Give Custom Field name to be created.
- Select the custom field sub- type.
- In the Values box, type the appropriate values (if it's a list limited text/numeric field)
- Click Save.
The new custom field is added to each record in your project.
Note: In case of list limited custom fields you have to enter all the valid values for the fields. These will appear as a drop-down per record.
To edit an existing custom field
- On the Project screen, click the Project Settings tab.
- Click the Custom Field Settings tab.
- Add/ Edit Custom Field Menu will be displayed.
- From the list of existing custom fields, select the Edit icon present on top left corner of custom field.(highlighted in image)
- It will take you to specific custom field.
- Make changes to the values.
- Click Update.
The custom field definition is updated.

To remove a custom field
- On the Project screen, click the Project Settings tab.
- Click the Custom Field Settings tab.
- Add/ Edit Custom Field Menu will be displayed.
- From the list of existing custom fields, select the Remove icon present on top left corner of custom field.(highlighted in image)
- Select the option to Remove custom field data or Remove custom field completely.
- Click Yes.

The custom field is deleted from the list. Deleting a custom field type deletes all the record information associated with it.
View/ Add Custom Field Data in PatSeer
Custom Fields cannot be seen in Tabular View. You can see them in Standard view or Biblio section within Detail view of a record. They can also be viewed in Dashlets, if you have selected the particular field to be seen in Dashlet. Adding data for each field is as simple as entering the value for the field.
You can even use these fields for filtering and analysis purpose. These fields can be combined with standard patent fields for filtering and analysis.
Importing Custom Data Points from a File: Generic Excel
Generic Excel option present within Field Import allows to add records and map fields that have to be imported into PatSeer Project.
PatSeer allows you to import your own custom data such as ratings, comments or custom fields from an Excel file. This is useful because in many cases you already have some data in an Excel file or sometimes it‘s also too tedious to update each custom field data online for each record when there are many records in your project.
For example, if you want to import data for DWPI fields like DWPI Title, Abstract, etc., then you can make use of custom fields. Once these custom fields are created then their values can be imported from Excel File using the option Generic Excel.
Note: The name of column header in Excel file should match with custom field name (that has to be mapped), in order to import the values into specific field
Custom Fields for File Imports
Custom Fields can be created and imported for specific File Imports which include WPIX STN TRN, HCAPLUS STN TRN and some Journal Imports like PUBMED MEDLINE TSV, SCIENCEDIRECT RIS, SCOPUS RIS, ENGG. VILLAGE RIS, and RAPRA STN RTF. Each of the file has its own set of custom fields and need to be defined before adding records to a project. Once these custom fields are defined, it will automatically fetch values from the file and put them into specific fields.
It is not mandatory to define these custom fields. If you want to view certain fields present in WPIX STN and HCAPLUS STN files as separate fields, then you can define them as custom fields. In case, you do not define these custom fields then also they will get imported from file but as a part of Abstract or Description.