This is pretty interesting but the takeaway I got from this (and from reading other things online about it), it sounds like it's mostly a form of data entry that exists outside of traditional CMS paradigms, like making web pages. In other words, it's a CMS-equivalent of database management for data (not pages) that can plugged into the CMS functionalities that pages are managed through (i.e. - Views). Sounds really awesome and I'm happy to know about this now. In the past, whenever a need for something like this came up, I always made content types but I can see now that was way overkill (despite working well enough). I'll definitely be using this in the future.
Not quite. With entity reference fields you can embed these in forms too. For example, the project I'm working on now allows for a "Payee" to be referenced. There's a lot of detail to collect around a payee and the majority of that will be unique to them (their name, address, payment details, etc) ECK gives a point-n-click UI to build the entity type. Then, when referenced in the form, I can look up existing payees so my users don't have to fill in all the details each time. New payees are created on the fly with the form submission as well. When the page is rendered for viewing the selected entity, or entities, are fetched for display without needing all that content on the submitted node.
Very useful explanation of nodes being different than entities created here. Thanks
Thanks. Never heard of this module before. Can be useful in some cases.
Nice module, well explained.
Thanks for the comment.
Nice video, thank you for sharing it with us, very helpful.
Thank you so much! Keep on the good work :)
This is pretty interesting but the takeaway I got from this (and from reading other things online about it), it sounds like it's mostly a form of data entry that exists outside of traditional CMS paradigms, like making web pages. In other words, it's a CMS-equivalent of database management for data (not pages) that can plugged into the CMS functionalities that pages are managed through (i.e. - Views).
Sounds really awesome and I'm happy to know about this now. In the past, whenever a need for something like this came up, I always made content types but I can see now that was way overkill (despite working well enough). I'll definitely be using this in the future.
Not quite. With entity reference fields you can embed these in forms too. For example, the project I'm working on now allows for a "Payee" to be referenced. There's a lot of detail to collect around a payee and the majority of that will be unique to them (their name, address, payment details, etc) ECK gives a point-n-click UI to build the entity type. Then, when referenced in the form, I can look up existing payees so my users don't have to fill in all the details each time. New payees are created on the fly with the form submission as well. When the page is rendered for viewing the selected entity, or entities, are fetched for display without needing all that content on the submitted node.
The date in the video is the 29.08. but the upload date is 28.08. 🤔