Skip to content

Project Entities do not display their relationships in tabs when showAuthorityRelations: true #5318

@tdonohue

Description

@tdonohue

Describe the bug

In #5134, a new relationship display was added for Entities which use the DSpace-CRIS style relationship model (i.e. relationships via authority framework). This relationship display is only enabled in the UI when showAuthorityRelations is set to true:

item:
  showAuthorityRelations: true

When this display is enabled, both Person and OrgUnit entities will have a tab display (on their Item pages) which shows all related Entities like this (notice the "Publication" and "Projects" tabs on this Person page):

Image

However, that same tab display does NOT appear if you visit the Item page for a Project Entity. This is a known issue because it requires enhancements to the Project entity submission form. See this comment:

#5134 (comment)

This incorrect display for Projects will be fixed in a later PR when the submission forms are enhanced during the DSpace-CRIS merger process.

To Reproduce

Steps to reproduce the behavior:

  1. Enable showAuthorityRelations as shown above on the frontend
  2. Disable default virtual metadata on the backend (relationship.enable-virtual-metadata = false) and enable basic authority framework settings for Persons & Projects:
relationship.enable-virtual-metadata = false

plugin.named.org.dspace.content.authority.ChoiceAuthority = \
 org.dspace.content.authority.OrcidAuthority = AuthorAuthority, \
 org.dspace.content.authority.ItemAuthority = ProjectAuthority,\
 org.dspace.content.authority.ItemAuthority = OrgUnitAuthority

choices.plugin.dc.relation.project = ProjectAuthority
choices.presentation.dc.relation.project = suggest
authority.controlled.dc.relation.project = true

choices.plugin.person.affiliation.name = OrgUnitAuthority
choices.presentation.person.affiliation.name = suggest
authority.controlled.person.affiliation.name = true

choices.plugin.dc.contributor.author = AuthorAuthority
choices.presentation.dc.contributor.author = suggest
authority.controlled.dc.contributor.author = true

cris.ItemAuthority.AuthorAuthority.source = orcid
cris.ItemAuthority.AuthorAuthority.entityType = Person
cris.ItemAuthority.ProjectAuthority.entityType = Project
cris.ItemAuthority.OrgUnitAuthority.entityType = OrgUnit

choices.plugin.project.investigator = AuthorAuthority
choices.presentation.project.investigator = suggest
authority.controlled.project.investigator = true

choices.plugin.dc.contributor.other = OrgUnitAuthority
choices.presentation.dc.contributor.other = suggest
authority.controlled.dc.contributor.other = true

choices.plugin.dc.description.sponsorship = OrgUnitAuthority
choices.presentation.dc.description.sponsorship = suggest
authority.controlled.dc.description.sponsorship = true

orcid.authority.prefix = will be generated::ORCID::
  1. Submit a new Publication. Link it to a Person (either from ORCID or local) in the submission form.
  2. Submit a new Project. Link it also to the same Person.
  3. Verify that the Person's Item page displays two tabs for Publication & Project. Clicking on either tab should display the linked Publication and the linked Project
  4. Verify the bug by visiting the Project page. It does not have a corresponding "Person" or "People" tab linking back to the associated Person entity.
  5. (Optionally) Submit an OrgUnit also linked to the Person. Verify the OrgUnit page has a tab which displays the linked Person.

Expected behavior

Project entities should display their relationships when showAuthorityRelations: true, just like Person and OrgUnit entities do.

Related work

First discovered in #5134 where this feature was added

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    Status

    📋 To Do

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions