Difference between revisions of "iRefIndex Testing 7.0"
From irefindex
(Created page with 'The testing procedure for iRefIndex Follow this link for a listing of all iRefIndex related pages (archived and current). Category:iRefIndex') |
|||
| Line 1: | Line 1: | ||
The testing procedure for iRefIndex | The testing procedure for iRefIndex | ||
| + | ==Cross check with output of element counter== | ||
| + | === Program to use : biotek.uio.no.XML.Element_Counter (SaxValidator package)=== | ||
| + | * For each interaction source </interactor> count should match the UID count | ||
| + | int_object (select (select name from int_db where int_db.id=source) as | ||
| + | intSource, count(uid) from int_object group by source; ). | ||
| + | * For each interaction source </interactor> count should match the UID count | ||
| + | int_source (select (select name from int_db where int_db.id=source) as | ||
| + | intSource, count(uid) from int_source group by source;). | ||
| + | * When </interactor> is not usable to count distinct objects (when this occurs | ||
| + | as part of interaction and repeated in interactorList) some other suitable | ||
| + | element has to be used (e.g </participant>) | ||
| + | * Why count the closing elements in the above cases (e.g. </interactor> , | ||
| + | instead of <interaction> or </interaction ). The reason is interaction elements | ||
| + | may have attributes and elements starting with interaction may be ambiguous. | ||
| + | This program uses text matching (to be independent of any XML parsing). | ||
Follow this link for a listing of all iRefIndex related pages (archived and current). | Follow this link for a listing of all iRefIndex related pages (archived and current). | ||
[[Category:iRefIndex]] | [[Category:iRefIndex]] | ||
Revision as of 09:19, 28 November 2010
The testing procedure for iRefIndex
Cross check with output of element counter
Program to use : biotek.uio.no.XML.Element_Counter (SaxValidator package)
- For each interaction source </interactor> count should match the UID count
int_object (select (select name from int_db where int_db.id=source) as intSource, count(uid) from int_object group by source; ).
- For each interaction source </interactor> count should match the UID count
int_source (select (select name from int_db where int_db.id=source) as intSource, count(uid) from int_source group by source;).
- When </interactor> is not usable to count distinct objects (when this occurs
as part of interaction and repeated in interactorList) some other suitable element has to be used (e.g </participant>)
- Why count the closing elements in the above cases (e.g. </interactor> ,
instead of <interaction> or </interaction ). The reason is interaction elements may have attributes and elements starting with interaction may be ambiguous. This program uses text matching (to be independent of any XML parsing).
Follow this link for a listing of all iRefIndex related pages (archived and current).
