91–100 of 172 posts
The single, killer feature I'm looking for in a document management system (besides collaborative environment that we're used to from gdocs) is a way to stamp versions and have those be reviewed independently, with git like diffs across them. Think gerrit for docs.
I never this is a thing. Our go to solution for this usually a kanban board in jira and confluence for the doc. Honestly would like to know what do I miss with this approach?
> Hermes uses Golang for the backend and Ember.js for the front end. It uses a PostgreSQL database for storage and Algolia to power its search capabilities. It also leverages several Google Workspace services for creating and modifying documents, sending email, etc. Great. 50 million incompatible parts combined with duct tape that is no better than Jira workflows with Google Docs, and less flexible. I can't wait to s…
What's wrong with that stack and how are they incompatible?
Box has Box Notes and Box Canvas for composing documents. Beyond the actual files, it has automated workflows like review & approval processes, document metadata, flexible sharing permissions, full text search, and a laundry list of other features enterprises want/need.
Alfresco was supposed to be the OSS alternative to documentum/stellent/etc closed source systems. It was basically a freemium model, which means that a complete OSS solution is out of reach. This basically looks like the same thing. I guess Hashicorp is slightly better at OSS, but... I dunno. A DMS needs: 1) storage (duh) 2) metadata 3) permissions enforcement 4) search / indexing 5) rendering to pdf and pdf signing…
I don't know what it is about the name Hermes for software folk, it's apparently irresistible. I've heard the name used by three different companies for internal projects just in my own circle in the last year. This concludes my useless comment. This is just a joke, that you learn what Hermes means at one company and have to unlearn that when the next Hermes enters your life :p
Earlier quoted context omitted.
Not mature, but if you fancy contributing I've started DMS.rs a couple of years ago: https://github.com/DMSrs/dmsrs It's written in Rust but I never managed to continue the project sadly :(
I can't help but notice the fact that language choice is put first. For document-organizer almost any language would work fine, there's no need for super-optimized memory management. Much more important would be language+ecosystem security and speed of safe development, IMHO.
Depends on the scale, and the original comment in this thread mention "serious performance issues" as something they care about, so choosing a faster language is not that far fetched as an idea (algorithms trump but still...)