It is possible to add some additional, entity-type-based metadata to the default short view of DSpace-CRIS objects.
The default view of entities, in this example, a publication, is rendered in this way:
with angular configuration file (config.yml) it is possible to add metadata. Property to be configured is searchResult.additionalMetadataFields which is a map having the lowercase entity type (“publication”, “person”,…) plus “fallback” as default as key and a list of attributes as value.
Attributes are:
name(Mandatory): name of the additional metadata to be rendered. NB: they are rendered only if set with a value.rendering(Mandatory): rendering to be applied, rendering type acts as defined in Layout and data security configuration tool page, available rendering types are:textcrisreflinklink.emailidentifier.<identifiertype>valuepair.<valuepairtype>date
label: label to be put close to metadata value, it can be an hard coded text or a key translated in i18n filesprefix: Text to be prefixed to rendered valuesuffix: Text to be added after rendered valuelimitTo: in case of repeatable metadata rendered, the number of occurrences to be displayedstartFromLast(boolean, default false): when set, in case of repeatable metadata rendered, the list of displayed occurrences start from last one.
Following is a configuration example defining additional metadata to be displayed for publications, and a default “fallback” set of additional metadata to be displayed in all other DSpace-CRIS objects short views
searchResult:
additionalMetadataFields:
- entityType: publication
metadataConfiguration:
- name: dc.relation.journal
rendering: text
label: Journal
- name: dc.relation.issn
rendering: text
label: ISSN
- name: dc.identifier.doi
rendering: identifier.doi
label: DOI
- entityType: fallback # used for other entity types
metadataConfiguration:
- name: dc.identifier.doi
rendering: text
With above configuration, system would render publication metadata in following way:

