1 / 8

Meet IKE

Meet IKE. Legal Server Integration. Why integrate ?. The integration with Legal Server will allow: Information that is collected routinely can be used as additional filters when searching for resources to use in a case.

galvin
Télécharger la présentation

Meet IKE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Meet IKE

  2. Legal Server Integration Why integrate ? The integration with Legal Server will allow: • Information that is collected routinely can be used as additional filters when searching for resources to use in a case. • Staff will be able to upload documents into IKE from LegalServer (ease of use) • Integration combines the power of Share Point with advanced search technology, with the power of our CMS, where important, usable information is stored.  

  3. Case Info to be Pulled from LS to IKE’s Metadata Fields • Case ID • Client Name • County of Jurisdiction • Gender • Legal Problem code/Special Legal Problem code • Court • Office • Advocate • Zip code

  4. Standard NJP Library View

  5. Legal Server View

  6. Tagging Form – If posting from IKE

  7. Create an API • Allows Legal Server to talk to IKE • All documents that are shared live on the SharePoint server (no need to share all LS docs) • Uploading while in IKE: enter LS Case # in tagging form and IKE makes the call to LS to return the designated data • If uploading from Legal Server to IKE: The tagging form will auto complete the LS fields

  8. Consider a Consultant! • json_array (    'md5' => [RESULT_MD5_HASH],    'result' => json_array (        'status' => [STATUS_MSG],        'num_results' => [RESULTS_COUNT],        'results' => array (            1 => array (                'id' => [CASE_DB_ID],                'label' => [CASE_IDENTIFICATION]            )        )    ))That next query will look as follows:json_array (    'md5' => [QUERY_MD5_HASH],    'query' => json_array (        'action' => 'get_matter_xml',        'matter_id' => [CASE_DB_ID],    ))

More Related