161–170 of 172 posts
I’m not claiming any right in naming after Ancient Greek gods. But wanna say that I choose the “same” name for a related goal project https://github.com/Ideabile/ermes
> https://github.com/search?q=hermes > 4,773 repository results
At least people have last names.
Source - https://www.silive.com/nation/2022/03/most-popular-baby-name...
Earlier quoted context omitted.
The hardest part of documents within a business is not producing documents but rather creating a useful library. Google Docs is a place where great documents go to die. Notion’s success (for example) is more about it making it possible to create a useable library of documents than it is about being an editor with neat widgets. I don’t know if Hermes is going to be particularly successful given it’s competing with thi…
I have lost count the number of times I’ve searched for a doc in Google drive and found nothing. It’s shockingly bad given that Google literally is a SEARCH company.
1. Like Google Search, you shouldn't try to organize your files, you should just let search do all the heavy lifting.
2. You should definitely organize things yourself, but search is a nice backup if you make a mistake -- anyone here create a document in Drive and have no idea what folder it *actually* ended up in?
3. Search? That's another team.Earlier quoted context omitted.
> https://github.com/search?q=hermes > 4,773 repository results
16,510 babies were named Olivia in 2022 At least people have last names. Source - https://www.silive.com/nation/2022/03/most-popular-baby-name...
The problem with versioning & management systems for docs is that you need the process to drive the adoption. Getting people to version, approve, and fully manage a document database is the hard part. Many companies do not even adequately document - they just send information in a Slack/Teams message and nothing is written down for later (this is why startups like Glean exist: https://www.glean.com/ ). There are mass…
https://www.glean.com/pricing is the worst ‘pricing’ page I’ve ever seen XD
Earlier quoted context omitted.
That's only because the scrooges don't have a stack of 5€ bills at hand. Sacrificing one such bill with every delivery magically makes Hermes minions much more reliable. Same applies to all the others.
I would pay him, but I never seen him. When he finds the house at all he puts the parcel at the baby buggy of my neighbor or directly in the paper collection bin.
This may sound sarcastic, but it is how it is. I don't envy the subsubcontracted delivery people, and I fume at the thougt of privatization, outsourcing to the lowest bidder, while their websites proudly present meaningless labels praising customer satisfaction, trust, reliability, whatever, while their hotlines are useless. But again, that's just how it is. I can't influence that shit. Except by 'tipping' the scale of the stressed, overworked, and time pressured person towards that 5€ dangling before his eyes, if package is delivered to my door.
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…
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…
Authors in larger organizations are more editors than authors, and documents require submissions and detailed reviews by many different people. A management feature would be summarizing comments (RID - review item discrepancies, AI - action items, etc) and status of each comment; plus document deltas; plus document delta markup (change-bars in the margins of presentation versions like PDF).
Another feature would be support of document hierarchies, where changes to one doc invoke functions/procedures/status changes on subordinate docs.
Another feature would be tagging a set of matching documents as a "release" set.
The enterprise products support much of this. And the price is not small.
The problem with versioning & management systems for docs is that you need the process to drive the adoption. Getting people to version, approve, and fully manage a document database is the hard part. Many companies do not even adequately document - they just send information in a Slack/Teams message and nothing is written down for later (this is why startups like Glean exist: https://www.glean.com/ ). There are mass…
> (this is why startups like Glean exist: https://www.glean.com/ ) https://www.glean.com/pricing is the worst ‘pricing’ page I’ve ever seen XD