Transition From Legacy CCH to New UC ControlSight
The new ControlSight API separates Authority Document metadata, Citations, Mandates, and Common Controls into dedicated endpoints. The legacy Services API required a Shared Authority Document List or Authority Document ID and returned all related information in one payload.
In ControlSight, use /authority-document/:id for metadata, /authority-document/:id/citation for Citations, /authority-document/:id/mandate for Mandates, and /authority-document/:id/control for Common Controls.
Legacy CCH Authority Document IDs remain supported. Retrieve an Authority Document using its legacy ID to obtain the new ControlSight elementId, then use that ID for subsequent requests. ControlSight metadata also returns the legacy CCH ID in coreMetaData.
Key property mappings include legacy live to coreMetaData.live, creation and update timestamps to coreMetaData.created.timeStamp and coreMetaData.modified.timeStamp, citation references to primaryCitation.reference, citation text to primaryCitation.taggedText.text, Authority Documents to authorityDocument, and mapped controls to matchedControl.control.