Search 1.4 billion lines of Odoo code on GitHub

dms

Author: MuK IT, Tecnativa, Odoo Community Association (OCA)
License: LGPL-3
Branch: 14.0
Repository: OCA/dms
Dependencies: base, http_routing, mail, mail_preview_base, portal, web, and web_drop_target
Languages: AspectJ (8, 0.1%), Bourne Shell (3, 0.0%), C (5, 0.0%), C# (8, 0.1%), C++ (6, 0.0%), COBOL (5, 0.0%), CoffeeScript (1, 0.0%), Fortran (0, 0.0%), Go (5, 0.0%), Groovy (1, 0.0%), HTML (457, 3.7%), Java (5, 0.0%), JavaScript (351, 2.8%), Markdown (88, 0.7%), PO File (4291, 34.5%), Python (3436, 27.6%), SVG (62, 0.5%), Sass (158, 1.3%), Scheme (3, 0.0%), XML (3149, 25.3%), and reStructuredText (411, 3.3%)
Other branches: 12.0, and 13.0
Other repositories: Change2improve/dms, ForgeFlow/dms, kmee/dms, ksher-solutions/dms, rameshwordhakal/dms, shawndanger/dms, and tegin/dms

Document Management System

Beta License: LGPL-3 OCA/dms Translate me on Weblate Try me on Runbot

DMS is a module for creating, managing and viewing document files directly within Odoo. This module is only the basis for an entire ecosystem of apps that extend and seamlessly integrate with the document management system.

This module adds portal functionality for directories and files for allowed users, both portal or internal users. You can get as well a tokenized link from a directory or a file for sharing it with any anonymous user.

Table of contents

Installation

Preview

mail_preview_base is required for DMS but it is recommended to install all the other mail_preview modules from social OCA repository in order to improve the preview of files.

python-magic library is recommended to be installed for having whole support to get proper file types and file preview.

Configuration

To configure this module, you need to:

  1. Go to Documents -> Configuration -> Storages.
  2. Create a new document storage. You can choose between two options on Save Type:
    • Database: Store the files on the database as a field
    • Attachment: Store the files as attachments
  3. Next create an administrative access group. Go to Configuration -> Access Groups.
    • Create a new group, name it appropriately, and turn on all three permissions (Create, Write and Unlink - Read is implied and always enabled).
    • Add any other top-level administrative users to the group if needed (your user should already be there).
    • You can create other groups in here later for fine grained access control.
  4. Afterwards go to Documents -> Directories.
  5. Create a new directory, mark it as root and select the previously created setting.
    • Select the Groups tab and add your administrative group created above.
  6. On the Directory you can also add other access groups (created above) that will be able to:
    • read
    • create
    • write
    • delete

Migration

If you need to modify the storage Save Type you might want to migrate the file data. In order to achieve it you need to:

  1. Go to Documents -> Configuration -> Storage and select the storage you want to modify
  2. Modify the save type
  3. Press the button Migrate files if you want to migrate all the files at once
  4. Press the button Manual File Migration in order to specify files one by one

You can check all the files that still needs to be migrated from all storages and migrate them manually on Documents -> Configuration -> Migration

Usage

The best way to manage the documents is to switch to the Documents view. Existing documents can be managed there and new documents can be created.

Portal functionality

You can add any portal user to DMS access groups, and then allow that group in directories, so they will see in the portal such directories and their files. Another possibility is to click on "Share" button inside a directory or a file for obtaining a tokenized link for single access to that resource, no matter if logged or not.

Known issues / Roadmap

  • Files preview in portal
  • Allow to download folder in portal and create zip file with all content
  • Save in cache own_root directories and update in every create/write/unlink function
  • Add a migration procedure for converting an storage to attachment one for populating existing records with attachments as folders
  • Add a link from attachment view in chatter to linked documents
  • If Inherit permissions from related record (the inherit_access_from_parent_record field from storage) is changed when directories already exist, inconsistencies may occur because groups defined in the directories and subdirectories will still exist, all groups in these directories should be removed before changing.
  • Since portal users can read dms.storage records, if your module extends this model to another storage backend that needs using secrets, remember to forbid access to the secrets fields by other means. It would be nice to be able to remove that rule at some point.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • MuK IT
  • Tecnativa

Contributors

Other credits

Some pictures are based on or inspired by:

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/dms project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.


Dependency Graph