Project

General

Profile

Actions

Bug #12420

closed

Narrative text is messed up when in multiple xml nodes

Added by Aureliano Gentile over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
Sep 07, 2018
Due date:
% Done:

100%

Estimated time:

Description

The text for scientific advice and for status and trends are messed up or put in separate boxes.
See this example http://data.d4science.org/ctlg/GRSF_Admin/a45df585-b8c0-3d33-99a6-36c07a02e918 and the source file http://firms.fao.org/fishery/xml/resource/10484/158284/en


Files


Related issues

Blocks StocksAndFisheriesKB - Bug #12906: Update "problematic" records in the GRSF admin catalogClosedYannis MarketakisNov 20, 2018

Actions
Actions #1

Updated by Yannis Marketakis over 6 years ago

This issue happens because the sequence of the narrative texts was not preserved (it was not defined to do so).
FORTH will investigate if it is do-able without updating the mappings and re-constructing the GRSF KB.

In addition, the value for state and trend should be merged (since they have the same source, owner, ref year)

Actions #2

Updated by Yannis Marketakis over 6 years ago

  • Blocks Bug #12906: Update "problematic" records in the GRSF admin catalog added
Actions #3

Updated by Yannis Marketakis over 6 years ago

  • Status changed from New to Closed
  • Assignee changed from Nikos Minadakis to Yannis Marketakis
  • % Done changed from 0 to 100

The issue has been resolved. The narratives for the fields scientific_advice and state_and_trend are concatenated while respecting their order in the original sources. The concatenated narratives are separated using a semicolon (';'). @aureliano.gentile@fao.org if you would like to change this character with something else, please let us know.

As a proof of concept, we've updated a legacy record (http://data.d4science.org/ctlg/GRSF_Admin/3a37e42b-c19e-316f-a5dc-35a6cf1f98b0) and a GRSF one (http://data.d4science.org/ctlg/GRSF_Admin/a45df585-b8c0-3d33-99a6-36c07a02e918), however, we will update all the records as soon as we resolved all the issues (#12906).

Actions #4

Updated by Aureliano Gentile over 6 years ago

Thanks a lot!
Actually multiple text nodes are generated by the FIRMS Word-to-XML converter tool for handling different paragraphs, so a semicolon is not needed. A paragraph would make it since the proper punctuation is already there. Therefore, is it possible to have a paragraph delimiter between the two blocks? (Or line breaks if easier. Or simply a space if nothing else is doable). I see that also formatting is ingored (e.g. bold, italics..) but I understand this is for a further development later on.

Actions #5

Updated by Yannis Marketakis over 6 years ago

  • Status changed from Closed to Feedback
  • % Done changed from 100 to 90

I think that we cannot use HTML formatting tags (i.e. <br>, <i>, <b>, etc.) for the properties of the catalog. @francesco.mangiacrapa@isti.cnr.it is that correct?

If we cannot use HTML formatting tags, I will simply put a whitespace to differentiate narratives.

Actions #6

Updated by Francesco Mangiacrapa over 6 years ago

Yannis Marketakis wrote:

I think that we cannot use HTML formatting tags (i.e. <br>, <i>, <b>, etc.) for the properties of the catalog. @francesco.mangiacrapa@isti.cnr.it is that correct?

Yes, It's correct. You may use simply the " " (whitespace) to separate them or by adding the "; " (semicolon and whitespace).

Actions #7

Updated by Aureliano Gentile over 6 years ago

It is (wrongly) correct, I would say ;-)

Anyway, so the best would be to add simply a space.

With thanks

Actions #8

Updated by Yannis Marketakis over 6 years ago

Thanks for your reply @francesco.mangiacrapa@isti.cnr.it .
So, I will replace ';' with whitespace.

Actions #9

Updated by Yannis Marketakis over 6 years ago

  • Status changed from Feedback to Closed
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)