The following naming conventions for resources on the calendar server have been created to make it easier for users to locate
the resources they need to include in their meeting proposals.
Locations:
Room names must be prefixed with a building name followed by
a room number, a descriptive label for the location, plus a tag
indicating what type of room it is. For example, a conference
room in 208a CCC would be labeled "CCC 208a Conf Rm". Where we
have buildings without formal names, we use the street address.
For example, Environmental Health & Safety has a conference
room in a building located at 201 Palm Road. The resource name for this room is
"Palm Rd 201 Conf Rm". The folks at 120 Maple Ave will have
conference rooms whose names begin with "Maple Ave 120".
Non-location resources:
Anything else that can be scheduled but does not represent a
location follows a naming convention that associates the
resource with the organizational unit to which it belongs. The
name begins with the org unit label from the OU1, OU2 or OU3 field
(whichever provides the more specific usable association). The
resource owner determines the remainder of the name. For
example, the Planning, Design, and Construction unit in AFF has
two IBM ThinkPad laptops that are schedulable resources. They
are labeled as "PDC ThinkPad 380" and "PDC ThinkPad 365", where
"PDC" comes from their OU2 field label.
A big constraint on naming is that there are only 31
characters available. The conventions above will be creatively
violated to accommodate this constraint while maintaining an
aesthetically pleasing resource name.
Resources are configured, by default, to allow booking on a first come/first server basis. If you would like a resource to allow for doublebookings - multiple events at the same time - please indicate this in your request. In addition if you would like approval requests to be sent to the person in your department who manages a calendar that allows for double booking, please include this persons name and email address with your account creation request.
Resource creation requests must be sent to ecalendar@cornell.edu
in the following format.
Resource data entry format:
Resource Name OU1 OU2 OU3
There are three different types of groups:
Private - can only be used by the user who
created the group.
Members Only - can only be used by the group
members.
Public Groups - are accessible by everyone on the
server.
The following naming convention is recommended when the creation of a public
group is necessary. The descriptive name of the group must be prefixed by
name of the department owning the group. For example, "CIT Conference Rooms".
Requests for the creation of public groups owned by the System Administrator
should be sent to the Oracle
Calendar System Administrator. All public groups will be owned by the
system administrator or by the unit account administrator.
Who owns a group once it has been created on the calendar
server?
When a group is created the owner of the group is the one
who created it. The owner is the
only person who can change or delete a group. The one draw back
to this is that when this person's account is deleted from the
server all of the groups owned by this person are automatically
deleted. It is possible to transfer groups from one user account to another, but this must be done before the group owners account is deleted and with the permission of the account owner if they are still employed by the university.
