| Jira |
|---|
| server | IHTSDO JIRA |
|---|
| columns | key,summary,issuelinks |
|---|
| maximumIssues | 200 |
|---|
| jqlQuery | filter=14658 order by issuekey asc |
|---|
| serverId | b202d822-d767-33be-b234-fec5accd5d8c |
|---|
|
| Jira |
|---|
| server | IHTSDO JIRA |
|---|
| columns | key,summary,issuelinks |
|---|
| maximumIssues | 200 |
|---|
| jqlQuery | filter=14642 order by issuekey asc |
|---|
| serverId | b202d822-d767-33be-b234-fec5accd5d8c |
|---|
|
This is a scheduled maintenance release for prioritised defect fixes and improvements, including an International Drools Rules (v1.16) update, but also marks a significant step as it moves the classification process into a new external stand-alone service.
Whilst compatibility and consistency with the "internal" (SnowOwl) classification results was a key goal for the new external service, there are some differences in the handling of concept equivalencies which should be noted. With the new classification service, a cloned equivalent concept is inferred as the new parent of the original concept, whereas previously the original concept was not changed. Furthermore, the original concept should also be a subconcept of the cloned concept. This is the normal representation of equivalency between two concepts.
Equivalent concepts are still highlighted and displayed side by side in a single row in the classification results. The details of their inferred relationships are not important, however, since the equivalency must be resolved to progress with the concept/task, and any new inferred relationships will be eliminated once the equivalency is fixed and re-classified.
...