Closed DanSmith closed 3 weeks ago
Should be completed by next release. XML assumed order. We need to mark these as ordered collections in CSV. "Sequence as ordered" is an example. We should find and mark these. Locate prior to making changes so we can move quickly on these.
I have provided a first pass of locations where order requirements should be evaluated. IssueDetails_No23.xlsx
Notes from TC meeting 2024-03-21 Not critical in short term (BETA version 2). Good to get multiple eyes on this.
Look at best way to include ordering (group types and schemes and supporting to hierarchical lists) (Dan) Groups/Schemes Instrument (ordered steps) Study/Group organization One class Obviously needing order Two those that might require ordering Known unknowns
Add those in and then test to see what was missed Need to devise a testing protocol that is needed to
IssueDetails_No23-annotated.xlsx I've noted those changes that were made in PR-48 Note that full Item and Complex type contents are listed and not all content required ordered designation. Not all were dealt with (that wasn't the expectation at this point) and some were added (see end of list). I have also added comments on a number of changes.
Addressed in #48
In the prior XML schema of DDI Lifecycle, all properties were implicitly ordered within the XML.
In the new model, we must explicitly set the property to be
Ordered
if required. This was only done for Sequence so far, there are other properties that should have theirOrdered
set totrue
.