Add scope view for GradingSurveyGroup and set access checks.
The access checks are now properly set for create, edit and show. To facilitate the scope view the access check have an extra check built in to ensure that a scope is actually present before cheking for an existing Program.
indexes:
# used to list proposal in descending order of their score
- kind: StudentProposal
properties:
- name: org
- name: status
- name: score
direction: desc
# used to list reviews in ascending order of date
- kind: Review
properties:
- name: is_public
- name: scope
- name: created
# used to determine which orgs have more then 0 slots assigned.
- kind: Organization
properties:
- name: scope
- name: status
- name: slots
# used to order accepted orgs
- kind: Organization
properties:
- name: scope
- name: status
- name: name
# used to determine which proposals have a mentor assigned
- kind: StudentProposal
properties:
- name: org
- name: status
- name: mentor
# used to determine which proposals will be accepted
- kind: StudentProposal
properties:
- name: org
- name: status
- name: __key__
# used for the bulk mailing of students
- kind: Student
properties:
- name: scope
- name: __key__
# used for the cron system
- kind: Job
properties:
- name: priority_group
- name: status
- name: __key__
# used for bulk mailing student and mentors with survey reminders
- kind: StudentProject
properties:
- name: program
- name: status
- name: __key__
# AUTOGENERATED
# This index.yaml is automatically updated whenever the dev_appserver
# detects that a new type of query is run. If you want to manage the
# index.yaml file manually, remove the above marker line (the line
# saying "# AUTOGENERATED"). If you want to manage some indexes
# manually, move them above the marker line. The index.yaml file is
# automatically uploaded to the admin console when you next deploy
# your application using appcfg.py.