Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

WORK IN PROGRESS

The DSpace User 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 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:

  • 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. 

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 )

researcher-profile.entity-type = Person

You can eventually specify a different Entity Type for the item that can be used as profile. This is an advanced setting, change it only if you know what are you doing and have implemented specific customisation

You need to enable also the EPerson authority for the dspace.object.owner (uncomment the following lines in the config/modules/authority.cfg)

# 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

...to be provided...

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.