# farmOS Demo Records Module **URL:** \ **Category:** Development\ **Created:** [September 17, 2026, 9:13pm UTC](https://farmos.discourse.group/t/farmos-demo-records-module/2606 "2026-09-17T21:13:41Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\ **Post date:** [September 17, 2026, 9:28pm UTC](https://farmos.discourse.group/t/farmos-demo-records-module/2606/2 "2026-09-17T21:28:17Z")
A few notes from today’s discussion: - What demo data should be created? - How should we store/manage the demo data? 1. CSVs that can be imported via the `farm_import_csv` module? 2. YML files that can be imported via the [Default Content](https://www.drupal.org/project/default_content) module? - What should trigger the data creation? 1. Automatically when the module is installed? 2. Manually by clicking a button in the UI? 3. Via Drush CLI commands? 4. … other? - How do we handle “shifting dates” so that the demo data appears “current”? (if the demo data has a timestamp in 2026, but someone installs it in 2036, we should shift the data to the present) - Do we need to be able to clean up (delete) demo data? - What happens if other records reference it? - Or do we just put a big warning somewhere? “Don’t use this on a real database!” - Can this tie into the setup wizard somehow? - The idea: the demo module may install certain modules to generate the data, and someone might want to start fresh with the same modules installed. - Conventions! - This module will naturally be following some [conventions](https://farmos.org/model/convention/), so maybe it’s an opportunity to [document them](https://farmos.discourse.group/t/documenting-conventions/1263) too. --- _[View the full topic](https://farmos.discourse.group/t/farmos-demo-records-module/2606)._