HOME > NEWS > 뉴스 게시판
뉴스 게시판
  [Talk Law Global 2014 Mar] 2nd Annual eDiscovery and Records Management Forum
작성자 : admin
작성일 : 2014-03-19 11:51 | 조회 : 4,756


2nd Annual eDiscovery and Records Management Forum
Millennium Hilton Hotel, Seoul, South Korea
15-16 April 2014

It is important for businesses and those who advise them to understand the expectations of US discovery, both because they have to face it and because it will become increasingly necessary for these jurisdictions to adopt their own discovery rules […]” – Chris Dale 

Maximizing your reach on litigation readiness and risk mitigation through the strategic management of data and records in your legal business infrastructure. Discover practical & effective insight to bolster your defense against litigation and to take a firmer hold on your data.



Attend this informative event and gain practical insights into key issues indicating:

      • Discovery and Korean Criminal Litigation Law

      • Negotiating with the Government in Regulatory Investigations and Litigation
      • Science and Technology in Law: Big Data
      • Latest Developments in eDiscovery Around the Globe 
      • One Step Ahead of Litigation, Steps to Take Now 
      • Cyber Liability: Developing a Data Breach Response Plan and Risk Mitigation Strategy
      • Intellectual Property and eDiscovery: Maintaining Compliancy whilst Protecting Your Intellectual Assets 
      • Strategic and Effective Record Management (RM) in Response to the Needs for eDiscovery 
      • Treating, Managing and Running eDiscovery as a Vital Business Process 
      • Dynamics of Multi-Lingual eDiscovery in Cross-Border Legal Cases 
      • Managing eDiscovery Within Multi-Jurisdictional Disputes 

33, Hangang-daero 52-gil, Yongsan-gu, Seoul, Korea
Tel. +82 2 323 8523 / Fax. +82 70 7545 8525 / eMail. info@koreapen.org
Copyright @ 2011 ASCo, All Rights Reserved.

Warning: Unknown: write failed: Disk quota exceeded (122) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (../data/session) in Unknown on line 0