Uwazi v0.5.0 released
Pre-releaseNew features
API documentation
We’ve started to document API commands for Uwazi. We're currently working on documentation for the search, entities, and attachments endpoints. You can access the API for your Uwazi instance by adding /api to the end of your Uwazi URL, like this: https://yourinstancename.uwazi.io/api. Please note: this is a work-in-progress!
Google Analytics integration
We’ve integrated Google Analytics into Uwazi so that administrators can see how many visitors are accessing their public-facing Uwazi content. More information >>
Other improvements
Choose between AND/OR operators in filters
We’ve added the ability for users to choose between using AND or OR operators in the Uwazi filters. More information >>
Easier to find the target documents for your connections
We’ve improved the connections search functionality by limiting the search to document titles instead of the entire document content. This will make it much faster to find the target document for your connections.
Easier access to Downloads
We’ve moved the Downloads section (previously the Attachments tab) to the main Information tab in the side panel, making them easier to access and edit. More information >>
Automatically attach files in all instance languages
We've added functionality to attach a file to all language versions of an entity / document with the click of a button. This will speed up the process of adding downloads that are shared between languages like images or sound files, for example. More information >>
Automatic document language detection
If your Uwazi instance is in multiple languages, it is important for users to know the language of documents as they are browsing the collection. We've added the ability for Uwazi to automatically detect the language of your document, and users will see the language of the document if it does not match the selected user interface language.
Bug fixes
- We fixed a bug that corrupted metadata-based relationships when a select-type property's name was changed
- We fixed how aggregations are generated for unpublished documents in the Uploads section
- We fixed a bug that broke the “load more” button for connections
- We changed some elasticsearch configurations that were causing incorrect sorting results in connections
- We fixed a bug that caused multi-select filters to disappear when writing on a numeric filter
- We fixed a bug that broke the filters when displaying rich-text properties on cards
- We fixed the index mapping so that Elasticsearch's field amount does not go beyond the usual default settings
What does this mean for you?
For those of you who have an instance hosted with us, we have already deployed this upgrade to your Uwazi instance, so there’s no need to do anything.
If you are hosting Uwazi yourself, you will want to upgrade by downloading the latest release and run the following database migration using terminal on the root directory of Uwazi:
$ export DATABASE_NAME='name'
by default the name is uwazi_development.
If the mongodb server is on a remote machine, then configure it by:
$ export DBHOST='theHost'
then run:
$ node ./run_migration.js ./app/api/migrations/assign_file_languages.js
$ node ./run_migration.js ./app/api/migrations/fix_entity_based_references.js
Additional information
- See all of our updates in our GitHub changelog
- We’re working on our user guide on GitHub and you’re invited to contribute.
- Contact us if you have any questions!