5

I want to make a document management system (interface in Ruby).
What do profesional sollutions (Alfresco, Liferay social office, others) use for storing and versioning documents?
What else can I use?

Key points:

  • storage space optimization (deltas, compression ...)
  • versioning
  • ability to index docs (can be external)
  • ability to make backups at runtime (live hot-backup)
  • locking?
  • scalability on large data volume
  • ensure data integrity (hashing?)
  • permissions
  • transactional
  • Workflow support (optional)

Bonus points:

Any books on this issue ?

clyfe
  • 23,695
  • 8
  • 85
  • 109

3 Answers3

5

Most of the enterprise document management solutions I've seen (Cimage, Documentum, LiveLink) definitely don't care about #1. Storage is relatively cheap, especially if it's storage vs processing (store and retreieve). They mostly rely on filesystem based storage - perhaps with name abstraction such that ShoppingList.doc perhaps becomes 20100909100101a.doc.rev1, with a database tracking the given-name, the stored name, revisions, and various other data {MIME type, headers & properties etc}. By not generating deltas + compression you get indexing very easily from any number of existing products/agorithms. Versioning is also extremely simple with this approach.

Depending on the size and scale you're building, you could also store versioned files within a database.

An (S)FTP or CIFS storage process would also allow your software to run on an app server with modest space, but store the files+history on a file or cloud server of some sort - although this isn't much different from filesystem based storage.

Rudu
  • 15,682
  • 4
  • 47
  • 63
1

Y'know, my first instinct would be to just use Subversion. You'll need external indexing, and if you want to store hashes you'll need to write some code to do it yourself, but everything else fits.

It ships with ruby bindings, though I'm not personally familiar with their quality.

Nicholas Knight
  • 15,774
  • 5
  • 45
  • 57
  • When I'll have TBytes of docs I'll need some sort of distributed storage and SVN won't work. – clyfe Nov 12 '10 at 14:33
  • @clyfe: Distributed storage is a whole different ballgame from what you're asking for. None of the systems you mentioned use distributed storage, and I can't imagine why you'd need it unless your traffic is ridiculously high. A good server with a bunch of 2TB disks in RAID 10 should do you just fine. – Nicholas Knight Nov 13 '10 at 01:56
0

alfresco is commonly used as the backend, it has a nice REST API. You can also define your own integration API if you don't like the included one.

Javier
  • 60,510
  • 8
  • 78
  • 126
  • Any usable docs or books? All tough I like the features, their wiki really kills my tiny ruby brain. I'm mostly interesting in how to define users, ACL's and read/write content, maybe define workflows ... – clyfe Nov 12 '10 at 13:46