When Filently files a document, it already understands a fair amount about it: who it involves, where it belongs, what period it covers. Today that understanding goes into the filename and the folder β which is exactly what it was built for, and for most archives it's enough.
It reaches its limit when an archive doesn't split cleanly into folders. A genealogy archive is the clearest example: one document can belong to a family line, a place and a date range at the same time, and a folder tree forces you to pick one. What you actually want to ask is "everything about this family in this location."
Requested capability:
Extract entities from documents during filing (people, organisations, places, dates, document type)
Store them as tags on the document
Let users search and filter by combining several tags
Files stay where they are in Drive β tags are an additional layer, not a replacement for the folder structure
Please authenticate to join the conversation.
In Review
Feature Request
3 days ago
Get notified by email when there are changes.
In Review
Feature Request
3 days ago
Get notified by email when there are changes.