Before comparing a product page with a laboratory report or a research paper, check whether they describe the same material. A short name can make the documents feel connected before that connection has been established. The useful work is in the details: the sequence, the chemical form, the modifications and the identifiers that let another reader find the same record.

This guide offers a document-reading workflow. It separates the description of a proposed compound from the evidence about a particular submitted sample. Both matter when deciding which information belongs together.

Build a small identity record before following the claim

Open the relevant documents side by side and copy the identifying information exactly. Retain punctuation, prefixes, suffixes and footnotes. A compact comparison table helps you notice where a description is complete and where a connection still needs confirmation.

FieldWhat to recordQuestion it helps answer
NameExact name, aliases and variant labelsAre the documents using the same naming convention?
Sequence or structureThe stated sequence, direction and structural representationWhich ordered or connected molecular entity is proposed?
Chemical detailsTermini, modifications, stereochemistry and reported salt formWhat information is missing from the short name?
Reference recordDatabase, identifier, species where relevant and version or access dateCan another reader retrieve the same description?
Sample linkSupplier reference, lot, laboratory sample code and report identifierWhich physical material was actually examined?

Leave uncertain fields visibly unresolved. Writing “not stated in this source” is more useful than filling a blank from another page without recording where that information came from.

Read a sequence in its stated direction

Peptide sequence conventions normally run from the amino, or N-terminal, end toward the carboxyl, or C-terminal, end. Residue order matters: changing the order changes the described chain. IUPAC’s peptide nomenclature recommendations explain both that direction and the difference between an amino acid and the residue it contributes to a peptide. IUPAC-IUB: peptide nomenclature, sections 3AA-11 to 3AA-13.

Amino acids can appear as three-letter or one-letter symbols. For example, alanine is Ala or A, glycine is Gly or G, and aspartic acid is Asp or D. The single-letter D in a sequence therefore has a different role from a D- stereochemical prefix attached to an amino acid name. Read the surrounding notation before deciding what a character means. IUPAC-IUB: amino acid names and symbols.

For a simple editorial comparison, imagine the three-residue strings AGK and GAK. They contain the same letters and have the same length, but the first two positions differ. A quick scan for matching characters would miss the difference; a position-by-position comparison would expose it. This example illustrates reading order and makes no claim about a marketed compound.

When transcribing, retain the original sequence beside any reformatted version. Remove layout spaces only when their role is clear. If an image makes a character ambiguous, seek a text version or ask the source to confirm it.

Check the ends and the modifications separately

A sequence line may need additional annotations to specify chemical details. The UniProt user manual records modifications as features with accompanying descriptions, including terminal acetylation and amidation. A reader should therefore look beyond the row of residue symbols for the exact position and nature of a stated modification. UniProt Knowledgebase user manual: modified residues.

Make separate entries for the N-terminal form, C-terminal form and any modified residue. Preserve the source’s notation instead of silently converting an unfamiliar abbreviation into a familiar one. If one document identifies a terminal modification and the other omits it, you have found an unresolved detail; you have not yet shown that the materials agree or disagree.

Connections between residues can require their own annotation. UniProt distinguishes disulfide bonds within one chain from bonds connecting separate chains and records the participating positions. Its documentation also distinguishes experimentally determined bonds from predictions or assignments made by similarity. Those evidence labels are part of the record. UniProt: disulfide bond annotation.

This matters when two illustrations look alike. A drawing can omit bond detail for readability. Prefer an explicitly annotated structure or sequence record when the bond arrangement is relevant to the comparison, and retain any uncertainty stated by its authors.

Keep stereochemistry in the description

Two structures can share the same atomic connections while differing in their spatial arrangement. IUPAC classifies these as stereoisomers. An elemental formula, a familiar name or a count of amino acid residues does not by itself describe every such distinction. IUPAC Gold Book: stereoisomers.

Copy stereochemical descriptors with the rest of the name. If the source uses D- or L- notation, a stereochemical drawing, or another explicit descriptor, preserve that information rather than treating it as formatting. If two documents differ, identify the exact position or descriptor involved before looking for an explanation.

The practical question is modest: “What configuration does each source actually specify?” A record with missing stereochemical information should stay incomplete in your notes. It should not be silently upgraded to the most familiar form of the compound.

Give the reported chemical form its own line

A sequence description and a description of a supplied salt answer related but different identification questions. ICH Q6A explicitly discusses identifying the individual ions of a salt, or using a test specific to the salt itself. That pharmaceutical guidance illustrates why a salt designation belongs in an identity record; it does not establish the form or quality of a particular research sample. ICH Q6A, section 3.2.1(b), hosted by FDA.

Copy a reported counterion or salt name exactly. If one source describes the underlying peptide while another describes the supplied chemical form, ask how those descriptions relate. Do not infer a composition ratio, water content or quantitative reporting basis from a short salt label. Keep those as separate fields to check against the analytical documentation.

Check whether a sequence is a precursor, a mature form or a fragment

A biological database may display a precursor sequence that undergoes processing. UniProt’s sequence-processing guidance explains that the displayed sequence can require cleavage to produce a mature form and points readers to its processing annotations. It also notes that absence of a processing subsection can reflect a lack of knowledge, so silence should not be treated as complete characterization. UniProt: sequence processing.

Before comparing a short synthetic peptide with a much longer database entry, identify the relationship claimed by the source. Is the short sequence a specified residue range, a processed chain, or a separately described variant? Record the numbering system and organism where relevant. Do not select a convenient segment from the longer sequence and present your match as if the paper had defined it.

Keep the accession number with that interpretation. UniProt recommends its accession numbers as stable identifiers for citing entries. The identifier makes the reference retrievable; the accompanying sequence and processing details explain which part of that reference you are discussing. UniProt: accession numbers.

Use database identifiers to follow provenance

PubChem makes a useful distinction between a Substance record and a Compound record. A Substance record preserves information supplied by a particular contributor; a Compound record represents a standardized chemical structure associated with one or more submissions. The distinction helps you follow who supplied a description and which normalized structure it was linked to. PubChem: Compound versus Substance.

A matching database identifier is useful for checking a proposed identity, but it is not a laboratory result for a vial. Keep the database record and the sample report in different columns. The connection between them still needs to be established by the sample documentation and its analytical evidence.

Also distinguish computed properties from measurements. PubChem labels properties such as molecular weight and formula as computed where they are calculated from the represented structure. Those values can provide a comparison target; they do not show that a particular sample has been measured and found to match it. PubChem glossary: computed properties and descriptors.

If two database pages appear inconsistent, compare the actual structures, components and stereochemical detail before choosing a value. PubChem’s search documentation offers different notions of structural matching, including settings for connectivity, stereochemistry, isotopes and tautomers. Record the setting or representation used when it affects the comparison. PubChem: structure search.

Ask what the laboratory evidence distinguishes

Once the proposed structure is clear, return to the report. Does it give a named identity test, an observed result and a comparison basis? A theoretical value copied into a report and an experimentally observed value play different roles. Preserve the labels that distinguish them.

A mass match alone cannot specify every structural arrangement: stereoisomers can share composition, and the order of a sequence is information beyond a list of its constituents. Peptide identification can draw on interpreted fragmentation data as well as other measurements. NIST’s work on a reference peptide spectral library illustrates the use of accurate mass, elution patterns and peptide-map information together. It does not mean every report labelled “MS” contains that full analysis. Dong and colleagues, 2018, NISTmAb peptide spectral library.

If a reported test leaves a distinction unresolved, record the limitation and ask what evidence addresses it. Understanding analytical methods explains how identity, chromatographic purity and quantitative results contribute different information. The COA field guide shows where to locate those statements in a document.

Carry the exact identity into your research notes

Before summarizing a paper, write one sentence defining the material as that paper describes it. Include the exact name or variant, the sequence or source reference where provided, and any stated chemical form. Then note which details match the document you are comparing and which remain uncertain.

For example: “Both sources use the same short name; one specifies a terminal modification and the other does not.” That is a useful finding. “They are the same compound” would require resolving the missing detail. Equally, avoid calling the sources contradictory until you have checked whether one simply provides a shorter description.

Keep conclusions attached to the material and setting actually studied. A useful next step is how to read a research paper, where the identity record becomes part of a broader check of the methods, comparisons and results.

Sources and editorial note

Prepared on 3 October 2026 with AI assistance. The linked IUPAC, ICH, UniProt, PubChem and NIST sources were consulted during preparation. The comparison workflow and short sequence example are editorial explanations. No new characterization, product verification or external scientific peer review was performed for this guide. The header image is an AI-generated editorial illustration. Database annotations should be read with their evidence statements and source records.

Introducing / CaliLean Field Notes

A little more
perspective.

An editorial letter for curious minds. Thoughtful reading, questions worth keeping and the sources behind them.

Explore Field Notes Join the list for the first edition
Back to all resources Back to top