CALPADS error brief · IVR
IVR0009
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
1.10 - Student Legal First Name 1.11 - Student Legal Middle Name 1.12 - Student Legal Last NameRecommended correction path
Suggested resolution
Read the complete validation
CALPADS rule: The field may contain alphabetic letters, numbers, periods, hyphens, apostrophes, forward slashes, and spaces. Alphabetic characters with accents, tildes, or umlauts are allowed. Valid characters are based on CALPADS-supported UTF-8 standards.
Severity: Fatal Type: Input Validation
Fields validated:
- 1.10 Student Legal First Name
- 1.11 Student Legal Middle Name
- 1.12 Student Legal Last Name
The 28 printable ASCII punctuation characters that are prohibited
These are the ordinary visible ASCII punctuation marks outside the approved punctuation set. Each character is shown at approximately 36 points so it can be recognized rather than merely described.
The punctuation CALPADS does allow
Important: The displayed space symbol ␠ is only a visual label. The submitted value must contain an ordinary space, not that symbol and not a nonbreaking space.
Look-alikes that commonly fool the eye
| Looks like | Common invalid version | Approved replacement when accurate | Typical source |
|---|---|---|---|
| Apostrophe | ’ right curly quotation mark or ‘ left curly quotation mark | ' straight ASCII apostrophe | Word processors, websites, email, mobile keyboards, smart-punctuation settings. |
| Hyphen | – en dash, — em dash, or − minus sign | - ASCII hyphen-minus | Formatted documents, copied text, automatic typography. |
| Space | Nonbreaking, narrow, zero-width, tab, line-break, or other hidden spacing | Ordinary ASCII space | Web pages, PDFs, spreadsheets, imports, pasted text. |
| Quotation mark | ", “, or ” | Usually remove it after confirming the legal name; quotation marks are not in the approved set. | Nickname notation or copied registration data. |
| Accented letter | A detached accent/tilde/umlaut or an unsupported combining sequence | The correctly encoded supported alphabetic character, such as é, ñ, or ü | Legacy encodings, keyboard composition, copy/paste, interface conversion. |
Valid versus invalid name examples
| Submitted value | Finding | Action |
|---|---|---|
O'Connor | Valid straight apostrophe. | Retain when supported by the legal-name evidence. |
O’Connor | Curly apostrophe may look correct but is not the approved ASCII apostrophe. | Replace only the punctuation with '. |
García | Accented alphabetic character. | Retain when accurately encoded and supported. |
Peña | The tilde is part of the letter ñ. | Retain the supported alphabetic character. |
Smith-Jones | Valid ASCII hyphen-minus. | Retain when supported. |
Smith–Jones | Contains an en dash rather than a hyphen. | Replace the dash with - after confirming the name. |
María Elena | May contain a nonbreaking space that looks ordinary. | Replace it with a normal space. |
Robert (Bobby) | Parentheses are prohibited and a nickname may not belong in a legal-name field. | Confirm the legal name and store aliases only in an authorized field or local process. |
Choose the diagnostic pathway
- Inspect the rejected field literally
- Which of fields 1.10–1.12 was rejected?
- What exact character appears at each position?
- Does punctuation merely look like an approved apostrophe, hyphen, period, slash, or space?
- Does the value contain a nickname, note, placeholder, or annotation?
- Reveal hidden and nonprinting characters
- Compare the field in a plain-text editor that can show invisibles or Unicode values.
- Check for tabs, carriage returns, line feeds, nonbreaking spaces, and zero-width characters.
- Inspect the raw delimited row rather than relying only on the spreadsheet display.
- Confirm the file remains valid UTF-8 and the columns have not shifted.
- Trace where the character was introduced
- Does the authoritative SIS contain the same encoded character?
- Did a registration import, integration, spreadsheet, or extract transform it?
- Does smart punctuation automatically return after staff correct the name?
- Will the next export recreate the rejected character?
- Protect legitimate names and diacritics
- Does authoritative evidence support the spelling and diacritics?
- Is the accent, tilde, or umlaut part of the alphabetic letter rather than a detached mark?
- Can the SIS and extract preserve the supported UTF-8 character?
- Are staff changing only the incompatible encoding or punctuation?
Follow the character from evidence to CALPADS
- EvidenceConfirm the legal name.
- SISInspect the stored character.
- ExtractReveal the encoded value.
- CorrectRepair the first divergence.
- VerifyConfirm acceptance and identity.
Primary participants for this error
- Registrar or authorized student-records staff
- CALPADS coordinator
- SIS system owner
- Registration/import owner
- Extract, integration, or vendor support
Choose the owner from the evidence
- Name itself is wrong: authorized student-records staff.
- SIS stores smart punctuation: SIS configuration owner.
- Extract changes a valid name: integration or vendor owner.
- One-time pasted artifact: correct the source and check similar records.
Recommended correction path
Preserve the rejected evidence
Capture the submission ID, row, fields 1.10–1.12, raw file, and SIS values before editing.
Confirm the student and legal name
Use authorized cumulative-file or identity evidence so the correction preserves the student’s actual name.
Identify the exact code point
Inspect the literal text and reveal invisible characters; do not assume two marks that look alike are encoded alike.
Compare the approved character set
Retain supported letters and diacritics. Remove or accurately replace only unsupported punctuation, symbols, controls, or spacing.
Correct the first system that diverged
Repair the authoritative SIS, registration import, crosswalk, integration, or extract rule—not merely the rejected upload row.
Regenerate and inspect the raw file
Confirm UTF-8 output, approved punctuation, ordinary spaces, intact delimiters, and unchanged neighboring fields.
Resubmit and search for siblings
Verify IVR0009 clears, then identify other students processed through the same entry, import, or export pathway.
Before closing the issue
- Confirm the accepted value accurately represents the student’s legal name.
- Verify all three legal-name fields contain only supported characters.
- Confirm the SIS and regenerated file agree character-for-character.
- Document whether the defect originated in entry, copy/paste, import, encoding, or extract logic.
- Check other records produced through the same pathway.
Official SENR IVR0009 troubleshooting page | Current CALPADS system documents | UTF-8 Basic Latin reference | UTF-8 Latin-1 Supplement reference
IVR0009 participant directory
Engage only the roles needed to confirm the legal name, find the incompatible character, and correct the responsible system.
- Registrar or enrollment staff
- Authorized student-records staff
- CALPADS coordinator
- SIS or registration-system owner
- Extract, integration, or vendor support