Versions Compared

Old Version 2

changes.mady.by.user Andrea Bollini (4Science)

Saved on

compared with

New Version 3

changes.mady.by.user Andrea Bollini (4Science)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


...

Info
The DSpace

...

Researcher Profile feature has been introduced in DSpace 7.3 to support the ORCID Integration work but can be used alone. It is turned off by default and must be enabled manually


A DSpace User Researcher Profile is a special Person item that is linked with exactly one EPerson (DSpace account). This EPerson will own the profile (Person Item) gaining WRITE permission on it. The link between the Person Item and the EPerson is keep in a special metadata, dspace.object.owner  configured to hold authority values. Indeed, the authority of such metadata will contains the uuid  of the EPerson that own the profile.

...

A few quick notes:

Here a summary of the key concepts & requirements of the feature

  • Profiles require Configurable Entities to be enabled, as every User Profile is represented by a Person Entity
  • Profiles can be linked to only one EPerson (user account). That EPerson has full rights to manage the profile, including whether the profile is publicly visible or private.
  • Optionally, Profiles can be synchronized (or initially created) via ORCID Integration.

When the feature is enabled the user can create a researcher profile from his Profile (account page)

Image Added

if a Person Item already exists in the system matching the account email address this Person Item is offered to the user

Image Added

once that a profile has been created or claimed, the user can make it public (Anonymous READ) or private

Image Added

By default, deletion of the researcher profile doesn't imply deletion of the corresponding Person Item, this can be changed as specified in the Advanced configuration paragraph. 

Enable the feature

To enable the feature you need to set the following property (uncommenting it in the config/modules/researcher-profile.cfg  or adding it to the config/local.cfg )

...

Code Block
# Configuration settings required for Researcher Profiles
# These settings ensure "dspace.object.owner" field are indexed by Authority Control
choices.plugin.dspace.object.owner = EPersonAuthority
choices.presentation.dspace.object.owner = suggest
authority.controlled.dspace.object.owner = true

Advanced configuration

You can configure some aspects of the Profile feature in the config/modules/researcher-profile.cfg 

Specifically, it is possible to force all the profile created via this feature to belong to a specific collection (default to the first Person collection where the user has permission) and set it as publicly visible (default, Anonymous READ) or not. Moreover, it is possible to decide if deleting the profile will imply also deletion of the Person Item or (default) only the unlink of the Person Item with the EPerson.

Trouble-shooting

I cannot found this feature

The feature needs to be enabled explicitly, please follow the instruction in the Enable the feature paragraph

The users get an error when he try to create their profile

The feature requires Person entity configured in the data model (see Configurable Entities) and the user must have permission to submit in at least one collection configured to accept Person entities. Please double check that the EPersonAuthority is bind to the dspace.object.owner  metadata, see the Enable the feature paragraphto be provided...