Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| AttributeValue files | 19 | Confirmed that Peter's fix to update the moduleID's to the DK module (from invalid core ID's) has been re-implemented correctly.
|
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| AttributeValue files | 19 | Confirmed that Peter's fix to update the moduleID's to the DK module (from invalid core ID's) has partially worked - problem now is that is has removed all 19 records in question, instead of replacing the moduleID's with the DK moduleID!! Peter found this was because the effectiveTime didn't get reset after he applied the fix again, so he's going to update the effectiveTime now and re-try... |
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| AttributeValue files | 19 | Confirmed that Peter's fix to update the moduleID's to the DK module (from invalid core ID's) has ben REVOKED BY THE VERSIONING!!!:
|
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| ModuleDependency files | 2 | 2 records updated for 20170930 as expected, in order to fix the dependency date |
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| ModuleDependency files | 2 | 2 records updated for 20170930 as expected, however the dependency date is still incorrect at Jan 2017! |
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| ModuelDependency files | 2 | 2 new records added for 20170930 as expected - but the dependency date is wrong, so needs fixing | |
| AssociationReference files | 6 | 6 records added for newly inactivated concepts, as expected in MSSP-92: > 59b614c0-d02b-4f43-95f1-5f38097a91bc 20170930 1 554471000005108 900000000000527005 555111000005107 725734005 | |
| AttributeValue files | 74 | 74 records added:
Also verified that Peter's fix to update the moduleID's to the DK module (from invalid core ID's) has worked:
| |
| Language-EN (full, delta and snapshot) | 3 | Following 3 language records added: > 4525f4ff-0185-46c9-b1b7-01953fc56c15 20170930 1 554471000005108 900000000000509007 4919641000005114 900000000000548007 These are related to the 2 new EN description records added in, and so are expected changes. | |
| Language-DA (full, delta and snapshot) | 148 | 50 records inactivated, as expected per the Description changes below + 1 updated - 4889551000005117, as expected from Camilla's change in DKSEPB-3 + 1 reactivated - 2723441000005118, as expected from Camilla's change in DKSEPB-3 + 96 records added, as expected per the Description changes below | |
| Concept files | 7 | DKSEPB-3 | 1 record added: > 557091000005108 20170930 1 554471000005108 900000000000074008 Traced back in Kibana to following tasks that Camilla made changes in over the authoring cycle:
+ 6 records inactivated, as expected in MSSP-92: > 555111000005107 20170930 0 554471000005108 900000000000074008 |
| Description-EN (full, delta and snapshot) | 2 | DKSEPB-3 | Following 2 description records added: > 4919631000005118 20170930 1 554471000005108 557091000005108 en 900000000000003001 Avlund mobility-tiredness scale (observable entity) 900000000000448009 Traced back in Kibana to following tasks that Camilla made changes in over the authoring cycle:
|
| Description-DA (full, delta and snapshot) | 146 | DKSEPB-3 | 96 description records added + 50 records inactivated Traced back in Kibana (via spot checks only due to volume of changes - Terance working on a detailed change report for next release, so that we can accurately compare all components changed in each release cycle) to following tasks that Camilla made changes in over the authoring cycle:
Plus some fixes that Terance asked Sonja to perform in Sept 2017 after upgrade to JUL INT, as Camilla was too busy and we wanted to start the release.
|
| Relationship files | 65 | 47 records added + 18 records inactivated - as always not possible to validate inferred relationships... | |
| Stated Relationship files | 7 | 1 record added: > 20170930 1 554471000005108 557091000005108 364644000 0 116680003 900000000000010007 900000000000451002 + 6 records inactivated: > 20170930 0 554471000005108 555111000005107 385559004 0 116680003 900000000000010007 900000000000451002 Matches the Concept changes, so all expected changes | |
| Readme file | n/a | Expected changes for latest release dates |
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| Language-EN (full, delta and snapshot) | 3 | Following 3 language records added: > 4525f4ff-0185-46c9-b1b7-01953fc56c15 20170930 1 554471000005108 900000000000509007 4919641000005114 900000000000548007 These are related to the 2 new description records added in, and so are expected changes. | |
| Description-EN (full, delta and snapshot) | 2 | Following 2 description records added: > 4919631000005118 20170930 1 554471000005108 557091000005108 en 900000000000003001 Avlund mobility-tiredness scale (observable entity) 900000000000448009 | |
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| Language-DA (full, delta and snapshot) | 841 | 693 records removed, plus 147 records added ????????????????????????????????????????? There are less changes to the Language records than to the Description records, due to the back end fixes that were required as part of the editing cycle. The description-DA file contains 4 unchanged apart from the effective time due to these fixes. The language refsets for the two extra inactive descriptions are already inactive, and thus not appearing in the current language refset delta: id effectivetime active moduleid refsetid referencedcomponentid acceptabilityid | |
| Language-EN (full, delta and snapshot) | 3 | Following 3 language records added: > 4525f4ff-0185-46c9-b1b7-01953fc56c15 20170930 1 554471000005108 900000000000509007 4919641000005114 900000000000548007 These are related to the 2 new description records added in, and so are expected changes. | |
| ModuleDependency files | 6 | 6 new additional records, MORE THAN WAS EXPECTED IN DELTA!! CHECK OUT THE EXTERNALLY MAINTAINED REFSET FOLDER FOR ISSUES... (perhaps due to S3 Migration) | |
| Description-EN (full, delta and snapshot) | 2 | Following 2 description records added: > 4919631000005118 20170930 1 554471000005108 557091000005108 en 900000000000003001 Avlund mobility-tiredness scale (observable entity) 900000000000448009 | |
| Description-DA (full, delta and snapshot) | 2 description records added, matching those in the EN files + 695 records removed????????????? | ||
| Concept files | 1 new concept record: > 557091000005108 20170930 1 554471000005108 900000000000074008 + Following 6 concepts were inactivated: > 555111000005107 20170930 0 554471000005108 900000000000074008 | ||
| Stated Relationship (full, delta and snapshot) | 7 | 6 records inactivated + 1 record added | |
| Relationship (full, delta and snapshot) | 73 | 65 records added + 8 records removed ???????????????????????????????????????????????????????? No new stated relationships were changed as part of the DK editing cycle, and no concepts were updated. These changes are therefore unexpected. Looking into them they appear to be partially a result of role group churn (due to the known issue in the classifier wrapper), but I've also found several which are new to the March release, and also some that were in the November release as inactive yet have now been activated (with all identical fields including the Role group) in the March release. Some have even been born inactive in this release... Further investigation therefore in progress... We discovered that the differences are due to the following:
Confirmed on the re-test that classifier wrapper fixes have removed 16 of these differences as expected - remaining differences are due to the reasons above and so are valid differences. | |
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
AssociationReference files (full, delta and snapshot) | 1 | Mistake made in the technical process - Michael now resolved it - AAT re-tested and confirmed resolved | |
| AttributeValue (full, delta and snapshot) | 356 | 12 of these records are due to the moduleID having been wrong in the previous release (was core, now corrected to DK moduleID in this release). Remaining 344 records expected due to inactivations of descriptions made by DK | |
| Description-DA (full, delta and snapshot) | 695 | DK do not keep records of the number of components they have updated. According to the traceability service, between December and March (their editing cycle for this release) they changed approx 350 concepts - HOWEVER in almost every concept they inactivated the old Description and created a new Description, so multiple changes per concept. The good news is that this matches the diff report, which shows 349 active record changes (i.e.) new description records, and 346 inactivation records. | |
| Language-DA (full, delta and snapshot) | 693 | There are less changes to the Language records than to the Description records, due to the back end fixes that were required as part of the editing cycle. The description-DA file contains 4 unchanged apart from the effective time due to these fixes. The language refsets for the two extra inactive descriptions are already inactive, and thus not appearing in the current language refset delta: id effectivetime active moduleid refsetid referencedcomponentid acceptabilityid | |
| ModuleDependency (full, delta and snapshot) | 2 | 2 new March 2017 records added as expected | |
| Relationship (full, delta and snapshot) | 25 | No new stated relationships were changed as part of the DK editing cycle, and no concepts were updated. These changes are therefore unexpected. Looking into them they appear to be partially a result of role group churn (due to the known issue in the classifier wrapper), but I've also found several which are new to the March release, and also some that were in the November release as inactive yet have now been activated (with all identical fields including the Role group) in the March release. Some have even been born inactive in this release... Further investigation therefore in progress... We discovered that the differences are due to the following:
Confirmed on the re-test that classifier wrapper fixes have removed 16 of these differences as expected - remaining differences are due to the reasons above and so are valid differences. |