# Concepts

To use ScholarshipOwl For Business in an advanced manner, you need to get acquainted with several basic concepts.

# Scholarship

Scholarship instance is created right after a scholarship is published. A newly created scholarship instance acts as an id (GUID) that can be later used for API calls or webhooks.

Scholarship id example: 4424406d-36a5-11e9-aff3-7824afb64838

# Field

As different scholarships may require different information from students, we want our scholarships to be agile and configurable in different ways, so as to accept different kinds of data from a student's profile.

Each profile’s data chunk ( name, email, phone, etc. ) is called a field. Scholarship may have many configured fields. Each field must be included in the application's data when students apply for a scholarship.

Fields must be configurable within a scholarship provider’s interface when they create a new scholarship.

# Eligibility

Fields can also be configured with additional "conditions" – used for creating an automatic scholarship eligibility check.

For example: If a scholarship is eligible only for 18-year-old students, we should ask applicants for their birthdates; applications with the specified age below 18 will not be accepted.

# Requirement

A scholarship may require some additional information from a user, not just the profile data. Such information is called a requirement. There can be different types of requirements.

Requirements displayed on an application form with a different input depend on the requirement type. Scholarship requirements must be verified against their basic field validations and other validations, depending on configuration.

# Requirement Type

Depends on the information we want to get from students. We may use different types of input on an application form. Each requirement type has a different input type and may be displayed differently in review options, within a review application process.

# Recurrence

If a scholarship is repeatable and configured as such in Deadline configurations, a new scholarship will be created immediately after the previous scholarship instance’s deadline.

If you have a repeatable scholarship, you need to subscribe using one of the integrations to scholarship published and scholarship deadline events if you want to subscribe to scholarship application events.

# Application

When a scholarship becomes active (published), it starts accepting new applications. Upon the action of applying for the scholarship, if we have all the applicant’s data and it passed validation criteria, a new application is created. After the deadline, a scholarship manager needs to finish reviewing applications and run a winner draw.

# Application Status

If a scholarship has requirements, an application’s status is received and the application must be reviewed before it is accepted into the winner draw. The application can also be rejected.

In another case, if a scholarship doesn't have requirements, the application will automatically be assigned the accepted status; upon a scholarship deadline, a winner is chosen automatically.

• received - Application received and waiting review
• review - Application under review
• accepted - Application accepted and will be included in winner draw
• rejected - Application rejected

# Winner

After a scholarship deadline, we need to pick a scholarship winner from all the accepted applications.