Dear community, We are testing configurable entities in our repository. Some of the OrgUnits will have many publications, ranging from 1k to 5k. When such OrgUnits are listed in a search result, or while browsing their owning collection, the page loads very slowly.
Inspecting the network tab in the browser I found that the JSON response from the discover API embeds all the entity metadata, with huge lists for the *relation.isPublicationOfOrgUnit* metadata field. The same behavior occurs in the DSpace demo. You can check the result of this search <https://demo.dspace.org/server/api/discover/search/objects?sort=dc.date.accessioned,DESC&page=0&size=10&configuration=collection&query=organization.legalName%3A%22Test%20OrgUnit%20-%20many%20publications%22&scope=d8ab207f-6eda-4c42-b2e5-ef76c2586070&embed=thumbnail&embed=item%2Fthumbnail&embed=accessStatus>, where the OrgUnit has a list with 100 entries of *relation.isPublicationOfOrgUnit* values*.* Is it possible to configure the discover to not embed this particular metadata field? Best regards, Alfeu U. Tavares -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/b4f5e87d-905c-4569-9169-f55b89fa6132n%40googlegroups.com.
