Difference between revisions of "StarRez"
Robert Pekor (talk | contribs) m |
|||
Line 5: | Line 5: | ||
Data feeds are provided from Banner for door access codes, demographic information and enrollment (housing eligibility) information. | Data feeds are provided from Banner for door access codes, demographic information and enrollment (housing eligibility) information. | ||
− | A data download from StarRez | + | A data download from StarRez to Banner is available as a job submission process in Banner. This process will push StarRez room assignments into Banner for use by the Active Directory feed, Facility Commander feed and Banner Room Key management forms. |
'''When will demographic data be loaded?''' | '''When will demographic data be loaded?''' | ||
− | Right now, demographic data will be loaded once a day at 1:00 am ET. | + | - Right now, demographic data will be loaded once a day at 1:00 am ET. |
'''How is the student demographic data population determined?''' | '''How is the student demographic data population determined?''' | ||
− | We use the SYBISTU table as the basis for the demographic data population. It feeds from the baseline Banner student table, but incorporates other datapoints useful for this load. | + | - We use the SYBISTU table as the basis for the demographic data population. It feeds from |
+ | the baseline Banner student table, but incorporates other datapoints useful for this load. | ||
'''SYBISTU/SGBSTDN is term-based. What terms are you using to pull records from SYBISTU?''' | '''SYBISTU/SGBSTDN is term-based. What terms are you using to pull records from SYBISTU?''' | ||
Line 35: | Line 36: | ||
==='''Demographic data push from Banner to StarRez''' === | ==='''Demographic data push from Banner to StarRez''' === | ||
− | '''Persons are inserted or updated by | + | '''Persons are inserted or updated by an API (application programming interface) push process using Banner data. ''' |
'''We do not delete persons from StarRez.''' The Housing office must purge person records as needed. | '''We do not delete persons from StarRez.''' The Housing office must purge person records as needed. | ||
Line 56: | Line 57: | ||
| TAs (Teaching Assistants) || Employee class = 28 || | | TAs (Teaching Assistants) || Employee class = 28 || | ||
|- | |- | ||
− | | CRDs (Commons Resident Directors) || | + | | CRDs (Commons Resident Directors) || Job Titles starting with Common Res* or CRA* || Example |
|- | |- | ||
| Summer Student Employees || N/A || Summer Student Employees will already be loaded into StarRez as students. | | Summer Student Employees || N/A || Summer Student Employees will already be loaded into StarRez as students. | ||
Line 62: | Line 63: | ||
| Language School Faculty || Faculty member actively employed by Language Schools and working on the Middlebury Campus || | | Language School Faculty || Faculty member actively employed by Language Schools and working on the Middlebury Campus || | ||
|- | |- | ||
− | | Language School Staff || | + | | Language School Staff || Staff member actively employed by Language Schools and working on the Middlebury Campus || |
|} | |} | ||
[[Category:StarRez]] | [[Category:StarRez]] |
Revision as of 13:30, 11 April 2017
Overview
StarRez provides the ability to manage and assign housing stock.
Data feeds are provided from Banner for door access codes, demographic information and enrollment (housing eligibility) information.
A data download from StarRez to Banner is available as a job submission process in Banner. This process will push StarRez room assignments into Banner for use by the Active Directory feed, Facility Commander feed and Banner Room Key management forms.
When will demographic data be loaded?
- Right now, demographic data will be loaded once a day at 1:00 am ET.
How is the student demographic data population determined?
- We use the SYBISTU table as the basis for the demographic data population. It feeds from the baseline Banner student table, but incorporates other datapoints useful for this load.
SYBISTU/SGBSTDN is term-based. What terms are you using to pull records from SYBISTU?
Housing business processes require future term data to assign housing. We use the following calculation to pick up students in future terms.
Current Term | Terms used in student demographic pull |
---|---|
Fall (90) | Fall (90), Winter (10), Spring (20) |
Winter (10) | Winter (10), Spring (20), Summer+ (50, 60, 65) |
Spring (20) | Spring (20), Summer+ (50, 60, 65), Fall (90) |
Summer (60) | Summer+ (50, 60, 65), Fall (90), Winter (10) |
Demographic data push from Banner to StarRez
Persons are inserted or updated by an API (application programming interface) push process using Banner data.
We do not delete persons from StarRez. The Housing office must purge person records as needed.
The concept of a population is to pull in everyone who could be housed.
Population Group Name | Business Rules | Notes |
---|---|---|
Students (Undergraduate, Language Schools, School of Environment, Summer Study) |
Active Student record in Sybistu and
|
|
Non-enrolled DMLs (Doctorate of Modern Languages) | Sybistu record exists for a summer term (ends in 60) with Student Type code = V (Visiting) and Student Status code = NE (Not Enrolled) | |
Long-term Housing Guests | Spriden name type = HGST (Housing Guest) | Spouses or dependents of language school faculty/staff, but may be other guests as well. |
TAs (Teaching Assistants) | Employee class = 28 | |
CRDs (Commons Resident Directors) | Job Titles starting with Common Res* or CRA* | Example |
Summer Student Employees | N/A | Summer Student Employees will already be loaded into StarRez as students. |
Language School Faculty | Faculty member actively employed by Language Schools and working on the Middlebury Campus | |
Language School Staff | Staff member actively employed by Language Schools and working on the Middlebury Campus |
- This page was last edited on 11 April 2017, at 13:30.
- Privacy policy
- About Library & ITS Wiki
- Disclaimers