Video Services may be known by many names over their lifetime. Every name commonly used in reference to the Video Service should be included in the EIDR record.
- Service Name: The primary, official, or most common name for the Video Service. This may not be in English and may not be in the Latin-1 alphabet. EIDR supports full Unicode characters in its text fields, so you can enter the name in its original form. NOTE: Each Service Name can only be used once in the Registry for a given Delivery Model (Linear, VOD, etc.). It cannot appear in another Video Service record as either a Service Name or Alternate Service Name.
- Alternate Resource Name: The additional names by which a Video Service is also known, including nicknames, abbreviation, obsolete names, and transliterations (for Service Names that are not presented in the Latin-1 alphabet). Include as many as are known, up to 10. NOTE: The same Alternate Resource Name may appear in more than one record, but it cannot appear more than once in the same record or also be used as a Service Name.
- Abbreviation: All names have an optional abbreviation attribute. Set this to “true” if the name is an abbreviation of a longer name. Record the longer name as an Alternate Resource Name. NOTE: If no value is provided, it is treated the same as if it were set to “false.”
When entering a name, follow these rules:
- Every name must be unique within the Video Service record. Do not repeat the Service Name in the list of Alternate Service Names.
- Video Service de-duplication keys off of the Service Name, so take particular care in its selection and presentation.
- The order of the Alternate Service Names does not affect discovery, but as a convenience to other users, if the Service Name is not in English or is presented in a non-Latin-1 alphabet, include an English or Latin-1 name as the first Alternate Service Name.
- Used mixed case (often called, “title case”). Standards for title capitalization vary by country (e.g., initial capital for all words other than articles and conjunctions; capitalize only the first word and any proper nouns). Use the standard appropriate to the Video Service’s home territory.
- Do not present names in all caps unless the name is an initialism or call sign (such as KNBC).
- Do not use trailing articles (“…, The” or “…, Les”).
- Do not include parentheticals or additional metadata in the name string unless it is a natural part of the name. All such information should be encoded in the appropriate field or included in the Description.
- The Registry will perform whitespace normalization. All non-space whitespace characters (tab, carriage return, non-breaking space, etc.) will be replaced with a space, consecutive spaces will be replaced with a single space, and leading and trailing spaces will be removed).
When EIDR evaluates a text field, it is case insensitive and punctuation is ignored. Capital and lowercase letters are equivalent. EIDR considers accented and un-accented characters identical. Thus, à, Ă, and ä are all the same as “a” and ß is the same as “ss.” The primary implication of this is that a name with accented characters or orthographic ligatures will be treated as identical to that title or name without them (and will be rejected as a duplicate by the Registry).
Record as many alternate identifiers with each EIDR record as are known, up to 10. Use the required Domain attribute to identify both the source and type of the ID.
The Description field is for additional information to assist human operators during discovery or manual de-duplication: it is not used in automated de-duplication. Include any useful information not specifically recorded elsewhere.
Use the Parent field to record the Video Service ID of the direct parent of the subject Video Service. This could be a Network/Affiliate relationship or a master channel/regional feed relationship. Use the Other Affiliations field to record all other associated Video Services or Companies (identified with EIDR Party IDs). These could be video feed providers or corporate owners.
These fields can repeat up to four times per Video Service. If the primary nature of a particular Video Service cannot be defined with a single value, generally because no one Format or Delivery Model dominates, then use them in combination.
 Even though such fields are case-insensitive, capitalization best practices still apply. Controlled vocabulary lists, such as Formats, are controlled by an XML schema. XML is a case-sensitive language, so capitalization does matter in such cases.
 Do not use typographic ligatures – those that are purely stylistic rather than linguistic – such as “ﬃ,” a single character that replaces the three-letter sequence “ffi.”