How Can We Help?
Customizing fieldsCustomizing fields
Who is this page for?
This page is intended for clients who have recently bought Pure, or a new part of Pure, and are currently or will soon be working on an implementation project with a Pure Implementation Manager. It provides general information that is applicable to all Pures; your Implementation Manager will help you address the details specific to your individual case.
Introduction
When you are deciding what data to add to your Pure, you may find that you need to make adjustments or additions to the default fields. For example, you might need to migrate data from another system stored in fields that have no obvious equivalents in Pure. To help you customize your Pure to suit your needs, it is possible to edit some default fields, to create new fields and also to remove some fields.
Note that some default fields cannot be edited or removed because they are tied to functionality in Pure.
Editing default fields
Editing values in dropdown fields (classification schemes)
The values in dropdown fields are defined by classification schemes, many of which can be edited at Master data > Classification Schemes. You can also use the global search to find classification schemes by the name of a value in the dropdown. Note that if your Pure has multiple UI languages, any values added to the classification scheme must be provided in every UI language. Note that some classification schemes cannot be edited.
Editing descriptions of types within editorial data content types
The type fields for editorial content types (e.g. Research Outputs) have descriptions which will appear in a popover if the User hovers over the type. These descriptions can be customized to help your Users understand which type to choose, by using the type configuration at Administrator > (e.g.) Research Outputs > Types.
Editing text resources
Most text resources in the UI can be edited, including the names of fields and content types, and help texts. To find and edit text resources, go to Administrator > Messaging and text resources > Text resources. There are risks to changing text resources. If the new name deviates too far from the default, it might obscure the original purpose of the feature and lead to confusion if there is functionality tied to it. When communicating with Pure Support, use the default names. Note that it is not possible to delete a text resource that has a default value.
Adding new fields
Enabling fields that do not appear by default
Some little-used fields are not enabled by default. Before considering adding a new field, check whether what you want already exists and just needs to be enabled. Go to Administrator > System settings and look through the settings for the content type to which you wish to add a field.
Some fields do not appear until a classification scheme that has only one value by default is given a second value, e.g. Impact status on the Impacts content type. Before considering adding a new field, go to Master data > Classification schemes to check whether a scheme already exists for it.
Adding free-text Profile information fields to Persons and Organisational Units
The Persons and Organisational Units content types each have optional free-text Profile information fields, which are enabled by default with a single type ('Person profile' and ‘Organisation profile’, respectively). To create new types of Profile information fields, go to Master data > Classification schemes and find the relevant scheme, e.g. Profile information type, and add new classifications with the names of the new types.
Adding single-choice (radio button) Category fields to editorial content types
Most editorial data content types have optional single-choice (radio button) Categories fields, which are by default disabled. To enable a Category field for a given content type, go to Master data > Classification schemes and find the relevant scheme, e.g. Research Output: Categories, then add new classifications with the names of the values for the radio buttons. The scheme must contain at least two values for the field to appear. Finally, go to the settings for the types of the content type, e.g. Administrator > Research Outputs > Types, and assign the category and peer review relations to the relevant subtypes.
Adding free-text Description fields to editorial content types
Many content types have optional free-text Description fields, which are managed in a classification scheme. To create a new free-text Description field for a given content type, go to Master data > Classification schemes and find the relevant scheme, e.g. Activity: Descriptions, then add a new classification with the name of your new free-text field.
Adding dropdown Indicator fields to Activities
The Activities content type has an optional dropdown field called Indicators that is by default disabled. To enable an Indicator field for an Activity subtype, first go to Master data > Classification schemes and find the Activity: Indicators scheme, then add new classifications with the names of the values for the dropdown. Then go to Administrator > Activities > Types, and assign the indicator relations to the relevant subtypes.
Creating custom Keyword Groups (free text or classification scheme)
A Keyword Group is a custom field that contains Keywords that categorize records. Keyword Groups may allow free-text values, values from a classification scheme (either default or custom), or both. Keyword Groups can be created by Users with the role Administrator or Technical Administrator.
For an overview of Keyword Group functionality, see Decision matrix for creating new fields below.
Requesting custom-defined fields (CDFs)
Custom-defined fields (CDFs) can be created for individual clients to fulfil specific requirements. During implementation, your Implementation Manager can request a CDF for you. It will then be considered by a panel of subject matter experts at Elsevier. If approved, your Implementation Manager will create the CDF in your Pure(s).
See Custom-defined fields (CDFs). For an overview of CDF functionality, see Decision matrix for creating new fields below.
Decision matrix for creating new fields
Criteria | Profile information | Category | Description | Indicator | Keyword Group | CDF |
---|---|---|---|---|---|---|
Use free text data type | X | X | X | X | ||
Use classification scheme (radio button or dropdown) data type | X | X | X | X | ||
Use free-text and/or classification scheme (dropdown) data types | X | X | ||||
Use other data types (e.g. numeric or date) | X | |||||
Select multiple values | X | X | ||||
Make the field mandatory | X | X | ||||
Limit how many values can be entered for the field | X | |||||
Mark the field sensitive | X | |||||
Configure the field once and apply to multiple content types | X | |||||
Apply to Persons and Organisational Units | X | X | X | |||
Apply to master data content types other than Persons and Organisational Units | X | X | ||||
Propagate field values to other content types | X | |||||
Apply to subtypes of an editorial content type | X | X | X | |||
Specify where the field is placed in the editor window | X | |||||
Use as a filter in the content type list | X | X | X | |||
Show the value of the field in the Reporting Module | X | X | X | X | X | |
Use as a filter in the Reporting Module | X | X | X | X | ||
Display as a filter on the Portal | X | |||||
Show the value of the field in the Portal | X | X | X | |||
Use in the API | X | X | X | X | X | X |
Use in an XML import | X | X | X | X | X | |
Create without Elsevier approval or assistance | X | X | X | X | X |
Removing fields
Removing default fields
Some default fields can be disabled. Go to Administrator > System settings and look through the settings for the content type for which you wish to remove a field.
Some fields will disappear if its classification scheme contains only one value, e.g. Impact status on the Impacts content type. Go to Master data > Classification schemes to check whether removing values from a scheme will remove the field. Note that this will not be possible if records exist with data in the Description field, or if there is functionality tied to the field for the given content type.
Removing Category fields from editorial content types
Most editorial data content types have optional single-choice (radio button) Categories fields, which are by default disabled. To disable a Category field for a given content type, go to the settings for the types of the content type, e.g. Administrator > Research Outputs > Types, and remove all the category and peer review relations from the relevant subtypes. Note that this will not be possible if records exist with data in the Category field. It is also not possible to remove ‘Research’ category relations from Research Output subtypes, as this is tied to other functionality; if this is the only category relation present, however, then the field will not appear in the editor window.
Removing Description fields from editorial content types
Many content types have optional free-text Description fields, which are managed in a classification scheme. To delete a Description field for a given content type, go to Master data > Classification schemes and find the relevant scheme, e.g. Activity: Descriptions, then delete the ‘Description’ value from the scheme. Note that this will not be possible if records exist with data in the Description field, or if there is functionality tied to the field for the given content type.
Removing Indicator fields from Activities
The Activities content type has an optional dropdown field called Indicators that is by default disabled. To disable an Indicator field for an Activity subtype, go to Administrator > Activities > Types and remove all the indicator relations from the relevant subtypes.
Removing Keyword Groups
Some Keyword Groups appear by default. If you wish to remove these, or any new Keyword Groups you have added, see How to delete Keyword Groups.
Requesting the removal of a custom-defined field (CDF)
Only Elsevier can removed CDFs. During implementation, your Implementation Manager can remove a CDF for you. To check whether a field is a CDF, go to Administrator > Custom-defined fields.
Published at June 13, 2025