Document.One, here and after also referred to as D1, is a cloud-based document management system that enables you to store, manage, and track electronic documents and images of scanned paper documents.
Document.One key features
With D1, you can access content stored in databases as well as in other content management systems. The key features of D1 include the following:
- Version control
- Integration with external CMS
- Documents converting
- Documents security
Before modifying content, you check it out, and then check it in. When content is checked in, its version is automatically increased. This facilitates collaboration among multiple users who work with the same content and enables users to view previous versions of content. This way, nothing is ever lost.
See Content versioning for more information.
Integration with external content management systems
D1 is ideal for enterprises which have their content distributed on different content management systems. Our platform allows you to seamlessly access and modify the content stored in these systems without the need for migration. To do this, an administrator can configure external repositories in D1, allowing D1 users to access their data from a single system.
See D1 administration area for more information.
Currently the integration with the following CMSs is supported:
Additionally, you can create native D1 repositories, and use them to manage your documents.
Do you have a bunch of images that you need to merge into a PDF? Perhaps you need to create documents from Velocity templates? With ADx, nothing is impossible. See Converting contents for more information.
When using D1, you can create and configure roles with different access rights, and assign them to groups and users.
Why would I ever need D1?
The most powerful ability of D1 is probably the integration of multiple document repositories and their management from a single source, without the need to migrate any data. This could prove especially beneficial to large companies with a number of subsidiaries using different content management systems, in addition to the parent company content.
Imagine a large company acquiring another company. Now, the parent company needs to access and manage documents of the subsidiary. The standard process would probably look as follows:
- A team dedicated solely to content migration is assembled.
- Content is blocked for the time of migration (which could be quite long).
- Content is migrated - a time-consuming, multiple-stage process, where the team has to ensure that the migrated product meets the standards of the parent company, which could be hard to achieve while dealing with all kinds of data formats.
The negative sides of the whole process are likely to be the following:
- If the process takes too long, the migrated content will be obsolete, requiring another effort to bring it up-to-date.
- In order to complete the migration, the parent company has to engage significant resources.
- If the company ever changes its content management system, they have to repeat the whole process.
With D1, it's possible to avoid this process altogether, provided you're using one of the above mentioned CMSs. D1 is capable of storing the subsidiary company content as one of its repositories - you just need to provide the details of the external repository to establish the connection. Once you have it, you can access the content, and use the full power of D1 on it. There is no need for migration whatsoever, and you're avoiding the trouble if one of the subsidiaries decides to change their CMS.
Once you have D1 installed, you can read on how to connect to a CMIS repository.