Version 3.1 "Papercuts"

Post Reply
User avatar
Posts: 548
Joined: Tue Aug 21, 2018 3:28 am
Location: Puerto Rico

Version 3.1 "Papercuts"

Post by rosarior »

Version 3.1 is available from the Python packager index and from the Docker hub.

Like version 3.0, this one is also filled with big updates but since they were backwards compatible the release was named 3.1 instead of 4.0 as semantic versioning guidelines adopted dictate.

The full release notes are available here:

The summary of the biggest changes in this release:

* We figured out a way to calculate offline images hashes. This means we can finally enable browser caching of document thumbnails and images. The default cache expiration is 1 year and can be changed with the DOCUMENTS_PAGE_IMAGE_CACHE_TIME setting. Cache invalidation happens automatically so there is no need to clear the browser's cache when images change.

* Another big change included in this release if the web based configuration system. While still available it is no longer necessary to create and modify Python setting files. All configuration changes can now be performed from the browser. Changes are stored in a YAML encoded file in the media folder. Users can also provide their own YAML configuration file. Changes still require a restart of the Mayan service process, there is still no way around this as it is a design of Django, the we framework used by Mayan. We are exploring methods to improve this.

* A frequently request feature by systems integrator is being able to change the title of the project to rebrand their offerings. This can now be easily achieved with the COMMON_PROJECT_TITLE setting.

* Many updates were added to the models to improve how data was exported and improved. This means that converting from a database manager to another has a much higher rate of success than before, using Django's dumpdata and loaddata. We've also added a custom command named convertdb that handles the entire process of database conversion. We will be adding a documentation change and/or a wiki section on different methods to do this.

* Many more events are now tracked and available for subscription or as triggers for workflows.

* ACL support was added to more objects in the system allowing for administration delegation. Some examples: Metadata types, Message of the day, settings and indexes.

* The main menu now refreshes when there are changes in the available objects in the system. For example: If there are not tags available the view all tags menu item is not displayed, only the create tag menu entry. As soon one tag is created the menu updates and the view all tags is also available. This refreshing/updating intelligence also extends to permissions and access controls. If an user doesn't have permission to view any of the available tags, the view tags menu entry will not be displayed. If that same user is granted access to a tag, the menu updates accordingly. This feature reduces confusion form users that see a menu entry but see the permission denied page when they try to access those menus.

* We've started working of a feature to sort documents. In line with out policy, we will start releasing this feature in incremental updates. Sorting documents, which are the most abundant database record in a Mayan install can be taxing to the database. In this first stage we worked the model fields and database indexing necessary to sort the documents. By default documents will always be sorted now by their label instead of their ID as was previously the case. As the user interface changes to support user selection of sorting columns improves more visible changes will be added.

* The actions and links in most views are also now sorted alphabetically. This breaks the previous groupings by function but our testing indicated that users preferred alphabetically sorted links as they were easier to scan visually and find in a hurry.

* In other to make Mayan more self documenting we've added help messages in many views. Instead of a staring at a blank screen and having to open a tab to browse the documentation, the view will now display an icon, a short explanation of the view or the objects it should display and the most common links that will affect that view.

* It now possible to disable password changes. This is useful when your installation has an guest or demo account meant to be used by many users.

* While they've remained visually the same, the dashboard widget have been refactored to support many new features like access checking, custom templates and custom renderers. It is now possible to customize the dashboard widgets to display not just text but graphics and charts too. This release added the code changes and if no problems are reported subsequent versions will add the visual changes to the widgets.

* Besides the existing menu entry to view the recently accessed documents. A new entry was added to view the newly uploaded documents. By default the 40 most recently added documents are shown but this number can be changed with the DOCUMENTS_RECENT_ADDED_COUNT setting.

* We also added support for favorite documents. Each user can add up to 40 documents in their own favorite list. This number can be changed with the DOCUMENTS_FAVORITE_COUNT setting.

* The field size of the document type label was increased from 32 to 96 characters to allow for longer document type names.

And many more fixes and additions too long to add here. For the complete list see the release notes at
Post Reply