Frozen data: we currently have our application cycle open for the 19-20 aid year. However, we will still be awarding from the 18-19 opportunities for the current academic year. As a result, we have had to freeze data using the import offset for 18-19 opportunities so that the application answers within the opportunities do not get overwritten. However, this has also stopped new import data coming from Banner into 18-19 opportunities. This is a major issue. Our institutional policy requires students to be eligible for an award at the time of awarding. As a result, we cannot award solely based on frozen data. I could imagine two ways to address this issue:

o   1.) Allow the import offset to only affect application answers and not imported data,

o   2.) Allow opportunities to be associated with a specific instance of a general or conditional application. That is, associate an opportunity with the 18-19 version of the General Application instead of simply the General Application. Since the answers are archived for the previous version of the application (i.e. the 18-19 version), those should not change within the opportunity. We could then import fresh data from Banner within the opportunity and not use the import offset at all.

The delineation is between opportunities within a portfolio and scopes do not play a role. We already have a lot of scopes (one per department), and adding more scopes to denote an open vs. closed portfolio instance may be too much for our department admins to track.