How Los Angeles Music Publishers Reconcile Duplicate Song Works in Salesforce

Why Do Duplicate Song-Work Records Matter to Los Angeles Publishers?

In this anonymized composite scenario, a Los Angeles music publisher imports separate co-writer submissions into Salesforce and creates two catalog rows for one musical work. An illustrative 15,000-row review shows how the team checks work and writer identifiers, keeps distinct recordings and ownership claims visible, validates its catalog report, and protects approved field changes with preview, backup, bulk undo, and restore. This is not a named customer result.

Presenter illustrating duplicate musical works and distinct sound recordings
Illustrative visual: two source work rows may describe one composition with separate recordings.

Why Duplicate Work Metadata Is a Los Angeles Catalog Problem

The Mechanical Licensing Collective’s guidance on duplicate work registrations says potential duplicates generally share song-title, writer, publisher, ISWC, ownership-percentage, or recording metadata; it instructs members to report the applicable work titles and MLC song codes for review. Its Claiming Tool guidance gives a concrete failure mode: two co-writers may each register the same musical work and create duplicate work records, while ownership shares still need proper claims. These are national music-rights rules, not a count of duplicate Salesforce rows in California. Otis College’s April 2026 creative-economy report identifies Los Angeles County as a major center for film, television, sound, and creative professionals. That local industry context makes catalog handoffs pertinent here; the specific record-grain problem is the MLC’s one-work/two-registration issue, not the county’s job count.

Scenario integrity: This is an anonymized composite of music-publishing and Salesforce-admin workflows. The 15,000-row population, example identifiers, and images are illustrative, not a publisher testimonial. The MLC and the publisher, not ZaapIT, determine official work registration and ownership outcomes.

Use Case: Two Co-Writer Imports Create Two CRM Work Rows

A Los Angeles publisher keeps a custom Salesforce Musical Work catalog. A writer’s team sends a work title, writer IPI, and draft ownership share; a co-writer’s administrator later sends a similar title with a different local work number and a separate recording reference. An import keyed only on each sender’s local ID inserts two Musical Work rows. A catalog report now counts the composition twice, while a licensing coordinator sees conflicting ownership-share fields and cannot tell which row holds the current MLC song code.

The rights team checks the work title and alternatives, writer identities and IPIs, any ISWC, MLC song code, publisher administrator, work history, and approved share documentation. It distinguishes the musical work (composition) from each sound recording of that work. Two recordings can legitimately relate to one composition. The team also preserves competing or pending claims for authorized rights review rather than using a CRM merge to decide who owns a share.

Record grainUseful identifiersUnsafe shortcut
Musical work / compositionMLC song code, ISWC where available, verified title and writer setCount each co-writer’s local work number as a separate song.
Writer or publisher partyIPI and verified party nameMerge similar names without checking the party identifier.
Sound recordingRecording-level identifier and recording metadataCollapse distinct recordings into one work row or treat each recording as a new composition.
Ownership claimClaim source, effective date, share, and review stateOverwrite a disputed share with the latest import.
Presenter reviewing writer and recording metadata for a music catalog
Illustrative review: check work identity and writer evidence before changing catalog rows.

How the Admin Reviews and Corrects the Catalog

  1. Profile a bounded population. Review an illustrative 15,000 custom work rows with title variants, writer IPIs, publisher names, ISWC, MLC song code, local source IDs, linked recordings, share status, and import provenance. Capture the pre-change count of unique verified works and unresolved claims.
  2. Generate candidate matches. Use ZaapIT filtering and text normalization to find similar titles and writer sets, then group by trusted work identifiers where present. The MLC’s work-registration instructions tell members to search before registering, specifically to avoid duplicate work records. A title match alone is only a candidate: different songs can share a title.
  3. Review the source of truth. Rights staff compare MLC song codes, writer IPIs, registrations, and approved share documents. They link both inbound submissions to the one verified internal work only when evidence supports it. Separate recordings and open claim disputes remain visible.
  4. Preview and back up. Preview approved Salesforce field and relationship corrections, preserve the affected rows and old values, and test a small controlled batch. Use ZaapIT bulk undo and restore for the specific supported changes if validation finds an error. Do not assume that undoing a CRM field update reverses an external MLC filing.
  5. Prevent repeat imports. Map each source’s local work number to the verified internal work and, where available, the MLC song code. Quarantine conflicting share updates and have authorized rights staff resolve them before a new row or outward registration is created.

Salesforce’s duplicate-job considerations say duplicate jobs can run on custom objects but the native compare-and-merge action is not supported for those custom-object results. Its matching-rule documentation explains how to configure custom matching criteria. Those tools can help surface candidates; they cannot adjudicate copyright ownership. A reviewable catalog crosswalk and recovery path matter for this use case.

Validate Work Identity Without Losing Recordings or Claims

After each batch, re-run the same catalog report. Compare unique verified work counts, unresolved candidate groups, linked recording counts, and claims awaiting rights review. Sample matched title variants, same-title different-work exceptions, and multi-recording works. The number of distinct recordings must not fall merely because two internal work rows were reconciled. Confirm that outbound registration files use the correct MLC song code and that no draft share was silently promoted to an approved claim.

Test a supported bulk undo or restore on a small approved set of Salesforce changes, checking old values and links against the backup. Keep external MLC change requests in a separate tracked process. No royalty-recovery amount or improvement rate is asserted for this hypothetical workflow.

Presenter illustrating backup validation and restore for music catalog data
Illustrative recovery: preview, back up, validate, and test restore.

Make Music Catalog Cleanup Reviewable

Use ZaapIT to profile Salesforce work records, preview approved updates, preserve a backup, and test bulk undo and restore for supported changes while rights staff confirm the correct composition and claim history.

Frequently Asked Questions

Why can two co-writer submissions create duplicate musical-work rows?

Each sender may supply a different local work number or title variant. An import keyed only on the sender’s ID can create two CRM rows for the same composition.

Does a matching song title prove two records are the same work?

No. Compare verified writers and IPIs, work codes, registrations, and supporting metadata. Different works can share a title.

Should separate sound recordings be merged when a work row is reconciled?

No. One composition can have multiple legitimate recordings. Preserve their recording-level identities and links to the verified work.

Can a Salesforce bulk undo reverse an MLC registration change?

No. Test bulk undo or restore for supported Salesforce changes, and manage external registration corrections through the MLC’s separate process.

Useful ZaapIT Resources

Sources