Page History

Example Value:

Person

Informational Note:

The type of Entity to use for Researcher Profile items. By default, the Person Entity is used, as this is provided out-of-the-box in DSpace.  This would only need to be modified if you have created a heavily customized Configurable Entities data model which does NOT include Person.

Example Value:

[collection-uuid]

Informational Note:

UUID of the Collection where all Researcher Profiles should be created by default.  This Collection MUST be configured to accept Person Entities (or the entity type specified in "researcher-profile.entity-type").

By default this is UNSPECIFIED. The default behavior is that the person's Researcher Profile will be created in the Collection in DSpace which is configured to accept Person Entities & where the user has permissions to submit.  If multiple Collections of this type are available, then the first one found will be used.

Example Value:

false

Informational note

Whether to enable "hard delete" when a Researcher Profile is deleted by an EPerson.  When "hard delete" is enabled (set to true), then anytime an EPerson deletes their Researcher Profile, the underlying Person Entity will be deleted (i.e. this acts as a permanent deletion).  When "hard delete" is disabled (set to false, the default value), then anytime an EPerson deletes their Researcher Profile, it will simply be "unlinked".  In other words, the underlying Person Entity will be kept in the system.

Example Value:

false

Informational note

Whether to make a new Researcher Profile "visible" (i.e. allow anonymous access) on creation.  When set to "false" (default value), a newly created Researcher Profile will only be accessible to the EPerson who created it. That EPerson may chose to make to visible (i.e. allow anonymous access) at a later time.  When set to "true", a newly created Researcher Profile will be immediately accessible to anonymous users.  But, the EPerson who created it may chose to hide it (i.e. disallow anonymous access) at a later time.