[Feature Request]: Entry field type #1176
Description
Checklist
- I am using an up-to-date version.
- I have read the documentation.
- I have searched existing issues.
Description
It would be pretty useful to have the ability to link an entry to other, related entries. My use case specifically could also be solved by entry groups, but having a field type could allow for more advanced relationships.
Solution
An entry field type could be added, which internally stores the ID of an entry.
As a widget, it could display a small thumbnail of the entry, along with some basic information such as the file path.
When clicking on it, it could open the entry it represents, though that presents the issue of how to get back to the previous entry. This could be solved by adding breadcrumbs to the entry panel, showing the entries you've navigated from, and clicking on them would return you to that entry and remove the relevant breadcrumbs.
When editing the field, it could present the user a sort of 'mini' library search, allowing them to search through the library as they would normally to find the entry they're looking for without disrupting their current search.
How I would do this would be to provide essentially a second, stripped-back view of the library, but supporting different "views" would likely require a lot of abstraction and refactoring of the current front-end. However, this would make other interesting features much easier, such as doing multiple, concurrent searches or interacting with multiple libraries at once.
Alternatives
Currently, I just put the name of the file into a normal text line field, but this isn't the best.
- If I wanted to check the entry it represents, I have to manually search for the file name, which is fairly tedious.
- If the file name were to change at any point, the field doesn't update, and I'd have to go through each field and update them upon changing a file's name.
- Visually, it provides no indication it represents an entry, and is easy to miss among a long list of fields.