Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I currently maintain a distribution for farm recordkeeping (http://drupal.org/project/farm) and in it we use the Log module (http://drupal.org/project/log) to represent specific events as log entities. Log entities have a name, status (done / not done), and a timestamp, and can also be given other fields via Drupal's Field API.
I am going to be building a checklist system on top of the log-based architecture I currently have, and I just came across this module. I figured I would create this issue simply to think about and discuss if that makes any sense.
I saw this issue #2056411: Attach checklists to entities as fields, and specifically comment #14 describes what I'm talking about: https://www.drupal.org/node/2056411#comment-8487769
Essentially, it would mean that individual items in the checklist could somehow be linked to specific Log entities.
I need to read through the code of this module in greater detail to understand it, and see if that would make sense. Input and ideas are welcome!
Comments
Comment #2
m.stentaI will outline one of the use-cases I have in mind more specifically:
Some farms are required to keep records of sanitation and other food-safety related activities. They need to perform certain activities on a regular basis, and keep records of the activity details.
In farmOS, those records are represented as Log entities. What I am envisioning is creating a set of checklists, using this module, for specific groups of activities that need to be performed on a regular basis (ie: daily, weekly, monthly). And when an item is checked off, it automatically creates a Log entity for that task. The user could then click through to that log entity to add more details, perhaps.
Comment #3
m.stentaI think for this to work, checklists would need to be full-fledged entities. I see there is some discussion about that in #2198085: [META] Roadmap - I will read through that and add any thoughts I have.
Comment #4
traviscarden commentedAn approach that might give you what you need without requiring a major architectural refactoring, @m.stenta, would be to create a hook that lets you react to a checklist item check/uncheck event. If a few details, including the checklist and item IDs, were passed into the hook, you would probably have everything you would need to generate log items. Let me know if such an approach seems desirable.
Comment #5
m.stenta@TravisCarden - Yes, I was thinking about that approach. That might be all I need.
I will be turning my focus to this part of the project next month. I'll give the hook approach a try, and if it works, I'll contribute patch(es) back!
Comment #6
traviscarden commentedClosing for apparent lack of interest.