ISNI for Independent Publishers: A Practical Contributor-Identification Guide

1. What BISG recommended in October 2026

On October 27, 2026, the Book Industry Study Group announced Recommended Practices for Assigning ISNI. Its announcement identifies six priorities: check and obtain identifiers early; cover new and older titles; involve self-publishing platforms; have metadata recipients flag gaps; draw on library expertise; and communicate identifiers through ONIX. BISG describes the recommendations as a living document. [1]

Source distinction: The six priorities above are verified against BISG’s official announcement. The linked Knowledge Center report and companion resource were not accessible during this review. The procedures, examples, register design, and rollout below are Publishing Standards’ implementation recommendations, not quotations from or a claim to have inspected the complete report.

Recommendations are different from submission requirements

The announcement is not evidence of a new universal obligation to obtain ISNIs before publishing. A retailer, distributor, library service, or contract may impose its own requirements. Check that recipient’s current documentation and agreement before treating a field as mandatory.

Maintain three separate labels in the production checklist: industry recommendation, house procedure, and recipient requirement. For a recipient requirement, retain its source, effective date, and the affected channel. A publisher can adopt an early lookup procedure without declaring every missing identifier a release blocker. Do not describe this announcement as a new Amazon KDP, IngramSpark, or other platform mandate.

2. What ISNI identifies, and what it does not

ISNI is an ISO 27729 identifier for public identities involved in creative content. It can identify people, organizations, and publicly used creative identities. It is not a book number, a copyright registration, a contract, or proof that a particular party controls a work’s rights. [2]

The International ISBN Agency explains that different product forms require separate identification. ORCID provides a persistent individual identifier and a researcher-controlled record. A person may have both ORCID and ISNI; keep the identifier type attached to each value. Similar-looking numbers do not make the identifiers interchangeable. [3] [4] [5]

When another identifier may be useful

Consider an additional identifier when it addresses a specific identity or distribution need. A scholarly author may use ORCID for research workflows while an ISNI supports book-trade identity matching. A publisher or imprint may benefit from its own organizational identification when partners support it. A separately used pen name may need a separate public-identity record. These are decisions about the entity being identified, not purchases to repeat with every format.

Bowker’s guidance distinguishes separate pseudonymous identities from spelling, presentation, and transliteration variants of the same identity. Links between pseudonymous identities require authorization. [2] Ask the registration agency about an uncertain case before applying. A new website, cover, imprint assignment, series, or distribution account alone does not establish that a new contributor identity is needed.

Do not obtain an ORCID merely to fill an ISNI field. Do not obtain an ISNI for every domain the company owns. Choose identifiers according to the actual public identity, its work, and the systems that will use the record.

3. Check existing identifiers before applying

Make lookup an assigned editorial task. A contributor’s statement that they have never applied is useful background, but it is not a substitute for checking available records.

1. Collect the public credit. Ask for the exact name intended for publication, known public name variants, a relevant professional page, representative works, and any existing identifier links. Discuss pen-name boundaries privately. Do not put contract names or private contact details into a public export automatically.
2. Search the ISNI database. Start from the ISNI International Agency website and its database search. Search the credit as written, then useful initials, earlier public names, or spelling variants. MVB specifically advises checking for an existing record before registration. [6]
3. Open candidate records. A matching name is not enough. Compare associated titles, subject area, organizations, and public links. Use more than one meaningful point of agreement when available. Treat a conflicting work as a reason to investigate.
4. Ask the contributor to review ambiguity. Present the candidate and supporting evidence. If two people share a name, do not choose the first search result or the most complete biography.
5. Record the outcome. Use statuses such as verified existing record, no match found, ambiguous, application pending, or correction pending. Record the search date and evidence even when no identifier is selected.
6. Approve before exporting. Give one person authority to change the accepted identity mapping. An unresolved candidate stays out of outgoing identifier fields until resolved.

If there is no reliable match

Use an ISNI registration agency. Bowker and MVB offer registration routes. Confirm eligibility, required evidence, current fees, submission permissions, and correction support directly with the chosen agency. [7] [6] Ask who will submit and pay, and record that agreement.

MVB’s published guidance asks for a name, a publication title, and an additional distinguishing attribute, with requirements depending on the case. It also addresses permission to publish submitted information. [6] Treat these as that service’s instructions, not a universal form specification. If the debut title is not sufficiently established for the chosen process, ask the agency when to submit rather than inventing a publication history.

Keep one application reference per public identity. Before submitting, check whether the author, agent, another imprint, or a platform has already started an application. An application confirmation is not an assigned ISNI. Update the register only when the assignment and identity match have been checked.

4. Keep one contributor register across all imprints

A small company does not need separate identity systems for each imprint. It needs one controlled contributor list and a way to associate each contributor with the correct product and role. Start with three connected tables in an existing workbook or database. The downloadable CSV templates implement this proposed structure.

Download the contributor-register CSV templates for contributors, products, credits, organizations, and correction tracking. Import identifier columns as text to preserve their values.

Keep publisher and imprint records in a small supporting organization table. Record the public name, entity type, parent relationship where appropriate, and a verified organizational identifier if one exists. Do not place the company’s identifier in the author’s row.

Storage rule: Store identifier values as text. Preserve leading zeros and any permitted terminal X. Bowker describes ISNI as 16 characters including its check character. [2] Keep an ORCID in its full URI form in the master record, following ORCID’s storage guidance; let the export transform it for a recipient’s ONIX field. [5] A spreadsheet must not silently convert identifiers into numbers or scientific notation.

Example: one author, two imprints

In a proposed MTDLN Media workflow, Earnest Sherrill has one local public-identity key for books credited under that name. A writing-prompt title under Black Anvil Books points to that key. A later instructional title under another approved imprint can point to the same key. Each product keeps its own ISBN, format, and imprint assignment. A verified ISNI, if one is found or obtained, belongs to the shared identity record and can be reused with the appropriate credits.

This example does not assert that Earnest Sherrill or any MTDLN imprint already has an ISNI. It illustrates how one identity can connect several products without copying biographies and identifier decisions into separate registers.

Example: an external author project

For an author project such as Dr. R. Tyrone Jackson’s, keep the author’s public identity separate from the publisher-of-record and the service provider preparing files. A production-services relationship does not make the service provider the author or transfer the publisher identity. Verify the approved public credit against the project’s title page and contributor instructions, then attach the correct identity to each product.

Example: pen names and organizational brands

Suppose a fictional press uses two public brands and one writer uses a separate pen name. Give the brands and public contributor identities distinct local keys where appropriate, even before any ISNI application. Keep confidential relationships in a restricted administrative record. Ask the agency how the identities should be represented. Never export a legal-name connection simply because production staff know it.

The test is whether the register explains who is publicly credited, which organization publishes the product, and which evidence supports each identity. Website ownership and private business relationships should not be mistaken for public contributor credits.

5. Make identity checking part of frontlist and edition control

At commissioning or manuscript acceptance, create or reuse the local identity key, confirm the public credit, and check identifiers. Before metadata delivery, approve the product’s actual contributors and roles. Before release, compare outgoing credits with the title page. After release, check a sample of downstream records.

A later edition starts from the previous product record, but it still needs a credit review. Ask who actually contributed to this edition. A new translator, illustrator, narrator, or editor gets their own contributor identity and appropriate credit. Do not attach an earlier translator’s identifier to a new translator merely because the source title is unchanged.

A different format usually does not create a different identity for the same author. It can change the credit roster. An audiobook may add a narrator, while a revised illustrated edition may add an illustrator. The identifier follows the verified identity; the product record describes this edition and format; the credit record describes the contribution.

OCLC’s ONIX guidance supports identifiable, ordered contributor entries and names that match the product, including translator credits where appropriate. [8] If the printed credit differs from the preferred public name in the register, retain both values and document why. Correct mistaken attribution without silently rewriting a historical title-page credit to match a new marketing preference.

For a repeat author, the production question becomes, “Does this book use the approved identity, and are its credits correct?” That is a short check. It should not become a new registration exercise.

6. Reconcile the backlist without creating new identity errors

Start with active titles, relaunches, translations, contributors with common names, and known attribution problems. A publisher with limited time can work through ten products at a time. The batch size is a house choice, not an industry threshold.

1. Export the current records. Include product keys, ISBNs, edition and language, contributor names and roles, existing identifiers, imprint, and destination channels. Keep a dated baseline.
2. Group candidate identities. Use names and identifier values to find possible matches, then review them. A shared surname is a search aid, not a merge instruction.
3. Check the underlying publications. Compare title pages and reliable records. Separate missing identifiers from incorrect credits, outdated biographies, and product-linking problems.
4. Choose the authoritative mapping. Record the identity decision, supporting evidence, reviewer, affected products, and any uncertainty. Resolve the source record before changing destinations.
5. Send targeted corrections. Use the recipient’s accepted update method. Include affected ISBNs and record references so support staff can locate the exact products.
6. Verify results. Record delivery, acceptance, and the observed outcome separately. A successful upload does not prove that every downstream system used the identifier.

Distinguish a duplicate from a mixed record

Two records that describe the same identity may be duplicates. One record containing works by two different people is a mixed record. They require different corrections. Do not solve either problem by applying for yet another identifier.

Submit the conflicting identifiers, record links, affected works, and proposed correction through the agency or the record’s correction mechanism. Bowker describes review by the ISNI Quality Team and explains that merged records can retain a deprecated identifier pointing to the resulting record. [2] Let the responsible authority resolve the registry record; keep the confirmed outcome and any superseded value in the local audit history.

After a confirmed merge or split, identify every affected product and channel. A registry correction alone does not prove that a distributor’s stored feed, a retailer’s author page, and the publisher’s own catalog have all updated.

Use librarians for hard cases

A library cataloger or authority specialist may help distinguish people with similar names and evaluate established name forms. Bring specific evidence and a clear question: which of these works belongs to this person, and which records appear to conflict? Do not assume a local library offers an ISNI registration service, guarantees a correction, or can override a commercial distributor’s records. Confirm the scope of help available.

Keep unresolved cases visible. “No match found” is different from “verified absent,” and “correction sent” is different from “correction accepted.” Those distinctions stop uncertain work from becoming a falsely complete record.

7. Communicate ISNI through supported ONIX fields

Ask the distributor or metadata supplier which ONIX release, schema, codelist issue, and recipient profile it supports. Also ask whether its intake stores contributor identifiers and whether its outbound feed transmits them. A platform can accept an identifier without displaying it publicly.

EDItEUR List 44 defines code 16 for ISNI and code 21 for ORCID. ONIX values omit the display spaces or hyphens. [9] [10] OCLC identifies NameIdentifier as the contributor identifier composite in its ONIX guidance. [8]

List 44 explicitly supports the ISNI type in name, publisher, and imprint identifier elements. [9] Have the feed provider verify composite placement and element order against the agreed schema. Do not substitute an author’s identifier for a company or imprint identifier.

A readable contributor fragment

The following instructional ONIX 3 reference-name fragment uses Ruth Rendell’s identity as documented in Bowker’s FAQ. [2] It illustrates placement, not a product listing for this publisher. It is not a complete ONIX message and must not be copied into an unrelated author’s record.

<Contributor>
  <SequenceNumber>1</SequenceNumber>
  <ContributorRole>A01</ContributorRole>
  <NameIdentifier>
    <NameIDType>16</NameIDType>
    <IDValue>0000000121491740</IDValue>
  </NameIdentifier>
  <PersonName>Ruth Rendell</PersonName>
  <PersonNameInverted>Rendell, Ruth</PersonNameInverted>
</Contributor>

EDItEUR List 17 uses A01 for author, A12 for illustrator, and B06 for translator. [11] An identifier does not replace the name, role, or contributor order. Use CorporateName for a corporate contributor rather than forcing an organization into personal-name fields. [8]

Validate the whole delivery, not just the number

1. Validate identity. Confirm that the assigned identifier belongs to the credited public identity.
2. Validate syntax. Preserve all characters, check length and check character, and remove display separators for the ONIX export. A valid checksum alone does not establish ownership of the identifier.
3. Validate the full message. Run schema and recipient-profile checks through the feed provider. A well-formed XML fragment is not evidence of a valid complete product record.
4. Inspect the actual export. Confirm that the intake field became the intended composite, identifier type, and value. Check that multiple contributors did not inherit the first contributor’s identifier.
5. Check receipt and use. Retain acknowledgments, error reports, and a follow-up observation or written confirmation of processing.

If the recipient does not support ISNI, keep the verified value in the master register and record the limitation. Ask whether a supported upload template or support-assisted route is available. Do not insert identifiers into subtitles, keywords, biographies, or ISBN fields to force them through.

Recipients also differ in update handling. For example, OCLC’s published ONIX instructions say it does not accept block-level partial updates and requests the entire record in a delta file. [8] That is an OCLC-specific delivery rule, not an instruction to use the same update method for every partner.

8. A manageable rollout for an independent publisher

Choose one owner, one shared register, and one pilot group. A solo publisher can perform all the roles; the records still need clear decisions and dates.

• First pass: List recurring contributors and confirm the approved public names. Search for existing identifiers. Log uncertain cases instead of forcing matches.
• Pilot: Select one forthcoming book, one multi-format title, and one backlist problem. Link contributor identities, verify credits, and test the available recipient fields.
• Corrections: Resolve the most consequential identity conflicts first. Send targeted updates and verify the result before enlarging the batch.
• Routine operation: Add identity reuse to each new project and review the exception queue at an established production checkpoint.

Track verified identities, unresolved matches, missing identifiers, applications pending, and destination corrections awaiting confirmation. Define the denominator: ten contributor identities are not the same thing as ten product credits. Measure whether the publisher can explain and reproduce a correct attribution, rather than treating identifier counts as a marketing performance metric.

Release and correction checklist

• The credited public name and role match the approved publication record.
• The contributor key points to the intended identity, with evidence and approval.
• Existing identifiers were checked before any new application.
• Pen-name relationships and private administrative details have appropriate access limits.
• Each edition includes its actual contributors rather than an unreviewed copied roster.
• Publisher, imprint, contributor, and product identifiers remain in their own fields.
• The recipient’s supported fields and current requirements are documented.
• The exported record, delivery response, and unresolved exceptions are retained.

For the wider year-end review, use The Publishers’ Guide: What Every Publisher Should Review Before 2027. For related guidance, visit Distribution & Metadata. The contributor register proposed here can sit alongside the title register recommended in Edition 005.

Frequently asked questions

Does every author need an ISNI before publishing?

BISG’s announcement does not establish a universal publication prerequisite. Check the current requirements of each distribution channel and adopt a documented house process.

Does every new book or edition need a new author ISNI?

No. Reuse the verified identity when the same public identity is credited. Review new editions for added or changed contributors, and apply ISBN rules separately.

Can an author have both ISNI and ORCID?

Yes. They serve different workflows. Keep their types distinct and send each through the field the recipient supports.

Should each imprint have its own ISNI?

Consider separate identification when the imprint is a distinct public organizational identity and a partner can use it. Check existing records and agency guidance first; a separate website alone is not sufficient reason.

What if two contributors have the same name?

Review their associated works and other reliable evidence. Keep separate local keys, and leave the identifier unresolved until the correct mapping is established.

What if a platform has no ISNI field?

Retain the verified identifier locally, ask about supported delivery alternatives, and log the limitation. Keep accurate contributor names and roles in the supported fields.

Will an ISNI automatically combine retailer author pages or increase sales?

Do not assume either result. Check how each recipient uses identifiers and handle author-page corrections through its supported process.

Can a publisher register on an author’s behalf?

Registration agencies may support publisher applications. Confirm the selected agency’s process, submission permissions, and responsibility for costs and corrections.

Authoritative references and further reading

Sources checked October 29, 2026. Original procedures and examples in this guide are editorial recommendations unless attributed otherwise.

1. BISG: October 27, 2026 announcement. This is the verified source for the six priorities. It links to Recommended Practices for Assigning ISNI and ISNI Implementation in the U.S. Market: Examples and Blockers; those two full resources were not accessible in this review.
2. Bowker ISNI: Frequently Asked Questions. Public identities, name variants, pseudonyms, corrections, identifier structure, and the documented illustrative identity.
3. International ISBN Agency: What is an ISBN?
4. ORCID: What is an ORCID iD and how do I use it?
5. ORCID: Structure of the ORCID Identifier.
6. MVB: ISNI FAQ. Agency-specific registration and correction guidance.
7. Bowker ISNI registration service. Check current service terms before applying.
8. OCLC: Advice for ONIX Providers. Contributor entries and recipient-specific delivery expectations.
9. EDItEUR List 44, code 16: ISNI.
10. EDItEUR List 44, code 21: ORCID.
11. EDItEUR List 17: Contributor role codes.