Citavi 5.1 Released

New, Improved, and Changed Features

  • It's now possible to add words to the spelling checker dictionary.
  • In the PDF preview you can now press the spacebar to use pan mode.
  • In the dialog for the Attachments folder path, you can now enter variables, for example "%dropbox%\Information Literacy\Citavi Attachments". On each computer "%dropbox%" will now be resolved to the Dropbox path.
  • The Citavi Picker can be used to import references from the legal database Juris.
  • Citavi for DBServer can be used with SQL databases saved in Azure.
  • User management in Citavi for DBServer has been improved.
  • The Citavi pane now automatically opens in the Word Add-In.
  • Citavi no longer automatically enters an automatically determined language in the Language field.

Resolved Bugs

Citavi
  • If a formatted abstract was changed in a multi-user project, it could not be saved (Error message: Requested value ‘AbstractRtf’ was not found.).
  • During a full text search, the error message "Object is currently in use elsewhere" would sometimes appear.
  • Citavi would freeze if a task list was created and then closed in Word.
  • Running a saved search with the parameter Yesterday returned incorrect results.
  • Changes could not be saved if keywords for a quotation were not alphabetically sorted (Error message: Requested value ‘Keywords’ was not found).
  • Opening an image quotation in PDF format led to an illegal parameter error.
  • Citavi would crash if a second category was added to a knowledge item in the Knowledge Organizer.
  • Under certain conditions a Categories error could occur in the Knowledge Organizer.
  • Adding a new line in the Advanced search caused an error to occur.
  • The online search in the IEEE database returned incorrect results.
  • Saving all the attachments in a selection of references was not possible if only one reference had an attachment.
  • When importing from a PDF file, the URL and the access date were not imported if they were in the PDF’s metadata.
  • Importing a PDF file with Chinese characters could cause Citavi to crash.
  • DOI names with unusual character combinations (for example, 10.1002/1615-4169(200201)344:1<17::AID-ADSC17>3.0.CO;2-8) were not recognized as DOI names.
  • Importing chapters in edited books from PubMed led to an error.
  • When importing from a file containing tabular data, an error could occur if the references contained categories.
  • The import filter for RIS files from Reference Manager did not correct Reference Manager mapping errors for edited books and internet documents.
  • When copying references with linked PDFs with relative paths, one folder level too high was displayed in the path shown in Citavi.
  • Moving a PDF folder under File > Project properties > Paths caused an error to occur if a PDF document was open in the preview.
  • When copying or moving references from one project to another, tasks were not moved or copied.
  • Citavi 5 could not convert Citavi 4 projects if special characters appeared in the user settings (SQL error message).
  • Citavi 5 could not convert Citavi 4 projects if invalid ID values were present (Error: Invalid GUID).
  • Citavi 5 could not convert Citavi 4 projects if invalid RTF cold was present in formattable text fields (Error: Unknown file format).
  • Citavi 5 could not convert Citavi 4 projects if the client of a cloud synchronization service was not fully uninstalled (Error: Illegal characters in path).
  • When converting a Citavi 4 project to Citavi 5 format, the entries in the Language field were deleted.
  • Citavi 4 projects couldn’t be converted to Citavi 5 projects if Google Drive had been installed on the computer at one time.
  • After converting a Citavi 4 project to a Citavi 5 project, the Task Planner sometimes displayed too few results if the filter Photocopy or scan was applied.
  • When converting a project from Citavi 4 to Citavi 5, images that were saved as ideas were not transferred to the Citavi 5 project.
  • When saving a local copy of a server project the following error message would appear: Copy process for source project of type ‘Desktop SqlServer’ not implemented.
  • Under certain conditions the contents of "InitialSettings.crd" (a file with start options set by the administrator) were not applied correctly.
  • The citation key setting First word only (ignore articles) did not ignore articles.
  • The citation key definition did not save settings for persons across sessions.
  • When searching licensed databases Citavi did not use the saved access information.
  • Writer documents could not be formatted with Citavi 5 if Microsoft Office was not installed on the computer.
  • If multiple quotations from the same page of a single reference were present, quotations that were edited automatically appeared at the end of the list instead of remaining where they were originally.
  • In the table view, sorting by number returned unexpected results if letters were also present in the column.
  • When adding quotations for a reference, the spelling checker language had to be switched from German to English each time a new quotation was added.
  • If a website was saved as a PDF file in the Citavi preview, the PDF file was not renamed with the Citavi short title.
  • Citavi interpreted letters in paragraphs (e.g. 63a) as page ranges. As a result §§63a would appear in the Word document instead of §63a.
  • In the Knowledge Organizer it was no longer possible to merge two categories using the shortcut menu.
  • In the Table of Contents field, paragraphs were no longer displayed in annotated project bibliographies and the table of contents would appear as running text.
  • The contents of the Link to and Link from fields did not appear in table view.
  • Text that was entered in the Evaluation field would only appear on the Content tab after the user switched to another reference.
  • The keyboard shortcuts Shift+Insert and Shift+Delete (alternatives for Ctrl+C and Ctrl+V) no longer worked in formatted text fields.
  • Comments added to knowledge items were displayed above the knowledge item instead of below it.
  • The duplicates search returned false positives.
  • After an update to Windows Vista, several Citavi windows could no longer be opened.
  • The Groups field on the Content tab displayed text as cut-off if the Windows display settings were set to 125%.
  • Hyperlinks in the Abstract field were not clickable on the Overview tab.
  • The keyboard shortcut Ctrl+Shift+W for inserting references in footnotes did not work for TeX editors.
  • The BibTeX export definition could not be customized for the field Standard type for the Standard reference type.
  • When exporting private collections to BibTeX the location was exported as {Location/Call number} or {Location/} if no call number was present.
  • The Quote command settings were sometimes not transferred to the TeX-Editor.
  • When exporting the Report reference type to BibLaTeX the editor was exported as an author if the author field was empty.
Word Add-In
  • The Word Add-In did not work in Word 2007.
  • If a knowledge item was entered in Word with the Word Add-In, words in the knowledge item could no longer be selected by double-clicking.
  • Under certain circumstances, references could not be inserted in a table.
  • It was not possible to jump from one citation of a reference to the next citation in the document.
  • If the user started typing page numbers for a reference, the correct page number type was not automatically applied.
  • If the quotation page range and numbering type were entered in Citavi, they could not be changed in the Word Add-In.
  • If the user selected a reference and began typing the page numbers, "Other" was shown as the default numbering type.
  • Categories were not inserted in the correct order in the Word document.
  • In the APA citation style, author names were not abbreviated if the citations appeared as a multiple citation.
  • After converting EndNote fields, instead of the page range for the quotation the page range or the number of pages for the reference was displayed.
  • When saving a copy of a document with placeholders the bookmarks that Citavi’s Word Add-In had inserted for headings and knowledge items were deleted.
  • If the link symbol was clicked in the Word Add-In, the corresponding quotation was not selected in Citavi.
  • The Word Add-In only displayed new references in a DBServer project after switching to a another project.
  • If a DBServer project was started from the Word Add-In, the wrong welcome screen was displayed.
  • The feature Copy the reference into the current project did not work with DBServer projects.
  • DBServer projects were shown as open in the Word Add-In even if they had already been closed in Citavi.
  • The Help feature in the Word Add-In opened the manual for Citavi 4 instead of Citavi 5.
The Picker Family
  • The Picker did not save books on kindle.amazon.com/your_highlights in Citavi.
  • The Picker icon appeared blurred on some webpages.
  • Citavi could not be started from the Acrobat Picker if it was not already running.
  • The Acrobat Picker did not insert the URL for a PDF when the PDF was added to Citavi.
  • The Chrome Hunter did not import years from SpringerLink.
  • The Firefox Picker did not send results from Google Scholar to open projects.
  • The Firefox Picker slowed down the speed of some websites.
  • The Firefox Picker did not display an icon next to ISBN numbers on certain webpages.
  • If Citavi 5 was started with the Internet Explorer Picker at the same time as a highlight was saved as a quotation, the notification window was displayed twice.
Citation Style Editor
  • The condition Placeholder has no quotation page range did not work.
  • The Citation Style Editor would sometimes display the error message "Object Graph cannot be null. Parameter name: graph" if the user attempted to save changes after saving the style under a new name.
Citavi for DBServer
  • Creating a manual backup caused an error to occur.
  • After renaming a DBServer project, records could no longer be deleted.
  • When importing local projects in a DBServer database, too many folders were created.
  • If a DBServer project could not be loaded, an instance of Citavi remained open in the background. As a result the welcome screen could no longer be displayed.
  • The DBServer Manager would crash if the UI language was changed from German to English.

Known Issues

  • PDF files in the PDF/A format that are created with ABBYY FineReader can cause Citavi to crash if they are displayed in the Preview. The creator of the PDF component used by Citavi has been informed and is working on a solution. Temporary workaround: Do not display PDF/A files in the preview or save ABBYY-Finereader files as "searchable PDFs".
  • DBServer Manager does not work correctly if the rights for the current user are inherited from Active Directory groups. This affects the following processes: creating a database; creating, renaming, and deleting a project; and adding and removing users. (Details)
  • The creation of new Citavi databases in SQL Server 2008 and SQL Server 2008 R2 is currently not possible in DBServer Manager. (Details)