Page History: QA Report
Compare Page Revisions
Page Revision: 2011/02/14 15:45
About
QA_Report was written to compare WSL's newspaper input data (i.e. data created for NDNP during reel evaluation) to the NDNP output after data conversion (i.e. the batch, mets issue and mets reel files). You may be able to adapt the script for use but be aware that these instructions are written for use with data from an MS Access 2007 database and a Windows operating system.
Download
QA_Report.tar v1Feel free to download but please help us improve it by
emailing me if you find bugs.
Install
Extract QA-Report and save it on your computer or external hard drive. This script works best if you save the folder on the same drive as the batch your are testing (e.g. C:\batch_wa_2009_sample and C:\QA-Report)
save to same folder as the batch |
FYI: the pictured batch is one reel with three titles |
How to Run
- To run QA-Report you must first save your input data as xml to the QA-Report folder
- Our input data is delivered in MS Access in three tables (titleTbl, reelTbl, issueTbl)
- From Access save each table as xml into the QA-Report folder (e.g. Export > More > XML File > C:\QA_Report\reelTbl.xml)
- Click OK
- Export XML window will open, save 'Data (XML)' only (uncheck 'Schema of the data (XSD)' - this isn't needed)
- Click OK
- Save Export Steps if you like, click Close
- You may close the database
- QA-Report should now have three xml files (titleTbl.xml, reelTbl.xml, issueTbl.xml)
NOTE: You may get errors if your data isn't structured in the same way as the sample data. If you know xsl, you're welcome to tweak the code to meet your needs. For example, if your field names are not the same as the sample data provided, simply change the variable names in the titleTbl.xsl, reelTbl.xsl, and issueTbl.xsl files in QA-Report save data to xml files |
- Now run the QA-Report using the BATCH.xml file
- Open your computer's MS-DOS command
- Start > Run > type 'cmd' > click 'OK'
- Navigate to QA-Report (cd C:\QA-Report)
- At the prompt run the run_report.bat file with the proper path to the BATCH.xml file as a parameter - use single quotes as shown here (e.g. run_report '..\batch_wa_2009_sample\BATCH.xml')
run the script from the command line |
- The script may take a few minutes depending on the size of your dataset. When the comparison is done a browser window will open to 'Test:titleTbl'
when the script finishes the first test table will open in a browser |
Understanding the Results¶
Links in all the tables will open up the corresponding mets (issue or reel) or the BATCH.xml file in the browser so you can investigate any found differences in the output data.
Test: titleTbl
This table is a re-creation of titleTbl in the database.
- Titles in red are missing from the BATCH.xml file
- The links at the bottom of the page will take you to the next test results
Test: reelTbl
This table is a re-creation of reelTbl in the database.
- Reels in red are those whose reelNumber is missing from the BATCH.xml file
- The data in this table is compared to the mets reel files throughout the batch (crawled via the BATCH.xml file using ndnp:reel)
- Cells in yellow are where there is a mismatch in the output
Test: issueTbl
This table is a re-creation of issueTbl in the database.
- Issues in red are those whose lccn is missing from the BATCH.xml file
- The data in this table is compared to the mets issues files throughout the batch (crawled via the BATCH.xml file using ndnp:issue)
- Cells in yellow are where there is a mismatch in the output
Known issues
- Need to fix test for ndnp:startDate and ndnp:endDate on reel mets test (error created when reel is split between two titles).
- Fix test for density readings
- Need to build a way to test when duplicate pages MODS:detail@type="page number"/MODS:number should not equal MODS:detail@type="pages"/MODS:start (since WSL delivers duplicates).