Scope attribute for events

[fgregg]

Right now, the Event model in opencivicdata-django requires a jurisdiction attribute.

This is so that all events related to particular legislature can be easily grouped together.

However, not all the things that we want to model within the wider OCD world have jurisdictions, i.e, Election days.

I would like to propose that OCD Events have an scope attribute that can be a jurisdiction_id, division_id or None.

This would allow for current pupa practice to be largely unchanged, but also allow for events that are not associated with jurisdictions.

I don't love the name scope.

Thoughts? @jamesturk @gordonje @jpmckinney

[jpmckinney]

Why not have jurisdiction_id and division_id attributes, and the code will determine the 'scope' based on those values?

[jamesturk]

I think that's what the implementation would look like, but in general in favor of the idea.

…

On Thu, Mar 16, 2017 at 6:17 PM, James McKinney ***@***.***> wrote: Why not have jurisdiction_id and division_id attributes, and the code will determine the 'scope' based on those values? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#84 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAfYp_00wXz1qTgLBO1G6BSZM9l-ixTks5rmbUNgaJpZM4Mf8pX> .

[fgregg]

Okay. Does this require an OCDEP?

[gordonje]

I am down with this. I can make changes to the elections spec and my drafts of those models in python-opencivicdata-django once this is decided.