Rows from matrix data types lost in multi-taxa surveys if number of rows > number of species recorded

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Define a single site multi species survey.
2. Add a matrix data type (columns) to the survey.
3. Fill out the survey.  Add 2 rows to the matrix.  Record one species only.

What is the expected output? What do you see instead?
Expect the matrix rows to remain associated with the survey (in the same 
fashion as a normal survey).
Instead, each row from the matrix is associated with a single species/record 
with additional rows seemingly discarded.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by chris.go...@gmail.com on 12 Dec 2012 at 5:29

[GoogleCodeExporter]

Original comment by chris.go...@gmail.com on 12 Dec 2012 at 5:32

[GoogleCodeExporter]

Note that the way the matrix data is associated with the records created for 
each species also breaks the algorithm that groups related records together 
based on identical survey scoped attributes.  This results in not all created 
records being displayed when viewing a record created using a single site multi 
taxa survey.

Original comment by chris.go...@gmail.com on 13 Dec 2012 at 12:58

[GoogleCodeExporter]

Made a fix for survey scoped matrix attributes by:
1) renaming the parameter that identifies the record id used for each matrix 
row to avoid a clash with the species row.
2) Removing a prefix check during attribute save as the prefix is the species 
row prefix which doesn't make sense to compare to matrix row attributes. 

RECORD scoped matrix attributes still don't work for various other reasons.

Original comment by chris.go...@gmail.com on 17 Dec 2012 at 5:31

Attachments:

• Issue380.diff

[GoogleCodeExporter]

reviewed and accepted by a.low

Original comment by aaron.lo...@gmail.com on 18 Dec 2012 at 3:25