Overall we’ve made a strategic mistake when implemented Document as a View in Fibery. We had long discussions about how to fix it two years ago, but unfortunately it is not so easy (but we still want to do it in some future).
Document should be a Database conceptually.
So if you want to create Document Database, it is totally OK. There are some benefits and problems.
Problems
- If you want to link this Document Database to some other databases, you will have to add quite many relations.
- Database should live in some Space, so you will have to give access to this Space to all people (maybe not a problem)
Other than that, only benefits
Benefits
- You can add some fields if you need (like Assignment, State, etc if you need them in some cases)
- Automations are available (+AI in automations)
- Smart folders with filters are available
- You can create Views with Document Database entities (it may be handy for some cases, even Whiteboard View)
- Semantic Search will work