Changeset 25063 in main


Ignore:
Timestamp:
04/14/22 18:55:21 (11 months ago)
Author:
GarthBraithwaite_STG
Message:

nm epht, 300 - Cleared NM Page.communityNames selections from 300, set the epht value as string instead of wrapped in NAME.

Files:
2 edited

Legend:

Unmodified
Added
Removed
  • adopters/nm-epht/trunk/src/main/webapps/nmepht-view/xslt/html/community/SiteSpecific.xslt

    r25011 r25063  
    3737        <xsl:param name="Page.communityReportType" select="'indicators'"/>
    3838
    39         <xsl:param name="Page.communityDimensionNames">
    40                 <NAME>GeoCnty</NAME>
    41         </xsl:param>
     39        <xsl:param name="Page.communityDimensionNames" select="'GeoCnty'"/>
    4240
    4341</xsl:stylesheet>
  • branches/3.0.0/ibisph-view/src/main/webapp/xslt/html/community/Page.xslt

    r23488 r25063  
    7272        />
    7373
    74         <!-- GARTH TODO: discuss with Lois/CoP
    75                 Implemented as a simple list so that adopters can override
     74
     75        <!--
     76                Parameter to control which communities show up in the selection list.
     77                This is needed for NM because IBIS and EPHT share the same dimensions
     78                of which EPHT only wants to use a few. 
     79                To implement an override / specify which dim names set the parameter
     80                with a simple CSV list as shown below:
     81
     82                xsl:param name="Page.communityNames" select="'GeoCnty', 'GeoRegion',
     83                'GeoSarea', 'GeoSchDist', 'RacEthDOH', 'Sex', 'SexualOrientation',
     84                'Income5Grps'"
     85
    7686                -or-
    77                 adopters can simply deselect the COMMUNITY_FLAG in the db for those
    78                 dimensions they don't want to be considered a community.
    79                 xsl:param name="Page.communityNames" select="$Page.dimensions/DIMENSION[COMMUNITY_FLAG = 'x']/NAME"
     87                The preferred way is for adopters to only set the COMMUNITY_FLAG (admin
     88                app) for those dimensions they want to be treated as a community.
    8089        -->
    81         <xsl:param name="Page.communityNames" select="'GeoCnty', 'GeoRegion',
    82                 'GeoSarea', 'GeoSchDist', 'RacEthDOH', 'Sex', 'SexualOrientation',
    83                 'Income5Grps'
    84         "/>
     90        <xsl:param name="Page.communityNames" select="$Page.dimensions/DIMENSION[COMMUNITY_FLAG = 'x']/NAME"/>
    8591
    8692        <xsl:param name="DimensionName"/>
Note: See TracChangeset for help on using the changeset viewer.