It is the University's intent that the following persons be eligible for Dormnet subscriptions:
The Host Database determines this eligibility by looking for the customer's netid in the Campus Directory (a.k.a. "LDAP"). A University netid (referred to as a uid in LDAP) is eligible for Dormnet based upon fields in the LDAP entry:
This Dormnet business rule is intended to extend Dormnet eligibility for a short time for undergraduate students who graduate in late May/early June.
Undergraduate alumni accounts are typically locked by OIT some number of days after the student graduates. See Accounts: When will my OIT accounts close and my e-mail address be removed?.
This Dorment businesss rule is intended to extend Dormnet eligibility for a short time for graduate students who graduate in late May/early June.
Graduate alumni accounts are typically locked by OIT some number of days after the student graduates. See Accounts: When will my OIT accounts close and my e-mail address be removed?.
That includes, for example, other undergraduate and graduate students who are not presently-enrolled, other Degree Candidacy Continuing (DCC) students, faculty, staff, and casual employees. A customer whose netid is no longer in LDAP also is not eligible for Dormnet.
The customer's entry in the Campus Directory (LDAP) also must meet consistency checks. Presently these checks include, for example:
(To be eligible for a Dormnet subscription, the uid must additionally meet a stricter requirement: the value must be composed of one or more characters from the set: lowercase alphabetic characters, digits.)
Although the Host Database will provision Dormnet service even when the mail field is missing or contains a value other than firstname.lastname@example.org (where uid is the value above), in such circumstances it is possible that email to this customer regarding Host Database transactions and regarding the use/abuse/misuse/malfunction of the customer's Dormnet subscriptions will not reach the intended customer.
The Host Database will provision Dormnet service regardless of whether the entry has a password, and the Host Database does not expect to be able to read that password from LDAP. However, the lack of a password will prevent the customer from using the Host Database web interface to subscribe to Dormnet, change a Dormnet subscription, or unsubscribe from Dormnet.
When a customer's eligibility for Dormnet ends, each of the customer's Dormnet subscriptions ends automatically.
At that time, the Host Database automatically removes each Host Database registered as a Dormnet subscription for that customer. This includes both entries that are presently-subscribed and those not presently-subscribed.
No notification is sent to the customer when this happens. This is because the information is rarely of any interest to the customer. (Many students graduate every year, and each typically has several Dormnet subscriptions. When a student graduates or otherwise leaves the University or loses his/her student status, a variety of University systems and services are updated to reflect the event. In the vast majority of cases, notifying each former student that each such University system (such as the Host Database) has been updated likely would not be helpful.
Andy other Host Database entries affiliated with that customer registered as office entries (not Dormnet subscriptions) are not removed.