Rendering strategies

Current out-of-the-box rendering strategies are:

Additional rendering types are available via the 4Science Addon UXPlus , including rendering over maps (google and openstreet map supported), automatic linking of value to search or browse results, and embedding of HTML, Markdown, or YouTube video.

Description

Heading

type of rendering commonly used for headings. It shows the metadata value in a container with css class h1.

Text

used to show short text information. If there is a label in the database record that defines the field, it will be shown, in bold, before the metadata value.

Longtext

longtext rendering is used to display very long texts. It provides a "show more" mechanism that allows you to view, as a preview, the first 3 lines of the text and by clicking on it you can show / hide the additional lines present.

Link

generates a link that has as displayed text and href the value of the metadata associated with the field

link.label

generates a link that has the metadata value as href and as text a i18n value if the label contains an i18n key, the label text otherwise

Date

formats the metadata value as a date in the current locale, ex. 2020-08-25 -> 25 August 2020

Identifier

This rendering type build a dynamic link from the identifier present in the metadata. If the metadata value is an http, https, ftp or ftps url the component shows an html anchor with the metadata value in href and text, otherwise if the value is an external identifier (ex. doi:xxxxxxx) the component shows an anchor with href valorized with url of external source and the identifier value for text.
It's possible to force a certain type of identifier using the related subtype, ex. if the metadata value contains a doi identifier in the shape xxxxxxxx (without the URN "doi:") to force doi rendering, use the subtype identifier.doi for the rendering field.

The mapping between the urn and the base url used by the resolver is defined in the environment.common.ts file, see the excerpt below.

By default, whitespaces are removed from metadata values before being used in an external identifier link. This behavior can be changed by setting shouldKeepWhiteSpaces as true.

crisLayout: {
    urn: [
      {
        name: 'doi',
        baseUrl: 'https://doi.org/',
        shouldKeepWhiteSpaces: false,
      },

CrisRef

This rendering build a dynamic link to the authority associated at metadata, it shows an icon based on the referenced entity type. To configure an icon for specific entity type you can add an entry at path layout.crisRef of client configuration file. The new entry must has two properties, entityType and icon. These properties must set with the entity type name (ex. Person) and font awesome icon (ex. fa fa-user), respectively. If for a specific entity type isn't configured an icon the default will be showed.

Thumbnail

This rendering is used to show a thumbnail of the item, if there is one or more fields of this type, the content will be shown on the left side of the row in which it is contained
as shown in the following image:

When inside the bundle there isn’t any ‘THUMBNAIL’ or ‘PREVIEW’ bitstreasm and the original file is an image, DSpace-CRIS tries to use the original image but only if its size is under the value defined in the configuration option cris.layout.thumbnail.maxsize. Its default value is 250kb. We suggest attention about raising this value. For example all results of a search have a thumbnail, with a thumbnail of 1Mb you need 10 Mb to download.
This configuration operates with the same logic in every place where a thumbnail is present.

Attachment

This rendering creates a link to the files attached to the item.
In case the attachment (bitstream) has a description (dc.description), the description will be shown below the link. It provides a "show more" mechanism that allows you to view, as a preview, the first line of the description and by clicking on it you can show / hide the additional lines present.

Tag

This rendering creates a button for each metadata value

Valuepair

This rendering should be used for metadata associated to a value-pair in order to render the display value instead of the stored value. The rendering must be provided using the valuepair name as subtype for instance, valuepair.common_language

Table

Used to display nested metadata as a table view using table html element with no borders. 

It creates a responsive table with rows and cells, where the content and styling of the cells are determined by the "metadataGroup" and "componentsToBeRenderedMap" data structures. 

Inline

Is used to display nested metadata. If it is configured as inline values (all values on the same line).

AdvancedAttachment

renders a list of attachments. It also provides a "View More" button if "canViewMore" condition is met. On clicking it more attachments/bitstreams are retrieved and displayed. 

Html

By applying the html rendering to text areas, for example Abstract, the text written with HTML code will be displayed entirely and properly rendered.

Longhtml

By applying the longhtml rendering to text areas, for example Abstract, the text written with HTML code will be truncaterd with the show more button and properly rendered.

Orcid [no more available]

Used to display the orcid logo & link for the orcid ID metatadata. Available only until ver. 2022.02.00 (05th Oct 2022).