Opened 4 years ago

Last modified 4 years ago

#310 new Issue

CP HL Single Page and Full Report IP XML structs SYNC Issue

Reported by: Garth Braithwaite Owned by:
Priority: Unknown Milestone: Unassigned
Component: View-App Version: Unknown
Severity: Unknown Keywords:
Cc:

Description

The 2.3 CP HL page report uses the community XML file for IP names. The CP HL full report uses the indicator set XML file for IP names.

Options: 1) keep both XML files in sync. 2) add a duplicate definition to the IP sets XML. 3) add nm\xslt\html\community\highlight\report\ss.xslt param to define the correct, default IP set to use:

<xsl:param name="IndicatorProfileSetName" select="'CHSI'"/> or whatever IP set name you'd like to use...

4) Modify the controller model map config to pull the IP set name from the URL and inject as part of the model. Example:

http://localhost/nm/community/highlight/report/CHSI/GeoCnty/1.html

For now in NM the report/Page.xslt was modified to loop INDICATOR_NAME which exists in both structures. The SS.xslt can be coded for the ip set name to use or can use the community XML IP names via overriding the Page.indicatorProfileSetIndicatorNames param. See 12/10/2015 NM commit for examples.

If this is not done then the default set name is: "CommunityInd?" and MUST exist in the set XML. This set MUST match the community IP NAME set or the reports will be out of sync.

Change History (1)

comment:1 Changed 4 years ago by Garth Braithwaite

Summary: CP HL Page and Report IP XML structsCP HL Single Page and Full Report IP XML structs SYNC Issue
Note: See TracTickets for help on using tickets.