I've created a Jira to keep track of the development of this bug. http://issues.collectionspace.org/browse/CSPACE-5579 - Jesse On Thu, Sep 27, 2012 at 10:31 AM, Jesse Martinez <jmartinez@movingimage.us> wrote: > Hi all, > > I've come across something unusual when adding elements to a > procedure's list results field block in a tenant binding file. I've > added two additional core elements to the list: > birthDateGroup/dateDisplayDate and deathDateGroup/dateDisplayDate, > which are separate non-repeating structured date groups. The xml block > looks like this > > <service:ListResultField merge:matcher="skip" merge:action="insert" > > <service:element>dateDisplayDate</service:element> > <service:schema>persons_common</service:schema> > <service:xpath>birthDateGroup/dateDisplayDate</service:xpath> > </service:ListResultField> > <service:ListResultField merge:matcher="skip" merge:action="insert" > > <service:element>dateDisplayDate</service:element> > <service:schema>persons_common</service:schema> > <service:xpath>deathDateGroup/dateDisplayDate</service:xpath> > </service:ListResultField> > > But the list results give me the same value for either field > "dateDisplayDate", which isn't correct. > > From a search query: > ... > <foreName>Carol</foreName> > <surName>Dempster</surName> > <dateDisplayDate>1991</dateDisplayDate> > <dateDisplayDate>1991</dateDisplayDate> > <termDisplayName>Carol Dempster</termDisplayName> > ... > > I'm thinking there is a mishap since the field names are identical > even through their xpath and group home are distinct. > Is anyone else doing something similar or have come across this one before? > > - Jesse