Stock language for mostly common emails sent regarding Sponsored NetIDs.
Tips and notes, mostly of value for Chemistry IT staff
- Preface "Business Reason" section's text with a summary, such as:
Hoffmann, FirstName LastName <NetID>. Prof. Roald Hoffmann:(...business reason...).
- For Scheraga's 29 Sponsored NetIDs we bulk-updated them in March 2017 using data munged within Excel. File located:
- R:\Chem IT\CCB people lists\Sponsored NetID uploads\Scheraga-Sponsored-NetIDs.xlsx
- See our page on creating a NetID, which is rarely done.
- CU's list of persons who are listed as Staff in the Directory but who no longer have active jobs at Cornell:
- If you do a Cornell people search for folks on this list, you will see under proxy (Other Information => PROXY:) that they are proxied by Dave Collum <dbc6> (current Chemistry Chair, as of 11/2016) or Michael Lenetsky (Oliver's supervisor, as of 11/2016).
- CIT will send an email to someone who was considered a student AND is now only a sponsored individual. That email states that their student status is dropping away, unaffecting their sponsored status. Thus, nothing should change for them.
- Why not use "GuestIDs" instead, usually? (There are exceptions: GuestIDs also listed here to ensure their review ~annually, triggered by Chemistry IT staff.)
- Not allowed: "Cornell GuestIDs are only issued to individuals who are not eligible for a Cornell NetID or Sponsored NetID." (grabbed 6/28/16)
- Often don't provide the access the faculty members intends to confer, such as Library access. "GuestIDs provide individuals with access to certain services that use central authentication."
- GuestID creation within Chemistry
- Not allowed: "Cornell GuestIDs are only issued to individuals who are not eligible for a Cornell NetID or Sponsored NetID." (grabbed 6/28/16)
Stock text for Sponsored NetID communications
Option 1: Create a ticket under the person with Sponsored NetID
- I've used this for when renewal is more likely.
Renewal request via our web form
Fill out form for person whose NetID is expiring. Then in Full Description, write something like:
Oliver reporting: This NetID is due to expire xx/yy/zzzz unless renewed by PI, to whom I'll write shortly.
Process: This creates a ticket to ensure PI's response is received and recorded. And proper action is taken on our part.
Option 2: Create a ticket under the PI sponsoring the NetID
- I've used this for when renewal is not as likely. Or for Scheraga where many renewals are under consideration.
Subject: Expiring Sponsored NetID: Firstname Lastname <NetID>
PIname,
The current sponsorship for Firstname Lastname <NetID> expires at the end of this month.
Do they require having their NetID re-extended? If so, for how long? Please reply so I may have a ticket created to record your response. Thank you.
Here's the language you used last time:
Firstname Lastname <NetID> (...).
I look forward to hearing from you. Thank you, -Oliver
Roald,
The current sponsorship for Thijs Stuyver <ts756> expires at the end of this month.
Do they require having their NetID re-extended? If so, for how long? Please reply so I may have a ticket created to record your response. Thank you.
Here's the language you used last time:
Thijs Stuyver was a graduate student (Belgium) visitor to my group until the end of July, with his own support. I write to request that we extend his NetID (ts756@cornell.edu) for a year beyond its normal expiration date at end of August. Thijs has a number of projects to finish, and these may be best accomplished on our computer cluster requiring an active NetID.
I look forward to hearing from you. Thank you, -Oliver