This suggestion is an initial idea or concept.
I believe it could help personalise installations and provide a flexible way to incorporate additional information through custom fields in the future. The ability to define custom fields would make it possible to store a wide variety of data without requiring a new feature request or the development of separate solutions for each use case.
Possible use cases (users can freely define the field name and the data to be entered).
| Custom Field Name |
Value |
| Location |
Library 1, Shelf 12 (see #56 ) |
| Call Number |
ABC-1234 |
| Format |
Paperback |
| Owned |
Yes (see #123 ) |
| Purchase Price |
€10.00 |
| Purchase Date |
2025-03-15 |
| Condition |
Good |
| Loaned To |
John Smith |
Initially, these could be simple data entry fields. Later, support could be added for different field types, such as:
- Predefined options (Yes/No; Paperback/Hardcover/Audiobook)
- Numeric fields (1234)
- Text fields (Abcd)
- Date fields
- ...
This approach would provide greater flexibility while avoiding the need to implement dedicated fields for every possible use case. The custom fields could appear below the predefined information and be managed through an administration page.
Possible integation
Book View
Settings View
I think my suggestion is largely inspired by the way @WoltLab Suite handles custom fields for user profiles and differents forms. Because of that, I think they deserve to be acknowledged as a source of inspiration. 🙂
WoltLab Suite: https://github.com/WoltLab/WCF
Custom User Fields: https://manual.woltlab.com/en/user-options/
This suggestion is an initial idea or concept.
I believe it could help personalise installations and provide a flexible way to incorporate additional information through custom fields in the future. The ability to define custom fields would make it possible to store a wide variety of data without requiring a new feature request or the development of separate solutions for each use case.
Possible use cases (users can freely define the field name and the data to be entered).
Initially, these could be simple data entry fields. Later, support could be added for different field types, such as:
This approach would provide greater flexibility while avoiding the need to implement dedicated fields for every possible use case. The custom fields could appear below the predefined information and be managed through an administration page.
Possible integation
Book View
Settings View
I think my suggestion is largely inspired by the way @WoltLab Suite handles custom fields for user profiles and differents forms. Because of that, I think they deserve to be acknowledged as a source of inspiration. 🙂
WoltLab Suite: https://github.com/WoltLab/WCF
Custom User Fields: https://manual.woltlab.com/en/user-options/