The views expressed in this blog are those of the owner and do not reflect the views or opinions of the owner’s employer. All content provided on this blog is for informational purposes only. The owner of this blog makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site. The owner will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information. This policy is subject to change at any time. The owner is not an attorney, and nothing posted on this site should be construed as legal advice. Litigation Support Tip of the Night does not provide confirmation that any e-discovery technique or conduct is compliant with legal, regulatory, contractual or ethical requirements.
The new Lanceleaf version 11.2 Relativity One will be released in the United States on September 12. One of the great new features is that integration points will perform automatic field mapping between a workspace and the load file.
Relativity notifies admins if there are fields of different sizes.
Lanceleaf will also include a field named "Is Published?" to track when documents have been published to a workspace.
Relativity Integration Points (RIPs) assist with the import of data from third party systems into Relativity workspaces. RIPs facilitate field mapping. RIPs provide the same functionality as Relativity Desktop Client. Relativity 9.5 and later work with RIPs.
When importing data with csv files select Document as the dynamic object.
Integration points can be set to sync data at different intervals. Data is imported via FTP addresses.
When mapping fields be sure to set a unique identifier and an object identifier - these are the only two required fields.
Keep in mind that in order for view / edit / add / delete permissions to an analytics index in a Relativity workspace to be effective, having those permissions alone is not enough. A user must also have permissions for the search index in order to use analytics index permissions.
Generally, only one search index is created for a workspace, but multiple indexes may be created if there are large sets of documents in multiple languages, or if searches need to be limited to a specific subset of documents.
A user with permissions to a search index without permissions to an analytics index, will still have those search index permissions activated.