Release QA Report Documentation

There are two QA reports generated during the release process:

Release QA
Release Finalization QA

Listed below are all of the possible messages that can be included in these QA reports, and what action should be taken for each of them:

Release QA

DestinationTerminology target used more than once
- Mappers confirm whether okay for current project
Map record has more than one entry
- Mappers confirm whether okay for current project
Map record not marked ready for publication
- Stop release – more work needed doing
  - Alternately, mappers confirm whether listed map records are not to be included in release
Map record failed validation check
- WCI to investigate which validation check failed for each concept, and present to IHTSDO
SourceTerminology concept not in scope - previously published
- Mappers confirm whether listed concepts correctly out of scope
SourceTerminology concept not in scope - edited this cycle
- Mappers confirm whether listed concepts correctly out of scope
SourceTerminology concept does not exist
- WCI to investigate why a ready-for-publication map record is associated with a non-existent concept, and present to IHTSDO
SourceTerminology concept inactive
- Mappers confirm whether listed concepts correctly inactivated
DestinationTerminology target code from previous release not used
- Informational – no action required.
Concept mapped to duplicate DestinationTerminology codes
- Mappers confirm whether okay for current project
Concept mapped to multiple DestinationTerminology codes
- Mappers confirm whether okay for current project
Concept has multiple map records
- Mappers confirm whether okay for current project
Concept mapped in previous version no longer mapped
- Mappers confirm whether listed concepts correctly no longer in scope
In-scope concept has no map record
- Stop release – more work needed doing
  - Alternately, mappers confirm whether listed concept not to be included in release
Ready for publication: ##
- Informational – no action required

Release Finalization QA

Finish Release run in TEST mode
- Informational – no action required
Map record discrepancy with recent edits -- will not be updated to release version
- Informational – no action required
Map record discrepancy -- will be updated to release version
- Mappers confirm concept ids match changes made on release server after clone
Map record found in release but no current record found -- no action will be taken
- Mappers confirm concept ids match map records that have been removed from production after clone
## records matched between release and current records
- Informational – no action required
Map record for concept out of scope will be removed
- Mappers confirm concept ids have been removed from scope on production after clone
## map records will be marked Published
- Informational – no action required

Release QA

DestinationTerminology target used more than once
- Mappers confirm whether okay for current project
Map record has more than one entry
- Mappers confirm whether okay for current project
Map record not marked ready for publication
- Stop release – more work needed doing
  - Alternately, mappers confirm whether listed map records are not to be included in release
Map record failed validation check
- WCI to investigate which validation check failed for each concept, and present to IHTSDO
SourceTerminology concept not in scope - previously published
- Mappers confirm whether listed concepts correctly out of scope
SourceTerminology concept not in scope - edited this cycle
- Mappers confirm whether listed concepts correctly out of scope
SourceTerminology concept does not exist
- WCI to investigate why a ready-for-publication map record is associated with a non-existent concept, and present to IHTSDO
SourceTerminology concept inactive
- Mappers confirm whether listed concepts correctly inactivated
DestinationTerminology target code from previous release not used
- Informational – no action required.
Concept mapped to duplicate DestinationTerminology codes
- Mappers confirm whether okay for current project
Concept mapped to multiple DestinationTerminology codes
- Mappers confirm whether okay for current project
Concept has multiple map records
- Mappers confirm whether okay for current project
Concept mapped in previous version no longer mapped
- Mappers confirm whether listed concepts correctly no longer in scope
In-scope concept has no map record
- Stop release – more work needed doing
  - Alternately, mappers confirm whether listed concept not to be included in release
Ready for publication: ##
- Informational – no action required

Release Finalization QA

Finish Release run in TEST mode
- Informational – no action required
Map record discrepancy with recent edits -- will not be updated to release version
- Informational – no action required
Map record discrepancy -- will be updated to release version
- Mappers confirm concept ids match changes made on release server after clone
Map record found in release but no current record found -- no action will be taken
- Mappers confirm concept ids match map records that have been removed from production after clone
## records matched between release and current records
- Informational – no action required
Map record for concept out of scope will be removed
- Mappers confirm concept ids have been removed from scope on production after clone
## map records will be marked Published
- Informational – no action required