Enhancements

Version Added

•Convert your existing databases to Concordance Viewer to increase your production speeds and improve doc to doc navigation.

oConvert Concordance Native Viewer databases to Concordance Viewer.

oConvert Concordance Image databases to Concordance Viewer adding the flexibility of more markup types and color productions.

•UI Improvements that include a new database color scheme, icons, and menus for an updated modern look.

•Performance improvements for handling large files and production sets.

10.25

•Added support for the Concordance Viewer.  Create databases linked to the Concordance Viewer or complete your case with Concordance Native Viewer or Concordance Image.  The Concordance Viewer provides familiar features with a more modern approach.

•New scrub text feature supported in Concordance Viewer, Concordance Native Viewer, and Concordance Image.  Users can now choose to create document-level scrubbed text for documents with redactions during production.

•Installation has been updated to change all Concordance folder and registry keys under CloudNine instead of LexisNexis.

10.24

•Attachment ranges that express the family relationships of produced documents can be populated from production numbers.

•Ability to search for documents with one or more redacted pages in Concordance Native Viewer.  Search results can be tagged or reviewed by the user.

•A new option is available to create placeholder image files that are unsupported or unavailable for production in Concordance Native Viewer.

•Ability to select append or overwrite existing data in the production number fields from the Concordance Native Viewer production wizard.

•Native files may now be produced from the imagebase or from a field in the database containing the path and filename of the native file. All options provide naming and numbering selections including current image key, current filename, a field in the document or incremental numbering. File naming and path information may be written back to a field in the database and exported as a field.

•Removed the words “LexisNexis” and “Concordance” from printed separator sheets.

•Image information in the imagebase may be updated with an OPT that references the same image key as the original import.

10.23

•Improved import speeds, additional logging and additional file handling.

10.22

•Streamlined E-documents database creation.  The new E-document database creation engine processes and normalizes the data for improved functionality across all forms of native documents, creating a consistent document display (PDF formatted files) and improved doc-to-doc navigation for Concordance Native Viewer.

•New drag-and-drop operation for adding documents to an E-documents database.  

•Improved tag management and tag organization within the Tag and Issues Management dialog or the Tags task pane using a drag-and-drop operation.

•New Native File production for creating and renaming copies of native files using defined production parameters.

10.21

•New Persistent Search that accesses a saved list of search terms to locate all records within a database that match the search terms and highlights those terms in the Browse view.

•New Find Attachments scans the database to return all documents and any related attachments.

•New tag documents and attachments feature to tag documents and related attachments simultaneously.

•New edit layout feature to create and save layouts for displaying fields in the Edit view.

•Streamlined database creation wizard for creating new load file, E-documents, and E-mail databases.

10.20

•Improved performance when using the EDoc import feature to load electronic documents into Concordance.

10.19

•Create and save record sorting layouts for the Browse view.

•Backup & Restore Tag Utility for scheduled scan and backup of a database's TRK file.  Email notification for damaged TRK files and ability to restore a damaged TRK files from a backup.  

•Ability to select individual fields and reorder them in the Edit view.

10.17

•The Delimited Text Database Creation Wizard provides the easiest way to create a database, import data, OCR text and and link media files for viewing in Concordance Native Viewer or Concordance Image.

•Import a list of tags and folders into a database from a text formatted file (.txt) or export the tags and folders from an existing database to a text file that you can then import into another database. Tag lists can be easily modified using any text editor application.

•Improved performance when loading imagebase files for Concordance Native Viewer or converting existing Concordance Image imagebase files for use with Concordance Native Viewer.

•New import options for viewing EDoc and email message files in Concordance Native Viewer.

10.15

•Write Tags to a specified field or create Tags from values within a specified field from the Tag and Issues Management dialog box in Concordance.

•Create a back up of the contents of multiple database .TRK files within a single directory, including all sub-directories when specified, in the associated database .GAT files.

10.13

•Concordance software is integrated with the new Concordance Native Viewer to view electronic files, emails, and attachments without the need to have the source software program installed.

•Concordance Native Viewer image bases and productions can now be managed and processed through Concordance. Using the new image base management utility, rename paths and folders, rename media keys/aliases, and export multiple image bases to a single OPT formatted file.

•The new production module in Concordance provides all the tools needed to produce color or grayscale TIFF or PDF files.

•The new bulk print module in Concordance provides all the tools needed to print documents to a default printer in color or grayscale.  

10.10

•The General preferences settings now include the option to Always Map Initial Browse Path.  This option ensures that any instance of Concordance opens the default path that is defined on the server.

10.09

•Concordance and Concordance Image are now compatible with Microsoft® Windows® 7, Windows Server 2008 SP2 and Windows Server 2008 R2

10.08

•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.

10.07

•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.

10.06

•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.

10.05

•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.

10.02

•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.

•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.

•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.

•The Default tag has been removed. 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.

•Added the capability to code issues in the Tags pane (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).

10.00

•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.

•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.

8.00