Opened 14 years ago

Closed 14 years ago

#30 closed enhancement (fixed)

Create data migration for activity categories

Reported by: adehnert Owned by:
Priority: minor Milestone: Sometime
Component: Core Version:
Keywords: initial data Cc:
Size:

Description

The activity categories are currently created by the util/import_categories.py script, which is sorta stupid and basically static. This should be converted to a data migration, which will help ensure they exist before util/import_db.py gets run for the first time on a new install.

Change History (1)

comment:1 Changed 14 years ago by adehnert

  • Resolution set to fixed
  • Status changed from new to closed

Progress:

commit 1207e05f4dd63583df4637f072ef8591e2f5ae31
Author: Alex Dehnert <adehnert@mit.edu>
Date:   Mon Dec 12 00:23:27 2011 -0500

    Use fixtures for categories, and track changes
    
    * Remove the old import_categories.py script, and associated
      legacy-categories.txt file
    * Add fixtures for:
        * Creating the groups.ActivityCategory objects (formerly the role of the
          import_categories.py script, see above)
        * Creating the forms.FYSMCategory objects (formerly done by hand)
    * Diff those fixtures in the diff_static_data.sh script
    
    This partially fixes Trac #29 and fixes Trac #30.
Version 0, edited 14 years ago by adehnert (next)
Note: See TracTickets for help on using tickets.