Yeah, I like the specificity of "record_active" versus "is_active", which
can become overloaded/pinned by the system's semantics.  I've replaced the
flag on the two models and added to the other existing models as well.


On Wed, May 7, 2014 at 12:15 PM, David Ormsbee <notifications@github.com>wrote:

> In lms/djangoapps/api_manager/models.py:
>
> > @@ -79,12 +78,9 @@ class LinkedGroupRelationship(models.Model):
> >      to_group_relationship = models.ForeignKey(GroupRelationship,
> >                                                related_name="to_group_relationships",
> >                                                verbose_name="To Group")
> > -    record_active = models.BooleanField(default=True)
>
> There's nothing built in that I'm aware of. You could use StatusModel for
> something like this as well, if you need multiple kinds of status to filter
> by. But if it's just a binary on/off, then I'd stick with the flag. In
> CourseEnrollment, the flag is called is_active (that's the convention
> used by authuser). I can't think of other models where we have a binary
> active/inactive field.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/edx-solutions/edx-platform/pull/41/files#r12386442>
> .
>



-- 
Matthew Drayer
Solutions Architect
edX | MIT
mattdrayer@edx.org