farmOS Demo Records Module

Development
2

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 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!