invisec's profile

19 Messages

 • 

462 Points

Tuesday, September 8th, 2026

Solved

Data Query / Incomplete Reversion Loop: Non-standard hyphen syntax across departments on Agent from Above

Good Day.

Category:
Data / Credits Contribution

Problem Statement: I am requesting staff review regarding recent, incomplete credit syntax reversions on Agent from Above that have left the page in an inconsistent state.

To preserve departmental categorization (preventing legitimate VFX and Animation credits from being misrouted to Additional Crew or other incorrect departments), specific on-screen sub-descriptors (e.g., visual effects cooperation, animated sequence) and vendor company names are included in the occupational field.

Per IMDb contribution standards, nested roles, sub-descriptors, and company affiliations must be separated using colon delimiters (:). Recent edits have partially overwritten standard entries with free-form hyphens (-), leaving a mix of both formats active on the live page.

Evidence of Inconsistent Formatting:

Visual Effects Department (Partial Revert):
- Reverted Entry: on-set vfx: visual effects cooperation - Whitedeer Animation CO., LTD.
- Unmodified Standard Entry: it: visual effects cooperation: Whitedeer Animation CO., LTD.


Animation Department (Reverted):

- Reverted Entry: director: animated sequence - Chimney Animation

- Standard IMDb Syntax: director: animated sequence: Chimney Animation

Questions & Requests for IMDb Staff:

  1. Formatting Confirmation: Can staff confirm that nested sub-descriptors and company affiliations within occupational titles must strictly use colon delimiters (role: sub-descriptor: Company Name) rather than hyphens?

  2. Batch Data Correction & Guidance: Can an editor review the recent submission history for Agent from Above, restore the standard colon-delimited syntax across affected departments, and confirm this standard so subsequent episode additions remain aligned?

Thank You.
    

Oldest First
Selected Oldest First

Champion

 • 

16.9K Messages

 • 

357.4K Points

1 hour ago

I think the hyphens are now preferred, though it is not stated in a guideline. It is mentioned in the reply to my post below.

The colon (:) separates the role (prefix) from the qualifier (suffix). Only one colon is permitted per job title. Any second colon in the suffix becomes -

https://community-imdb.sprinklr.com/conversations/data-issues-policy-discussions/occupations/6a1ac23357c3ac7486a03c8c

19 Messages

 • 

462 Points

@Peter_pbn​ ... Thanks for chiming in and sharing that link, Peter!

The replies from Col Needham in that thread are definitely eye-openers - it’s amazing how much structural house style exists in those replies that never quite makes it into the public help guides!

The interesting edge case here is that Col Needham’s example of (role: sub-role - detail) covers nested job titles, whereas in my case, that third segment is a vendor company name (role: sub-descriptor - Company).

If the intent is for all secondary delimiters in the suffix, including company affiliations, to flatten into a hyphen, then (role: sub-descriptor - Company) is clearly the target.

I’ll keep an eye out for official staff confirmation on this thread just to be 100% certain company names follow the exact same flattening rule as sub-roles. Either way, having Col Needham's broad single-colon framework gives a much clearer direction for submitting the rest of these episode credits uniformly.