Ticket #906 (closed defect: wontfix)

Opened 13 years ago

Last modified 12 years ago

[M] MOLES-to-DIF problem with embedded html?

Reported by: selatham Owned by: selatham
Priority: blocker Milestone: Replace Metadata Gateway
Component: discovery Version:
Keywords: DiscoveryService Cc:


Search on ipcc in Discovery - there is no summary info. I have looked at the record as harvested and there's a summary tag with no content. Go to browse and there is summary info (i.e. descriptionSection in Moles). Note it has html tags in which are visible. They have been escaped into the moles XML. Here's the actual content from the file in badc's exist>

The DDC has been established to facilitate the timely distribution of a consistent set of up-to-date scenarios of changes in climate and related environmental and socio-economic factors for use in climate impacts assessments. The intention is that these new assessments can feed into the review process of the IPCC.
The initiative to establish a DDC grew out of a recommendation by the IPCC Task Group on Data and Scenario Support for Impact and Climate Analysis (TGICA). This Task Group was itself formed following a recommendation made at the IPCC Workshop on Regional Climate Change Projections for Impact Assessment (London, 24-26 September 1996).

So my theory is that MOLES2DIF is doing something strange when there are escaped html tags.

Change History

comment:1 Changed 13 years ago by selatham

  • Status changed from new to closed
  • Resolution set to wontfix

Actually ipcc (and coapec) records are not getting through the CEDA metadata pipeline. I think they are failing to be added to the CEDA Moles db due to funny characters. Errors in log for script moles_xml_bulk.py:-

storing document dataent_COAPEC.xml (22 of 148) ...could not parse file /usr/local/exist-client/./dataentout/dataent_COAPEC.xml: networking error

storing document dataent_isccp_d1.xml (40 of 148) ...could not parse file /usr/local/exist-client/./dataentout/dataent_isccp_d1.xml: networking error

So this is a CEDA content problem.

comment:2 Changed 12 years ago by lawrence

  • Keywords DiscoveryService added
  • Component changed from DiscoveryService to discovery

Moved from DiscoveryService? component to discovery as part of NDG2 cleanup

Note: See TracTickets for help on using tickets.