1. Changing Meta Data and WSDL OPEN Development Conference September 17-19, 2008 Ravi Rajaram IT Development Manager Max Lin Senior Systems Analyst

2. 9/19/08 Changing Metadata 2 Metadata Update Metadata xml is the key for processing the clinicaldata coming from OPEN portal for every registration. Metadata xml filename format - >v. _ _ _step _meta.xml Metadata xml changes when –A question is added or deleted in the Eligibility Checklist form –A valid value (codelist item) is added or deleted Metadata xml does not change when –Question layout in the OPEN portal is changed –Adding or deleting an edit check –Adding or removing a skip pattern Procedure for requesting a EC form change in OPEN is covered in the general session on Thursday 9/18/2008

3. 9/19/08 Changing Metadata 3 Metadata Update When the metadata is changed –The form is updated with a new version date within OPEN. The version date here is specific to OPEN and nothing to do with RSS protocol version dates. It is possible it is equal to the protocol version date. –The form’s meta data is generated and saved to OPEN DB –Group is informed about the new metadata availability through email (manual at present, automatic in future) –Group/RandoNode requests the meta data through Opendataservice using the protocol number.

4. 9/19/08 Changing Metadata 4 What needs to happen at Groups when metadata changes Download the metadata xml through opendataservice using the protocolnumber –Make sure that the new metadata.xml is stored in the appropriate metadata file directory. ([CTSU_HOME]/RandoNode/meta) RandoNode starter kit software is not affected. May need to update your business logic to deal with the added/deleted question or codelist item. Will test few registrations using the new metadata file. Use Open portal to submit new registrations. If tests are OK, ask CTSU to move the new version of the form to production.

5. 9/19/08 Changing Metadata 5 Business rules for existing incomplete registration during the metadata change Any incomplete (un-submitted) registrations can be completed by the site even after the new version of the form is moved to production. If Groups do not want any of the incomplete registration point to the old version of the form, CTSU can void those forms. If not voided, sites can submit the registrations corresponding to the old version and group can process the data based on the metadata file name contained within the ODM object. ODM API takes care of this association automatically. –One more reason to use the ODM API

6. 9/19/08 Changing Metadata 6 Task 4a – Metadata change Hands-on Lab

7. 9/19/08 Changing Metadata 7 Task 4a Steps Revert back to ServiceImp.cs as working source file. Run OPENPortalProxy to invoke doRegister with 27499.xml, which has the new question in it and referring to a new metadata file which does not exist. When finish, inspect the log to see the error message. Copy the new metadata file v.NSABP-B- 42_2494107_080912_step1_meta.xml to the metadata file location. Re-run OPENPortalProxy to verify the 27499 is working.

8. 9/19/08 Changing Metadata 8 Metadata Update End of Task 4a

9. 9/19/08 Changing Metadata 9 WSDL Update The RandoNode at the group is built based on the WSDL defined by CTSU Currently there are 6 interface objects and 5 interface methods WSDL changes only when any of the interface objects or the methods change The possible changes are –Addition/deletion of an attribute in an interface object –Addition or deletion of interface method –Change the input /response objects for the interface methods

10. 9/19/08 Changing Metadata 10 What needs to happen at Groups when WSDL changes Install the new DLLs (e.g. OPEN_Message.dll) to RandoNode bin directory. To identity the DLL version, right click on the DLL and select Properties. The Version tab will contain the version information.