A system for maintaining a repository of electronic documents?

A

alex_ant2013-10-02 11:17:05

git

alex_ant, 2013-10-02 11:17:05

There is a task: organizing a database for storing digitized documents from different branches of the company, together with metadata, full logging of changes, cross-references and document versions both in the plane of storage instances and in the plane of expiration and execution of new versions of documents. For clarity: a legal international company. Purpose: the ability to restore any slice of events many years ago, to find documents that were relevant at that time with all references.
A version control system immediately comes to mind, any of which serves the described purpose when developing code. But, as I wrote above, the specifics are that there is meta-data and many different version planes. There is such a thing as "Document management system": en.wikipedia.org/wiki/Document_management_systemBut all roads lead to ready-made, self-contained solutions with a ready-made UI and, as a rule, SaaS. And you need to have your own server a la Subversion or MongoDB server, which meets the needs, but is as flexible in use as a DBMS or VCS server.
What can you advise? I'm sure there are ready-made systems, but I do not know the correct terminology, and therefore it is difficult to find something. Thanks to!

Reply

Answer the question

In order to leave comments, you need to log in

6 answer(s)

K

kxyu, 2013-10-02
@kxyu

Alfresco. In theory, you can only take a repository of documents and twist your UI

I

Ilya Evseev, 2013-10-02
@IlyaEvseev

Lotus.

N

Nikolai Turnaviotov, 2013-10-02
@foxmuldercp

No matter how funny it is, for a bunch of documents from a bunch of branches in large offices, Sharepoint is usually deployed. With versioning, backups, search and other corporate goodies.

W

WordPress WooCommerce, 2013-10-05
@maxxannik

WordPress :)
It has a WP Document Revision plugin made with a grant from Google.
We made a document portal for a large federal company on it. Description of the project here casepress.org/?portfolio=baza-znanij Placed
on your own server or in the cloud - a matter of religion. Versioning is. Working with metadata is just a holiday. Holds loads well.
Extensibility - without brakes.
Now we are doing a similar project for a well-known federal brand.

S

Sergey, 2013-10-02
Protko @Fesor

well... mongodb - store revisions as sub-documents or just think about the data structure. having git or svn won't help you in any way. Keeping the database in svn is extremely stupid. git is highly undesirable for binaries. Well, again, it's stupid.
Since monga has a rest interface, you can write a simple client using angular.js + twitter bootstrap.

G

gorodok11, 2013-10-02
@gorodok11

Alternatively, you can look towards 1C: Workflow . You can organize access via the Web. Open systems with such functionality have not yet come across.