Versions Compared

Key

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

...

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

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

...

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.

...

Troubleshooting

I cannot

...

fid this feature

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

The users

...

sees an error when

...

they 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 paragraph section above.