Cassini Request Naming Convention
 
Example A: (ISS prime)
ISS_027EN_GLOBAL002_PRIME

Example B: (VIMS rider to above ISS prime)
VIMS_027EN_GLOBAL002_ISS

Decoder Ring:
The name consists of up to four parts, each separated by an underscore:

1) Team designation This field is 3 to 5 characters long and is entered for you by CIMS based on your login account.

2) Orbit designation (three characters) concatenated with a two-letter target body designation  In the examples above, 027 refers to the 27th rev (orbit). In general, the targets are indicated by the first two letters of the feature's name. EN = Enceladus, TI = Titan, and SC = "spacecraft," a dummy target for SCO use.

3) A description of that particular observation, up to nine characters long, concatenated with the instance or iteration number of this particular observation (three characters long) In Examples A and B, GLOBAL002 refers to the second instance of a global view of the indicated target body (Enceladus in orbit 27). Another way of thinking of it is that the description may be up to twelve characters long and includes: a descriptive name of the observation (e.g. 2x2MOVIE); a single character to accommodate different versions of a basic observation (e.g., 2x2MOVIEA, 2X2MOVIEB); and the 3 digits which form an incremental counter to provide uniqueness (e.g., 2x2MOVIEA002).

4) Indicates this instrument is the prime or in the case of a rider reqeust, what instrument is prime. Example A shows that this ISS request is prime. Example B is the VIMS rider to the ISS observation; the fact that it is a rider and that ISS is the prime is indicated by "_ISS." The descriptions must match for primes and riders (e.g., GLOBAL002 is the same for both the ISS and VIMS examples).

Including the underscores, the name can be up to 30 characters long.

No special characters may be used, except for underscores which are used as delimiters only.

 
Note: In CAPS request names, the target and the prime/rider fields are not used consistently. In addition, the instance number is in the order requests were entered into the project's database and not in order of the times they will execute.