Before installation
Contents
Review the following information to understand the installation and implementation process. If you did not buy CaseMap Server, you only need to install or upgrade the TextMap client application.
Installing TextMap involves the following:
| • | TextMap client application installed on local machines |
| • | CaseMap Server (optional, for clients who want to create SQL cases) |
| • | CaseMap Admin Console (optional, for clients who want to create SQL cases) |
Implementing TextMap can involve one or more of the following:
| • | Configuring SQL Server for CaseMap Server installation |
| • | Creating network folders to store local case files or creating SQL servers and SQL cases in the CaseMap Admin Console |
| • | Applying network folder and field level security for local cases in CaseMap or setting up users, roles, and permissions in the CaseMap Admin Console for SQL cases |
| • | Assigning users to SQL case databases in the CaseMap Admin Console |
| • | Creating network folders to store case transcripts and other related files (videos, etc.) |
The licensing options for TextMap include:
|
Please review the current system requirements for setup considerations for your processor and RAM. Review each section in advance before making expensive hardware and network decisions that may not be in line with LexisNexis recommendations. Please keep informed of TextMap release updates and how they impact your system by checking our Web site at http://www.lexisnexis.com/casemap/textmap.aspx?content=downloads. |
Local cases should be stored on the network where all case users can access the file. Local cases should be stored by case name or matter, or according to your organization's internal guidelines. Most organizations have network directory design guidelines already in place for storing information in a consistent manner. If there is no network setup or only one individual is using a case, the case can be stored locally on a user's hard drive. In this instance, nightly back-ups of the case should be made to a flash drive or portable hard drive. In this scenario, other users cannot access the case without using a replica copy. Synchronizing data with the primary case should then occur regularly.
|
Local case security is applied by controlling access to cases stored in directory folders on your LAN. Grant folder access to only those users working on a particular case. In this manner, you are preserving case integrity by preventing others from reviewing your case information and strategy. |
All users must be added to a case in order to access it within TextMap or be assigned to a TextMap SQL case in the CaseMap Admin Console. Having a TextMap license does not grant a user permission to open a case. We also recommend that you require users to set passwords. Users can set and change their passwords at any time. If a user of a local case has forgotten a password, contact Technical Support to have it reset. If a user of a SQL case has forgotten a password, he or she should contact their case database administrator. |
If you are using CaseMap Server, a migration path for importing cases from previous TextMap versions is essential. You should only migrate a case to CaseMap Server once. If you experience an issue during the import, you can try migrating the case again. Each SQL case requires its own SQL database. For more information, see the CaseMap Server Answer Center. |
 |