I see myself re-creating the same views over and over again, especially if they are used across different databases.
The main purpose of additional collection field views, is often adding context.
That is because navigating fibery is still the main challenge for uses in my experience.
I use additional collection views (as tabs in fields) to have direct access to:
- my recent content (across a number of personal databases)
- the teams recent content (across a number of shared databases)
- any listing of entities that don’t need a dedicated field in the currently viewed entity.
- to merge linked databases of the current entity together in one field, as to remove empty fields or many fields being shown in the page (a big issue in fibery; its impossible to hide collection field automatically when empty)
Because of the re-use of common views, it would be much more efficient (for the fibery as well as for the users) to attach existing views to collection fields.
Please add option ‘Link Existing View’