NoodleBus Admissions

Noodle Bus Admissions

The Admissions Core

The Admissions Core is the central component in the NoodleBus for all the recruiting and admissions related connectors. All the connectors pass through the central core to:

  • Standardize the data and manage the client’s translations and configurations
  • Manage the routing of the data to other systems
  • Monitor and report on the transaction statuses
  • Relay information to supported analytics platforms

 

Admissions Core Connectors

The Admissions Core is designed with standard API connectors to handle data that needs to flow between:

  • Student Information Systems (SIS)
  • Enrollment CRMs
  • Lead Generation Systems
  • Application Systems
  • Recruiting and Admissions Coaching Systems
  • Document Imaging Systems (ECM – Enterprise Content Management)
  • Enrollment Analytics Systems (such as Noodles Analytics for OPM)

 

API Documentation:

 

 Admissions Architecture:

 

 Admissions Transactions (overview)

  • /Admissions/All

The set of admissions transactions for post, get, and push are designed to include the full set of all admissions objects and fields. This is used as a mass API to create or update a batch of records with a specific individual and ANY of their related admissions data. The list of data objects included in these transactions are:  Person, Person Alternate IDs, Person Address, Person Phone, Person Email, Prospect, Applicant, Application, Source, Activity, Rating, Checklist Items, Financial Aid, Education, Credentials, Test Scores, Relation, Relation Address, Relation Email, Relation Phone, Events

Admissions API (Draft)

Sample Flat-File Format

 

  • /Prospects

The set of Prospect transactions for post, get, and push are designed to include objects and fields related to the recruiting lead. This is used as a method to create or update a batch of records with specific individuals and their contact information, recruiting/coaching rep, lead source, ratings, and other related specifically to recruiting. The list of data objects included in these transactions are:   Person, Person Address, Person Phone, Person Email, Prospect, Source, Rating

Admissions API (Draft)

Sample CSV Format (Available soon)

 

  • /Activity

The set of Activity transactions for post, get, and push are designed to include objects and fields related to the recruiting activity (coaching or recruiting rep interactions with the prospect). This is used as a method to create or update a batch of records with specific individuals and their recruiting activity. The list of data objects included in these transactions are:  Person, Prospect, Activity

Admissions API (Draft)

Sample CSV Format (Available soon)

 

  • /Applications

The set of application transactions for post, get, and push are designed to include objects and fields related to an application. This is used as a method to create or update a batch of records with specific individuals and their application data. The list of data objects included in these transactions are:  Person, Person Alternate IDs, Person Address, Person Phone, Person Email, Prospect, Applicant, Application, Source, Financial Aid, Education, Credentials, Test Scores, Relation, Relation Address, Relation Email, Relation Phone

Admissions API (Draft)

Sample CSV Format (Available soon)

 

  • /Checklists

The set of Checklist transactions for post, get, and push are designed to include objects and fields related to an applications checklist of received documents and completed activities. This is used as a method to create or update a batch of records with specific individuals and their application checklist data. The list of data objects included in these transactions are:  Person, Applicant, Application, Checklist Items

Admissions API (Draft)

Sample CSV Format (Available soon)

 

Admissions Core DataBase ERD:

 

Admissions Core Object Descriptions

  • Person: Primary Object. Mostly Demographic data.
    • Person Alternate IDs: Person's Alternate IDs with Agencies.
    • Person Address: Person's Addresses with type
    • Person Phone: Person's Phones with type
    • Person Email: Person's Emails with Type
    • Education: Person's Educational History (Per institution)
      • Credentials: Academic Credentials for Person at institutions
    • Test Scores: Test Scores for Person
    • Relation: Person's related Family Members
      • Relation Address: Addresses for each relation
      • Relation Email: Emails for each relation
      • Relation Phone: Phones for each relation
    • Prospect: Lead/Prospect data for Person
      • Program Interests: Specific Program/Start (term or date)
      • Source: Lead Source information for Prospect and, optionally, program interest.
      • Activity: Lead contact activity by recruiter or coach for Prospect and, optionally, program interest.
      • Rating: List of recruiting ratings with different rating types for Prospect and, optionally, program interest.
      • Events: Event Registrations
    • Applicant: Applicant Data for Person (1 to 1 with prospect)
      • Application: Application Data for Person/Applicant
        • Checklist Items: List of application checklist items with Status Related to: Application Relation Type: Multiple
        • Financial Aid: Financial Aid Award information Related to: Application Relation Type: Multiple
    • Extra Object: Extra Object(s) for Custom Data
    • Batch Transaction: Transaction Object for entire Batch (all records)
    • Item Transaction: Transaction Object for single Item (each record in primary object)
    • Transaction Data: Standard object used by every object to store transaction statuses and Routing Details.