geonetwork / geonetwork/core-geonetwork

inconsistent rich content display

Open
#4,885 4 comments 0 reactions 0 assignees View on GitHub
stale
Dominant language
Java
Stars
521
Forks
515
Avg merge
6d 13h
Merged PRs (30d)
19

Description

A customer reported that his table (below) was added to metadata-abstract, but various views in geonetwork render the content differently

```html

ab
ab

```

Search result tile
![image](https://user-images.githubusercontent.com/299829/88632202-8b1edb00-d0b3-11ea-8552-9007234ff952.png)

Search result list
![image](https://user-images.githubusercontent.com/299829/88632304-b1dd1180-d0b3-11ea-8bf7-3c296ab306d0.png)

Metadata index view
![image](https://user-images.githubusercontent.com/299829/88632137-793d3800-d0b3-11ea-832e-fa7743e3af8b.png)

Metadata html formatter
![image](https://user-images.githubusercontent.com/299829/88632395-cfaa7680-d0b3-11ea-87a9-ceddd124b6db.png)

Suggestion is to make display consistent. Somehow i like rendering of the html elements, maybe we can make it a configuration in config.js for people to decide how they want to render the abstract (and other long string fields?)

Contributor guide

Open the contributing guide

Research direction

Compare rich-content rendering in the search result tile, search result list, metadata index view, and metadata html formatter using the supplied table example. Then inspect config.js to determine whether a consistent rendering choice or configuration is appropriate; done means the abstract displays consistently across the affected views.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, javascript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.