Concordance version 10.08 and Concordance Image version 5.05 are now compatible with Microsoft® Windows® 7, Windows Server 2008 SP2 and Windows Server 2008 R2
Beginning with Concordance version 10.08 and Concordance Image version 5.05 the location for application data folders are now stored in the following locations and a shortcut is added to the desktop:
Note: When a previous version of Concordance 10.x is uninstalled, the CPL and Databases folders associated with the previous version are not removed. Make sure the folders are backed up before manually deleting them.
When performing workstation installs, share the following application data folder for users to access Concordance version 10.08 and Concordance Image version 5.05 data. This requirement is a result of how Microsoft Windows 7 stores and accesses application data, thus making it necessary for various Concordance and Concordance Image files to be moved to allow the applications to function as expected.
Important: Only the folder listed above needs to be shared, not the entire Application Data tree.
For detailed information on installing Concordance and Concordance Image, see the Installing Concordance and Installing Concordance Image topics in Concordance Answer Center.
The following table defines the file and directory changes for Concordance version 10.08 and Concordance Image version 5.05:
|
Tags and tag folders can now be renamed in the Tags and Issues Management dialog box. Similar to renaming a folder on a computer, simply click the Rename button and type the new tag or folder name. Concordance automatically updates all tagged records with the new tag name.
For more information, see the Rename tags and folders topic in the Concordance Answer Center:
Version 8 databases required a dialog to create, delete, and modify persistent tags, but with version 9 and 10 databases, all tags are persistent. Also, version 8 databases stored tags in two files (.tag and .trk), and needed the validation window to resynchronize the files. Neither of these features (Persistent Tags and Tag Validation) was needed for version 9 or version 10 databases.
|
•Issue codes can be removed from the selected text not only in the Notes dialog box but now also by right-clicking on the issue in the Tags task pane, and clicking the Uncheck issue command. This does not delete the issue code from the database. Issue codes can be deleted from the Add/Delete panel in the Tag and Issue Management dialog box. •The field names in the Cowco and Calfco sample databases have been standardized so they also match the names used in Concordance Training classes and in the sample Training databases. |
•The Conversion Report is a comma-delimited conversion log file generated at the end of the database conversion process when converting existing databases to Concordance version 10.x or later. When the database conversion completes, Concordance generates and saves the Conversion Report - [database name]-[date].csv file in the same directory as the converted database(s). For more information about the report, see the Conversion Report topic in the Concordance 10 Help system. •Integration with Equivio® has been added to Concordance. Equivio is an optional companion product for Concordance e-mail databases. In Concordance, Equivio highlights the textual differences between two e-mail documents. Equivio helps identify and skip redundant text during document reviews in Concordance. •For more information about the Equivio integration in Concordance software, see the “File | Send to | Equivio” topic in the Concordance 10 Help system. •Implemented a confirmation dialog box so users can confirm they intended their tagging action when they have selected multiple records in the Table view and drag them to a tag. •Concordance databases now record which major version they were created in or converted to in the database's corresponding .ini file. For example, the .ini entry appears as: [VERSION]
version=10
|
•A log of security changes can now be exported and viewed from the Security Log tab inside of File > Administration > Security. See the Release Document and Concordance Help for detailed information. •Added the option to code Issues by holding down the Shift key while left-clicking in the Tags pane. This is to reduce the number of issues that are created accidentally. This option is found in the Tools:Preferences menu on the Browsing tab of the Preferences dialog. |
•Manually refreshing Tags and Issues can be done by right-clicking in the Tag/Issue list and choosing "Refresh view". This will refresh tags or issues created and/or deleted by other users during the same session. If a tag that has been deleted by one user is marked by another user, then the tag will not be deleted. •Zap and Pack menu items have been moved from the File menu to the File > Administration menu, and these menu items now require the admin password to access them. •Concordance version 10 is a major version release, so all CPL (Concordance Programming Language) programs are in the CPL folder (…\Program Files\LexisNexis\Concordance 10\CPL). CPLs have the version number included in the name of the CPL. For example: AppendTextToField_v10.00.cpl. •Going forward, if a CPL is updated as part of a release, the version number will be updated to match the release number. •CPL names now have a standard naming convention for clarity. All CPL names now use mixed case to improve readability and no longer use odd abbreviations like using the number “2” in place of the word “to”. •The description headers in each CPL included in Concordance 10 have been updated to provide better information about using that CPL. •These steps have been taken to improve the usability of the CPLs, avoid confusion about which CPLs work with which version, and improve clarity when users contact Concordance support. Note: Some CPLs will not be compatible with Concordance 10. The CPLs that are most likely to have issues are CPLs that attempt to directly manipulate the .trk B-tree file.
Note: The new CPL naming convention does not affect whether CPLs created in prior Concordance versions are compatible with Concordance 10.
•The database version number has been changed to an integer to decrease confusion. Previously, the version included decimal values that had no impact on the database. There was no difference between database version 8.0 and database version 8.24. •Beginning with Concordance 10, Concordance no longer associates .dcb and .fyi files with itself on exit. •The “Bulk Convert Databases to Current Version…” tool has been added to the File:Administration menu. This tool will convert all databases in a folder and all of the folder’s children. The databases will be converted to version 10. •Added integration support for Electronic Legal Software’s E.L. Native Review tool. •Resolved an issue where Concordance did not detect the latest version of Verdict Systems Sanction®. Concordance now uses Verdict Systems’ preferred method to detect Sanction software, preventing the reoccurrence of this issue with future versions of Sanction. •Strengthened encryption for database and user passwords. •Resolved an issue where using Global Replace to replace text in a native document hyperlink would sometimes also alter a different hyperlink in the same document. •Concordance 10 can be installed on the same computer as Concordance version 2007 (v9.x), and Concordance version 8.x. This means that there will be an additional registry location, install folder location, and Add/Remove Programs entry. •Added support for importing Microsoft Office 2007 documents. •The Concordance executable file has been renamed to Concordance_10.exe. |
Concordance version 10 and Concordance Image version 5 support the Unicode™ Standard, SHA-1 Security password encryption and a relational SQLite .trk file structure that stores tags and tag histories, security and replication data.
Unicode provides a consistent way to digitally represent the characters used in the written languages of the world. As an accepted universal standard in the computer industry, the Unicode Standard assigns each character a unique numeric value and name. This encoding standard provides a uniform basis for processing, storing, searching, and exchanging text data in any language.
In Concordance version 10, Unicode is supported in Arabic, Chinese, English, Hebrew, Japanese, Korean, Russian, and other languages.
To display characters in Unicode within Concordance, the appropriate language packs need to be installed on the computer. For more details, see the Concordance v10 Installation Guide or the Installing Language Packs topic in the Concordance Answer Center.
Supporting Unicode required major database structure changes. For example, Concordance version 10 is installed in a new default directory and all databases need to be converted to version 10 or later. For more details, see the Database Compatibility sections in this guide below or the Concordance Help topic, "Installation and Database Compatibility".
Currently, Unicode is supported when importing, searching, printing, and exporting documents in the languages listed above. However, certain issues and tips are important to know when using these features with a non-English document. For example, when sending data to a third-party software program using the “Send to” feature, sometimes only ANSI text is sent. This is because some applications do not support Unicode character sets. Send to > Excel however sends Unicode text.
Note: The install guide resides in the same directory where Concordance version 10 is installed. The install guides and Release Document can also be downloaded separately here: http://answercenter.ediscovery.co/litigation/ac/cn_classic/index.html?pdf_documents.htm.
Note: “Send to” text is generally sent as ANSI rather than Unicode. Not all partners support Unicode formatted text.
Note: Kashida justification in Arabic text inserts Unicode character 0640 into the text of words to even out lines of text. Because these characters can be anywhere in a word, they can impact searching in Arabic text. Concordance includes a utility to strip out kashida from the text in the documents. This will allow searching and hit highlighting and does not impact the original document or .tiff file.
Note: Some Adobe® PDF files with Arabic text do not display the Arabic text in the proper right-to-left order in Concordance. These PDF files display the text in reverse order (left-to-right) because the files report the language incorrectly or are not in the standard format.
In support of Unicode, new options were added to denote highlighting when printing. This is to resolve the issue that in some character sets an underlined character may closely resemble a different character.
For more information, see the Unicode Support topic in the Concordance Answer Center.
|
In version 8 databases, every database included a built-in Default tag. The Default tag has been removed in version 9 and 10 databases. For conversions to version 10 databases, the Default tag is not renamed and will look the same as it did in version 8 or version 9 prior to the conversion.
Version 8 Default tag
|
After Conversion to 10
|
|
|
|
The capability to code issues in the Tags pane is added to Concordance 10 (press Shift and click). This option helps reduce the number of issues created accidentally. Setup this method of issue coding by selecting the “Use shift-left-click for issue coding” option on the Browsing tab of the Preferences dialog (Tools > Preferences).
|
The new TRK Maintenance Tool, allows database administrators to either scan only or scan and repair the .trk file. The TRK Maintenance Tool, File > Administration, scans all tags in the currently open database and, if necessary, cleans up SQLite table entries in the .trk file (e.g., broken links or orphaned entries).
Each time the maintenance tool runs, it creates a .csv file report that is saved in the database directory. The report lists all tag names, the total tag count, the number of documents tagged for each tag name, and whether any errors were found. The TRK Maintenance Tool function, like indexing, is an exclusive Concordance process that requires all users, except the database administrator, to be logged out of the database when the process runs.
For complete instructions see the Scan and Repair Help Topic in the Concordance Answer Center.
|
Bulk Field Format Resetting removes rich text formatting to save space or remove certain text features that affect the precision of hit highlighting when searching.
The Bulk Field Format Resetting has been added as a menu item under File > Administration. This functionality was already available for a single record at a time on a chosen field by using the Edit > Format > Reset Field Formatting menu item and was also available as a CPL for bulk format resetting, but administrators now have the ability to remove all rich text formatting e.g., italicized or color fonts in a simpler manner or with one click. After running Bulk Field Format Reset, all single byte and Unicode character sets are retained. To see the red search hit highlighting again, reindex the database, as indicated by the Reindex checkmark flag. The Bulk Field Format Resetting function, like indexing, is an exclusive Concordance process that requires all users, except the database administrator, to be logged out of the database when the process runs.
For complete instructions, see the Remove Rich Text from Multiple Records topic in the Concordance Answer Center.
|
|