Page History

...

LexEVS 6.4 CTS2 release consisted of the following changes:

• Interactive CTS2 API Documentation
• LexEVS 6.4 CTS2

CTS2 API Documentation

Interactive CTS2 API Documentation has been updated and is available for LexEVS CTS2 6.3.

• Note that issue LEXEVSCTS2-21 has been resolved and allows for value set names greater than 50 characters. 

Entities Active Flag

• Default URI Resolver is NCI's production URI Resolver

Property Qualifier Support

Property Qualifiers (property to property relationships) are now being returned by the CTS2 RESTful service in XML and JSON formats.The previous version of the CTS2 service (LexEVS 6.2) was updated to accept an "active" flag for entities.  As a side effect of this change, the default behavior of LexEVS API was inadvertently changed.  In 6.3, the default behavior was changed to return "active" and "inactive" entities by default.  

• Jira
  server NCI Tracker

  serverId7954a81f-12da-3366-a0ef-97c806660e7ckeyLEXEVS-811  JiraserverNCI Tracker

  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVSCTS2-

  29

The two options for the active flag are:

• ACTIVE_ONLY - The inquiry only applies to ACTIVE entries.
• ACTIVE_AND_INACTIVE - The inquiry applies to both ACTIVE and INACTIVE entries

• 35

http://<base url>/codesystem/AutomobilesNCI_Thesaurus/version/114.005d/entity/entities?active=ACTIVE_ONLY

C12435?format=json

Default URI Resolver

The default URI Resolver that CTS2 points to is now an internal URI Resolver at NCI.  This removed the dependency on an external URI Resolver being active.

• Jira
  server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVSCTS2-37