|
1 | 1 | # nci-diff-CDISC
|
2 | 2 | diff specific for CDISC reports
|
| 3 | + |
| 4 | +CDISC Changes Report Generator |
| 5 | +============================== |
| 6 | + |
| 7 | +This program will generate a changes report between two CDISC releases. |
| 8 | +The releases may span any amount of time. |
| 9 | + |
| 10 | +Requirements |
| 11 | +------------ |
| 12 | +Git |
| 13 | +Apache Ant |
| 14 | +Java Developers Kit |
| 15 | + |
| 16 | +Building the program |
| 17 | +-------------------- |
| 18 | + |
| 19 | +Clone the DiffCDISC repository onto your local filesystem using Git. |
| 20 | + |
| 21 | +C:\> git clone https://github.com/NCIEVS/diff-cdisc.git |
| 22 | + |
| 23 | +Open a Command Prompt and navigate to the repository directory. |
| 24 | + |
| 25 | +Run an ant build |
| 26 | + |
| 27 | +C:\DiffCDISC> ant build |
| 28 | + |
| 29 | +This will create a 'classes' and add a jar file to the 'dist' directory |
| 30 | +where program dependancies are stored. The program is now ready to run. |
| 31 | + |
| 32 | +NOTE: If the build fails, you may need to inspect your ant configurations. |
| 33 | +See: https://ant.apache.org/manual/ |
| 34 | + |
| 35 | +Preparing data for the program |
| 36 | +------------------------------ |
| 37 | + |
| 38 | +Users should pull two reports in .txt format from the same EVS CDISC |
| 39 | +Archive directory (e.g., ADaM, SDTM, SEND). |
| 40 | + |
| 41 | +Included in this repository are two example reports from the SDTM Archive |
| 42 | +directory. The example below will demonstrate how to run the program |
| 43 | +using these two files. |
| 44 | + |
| 45 | +Running the program |
| 46 | +------------------- |
| 47 | + |
| 48 | +Each report is input into the program (newest followed by oldest), |
| 49 | +followed by a "release date" and then the filename of the output. |
| 50 | + |
| 51 | +C:\DiffCDISC\dist>RunChanges "..\docs\SDTM Terminology 2015-09-25.txt" "..\docs\SDTM Terminology 2015-06-26.txt" "9/25/2015" Changes.txt |
| 52 | +Initializing diff report... |
| 53 | +Getting changes... |
| 54 | +Printing changes report... |
| 55 | + |
| 56 | +About the program |
| 57 | +----------------- |
| 58 | + |
| 59 | +The following changes between CDISC releases are detected. In the event |
| 60 | +of an Update, original and new values are reported. |
| 61 | + |
| 62 | +- Add new CDISC Synonym |
| 63 | +- Add new term to existing codelist |
| 64 | +- Add new term to new codelist |
| 65 | +- Addition of new codelist |
| 66 | +- Remove CDISC Synonym |
| 67 | +- Remove term entirely from codelist |
| 68 | +- Remove term from retired codelist |
| 69 | +- Retire codelist |
| 70 | +- Update CDISC Codelist Name |
| 71 | +- Update CDISC Definition |
| 72 | +- Update CDISC Extensible List |
| 73 | +- Update CDISC Submission Value |
| 74 | +- Update NCI Preferred Term |
| 75 | + |
| 76 | +Known issues |
| 77 | +------------ |
| 78 | + |
| 79 | +The 'Request Code' column will always be empty as they are stored in the |
| 80 | +JIRA tracking system. This column is manually populated by EVS before |
| 81 | +each quarterly release. |
0 commit comments