CACrown ArchivesThe cinema collection
EN/FR
Search
Menu
Research dossier · People & Ideas

Nicholas Mynn

English politician

Correspondence, annotated notebooks and portrait silhouettes prepared for research
People and ideasInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionMar 6, 2026
Entity authorityQ16227792 ↗
Source-derived summary

Nicholas Mynn (fl. 1558–1572), of Little Walsingham, Norfolk, was an English politician.

Life

Mynn was the second son of John Mynn. He married Elizabeth Drury, who was the daughter of Robert Drury.

Mynn was a servant of Thomas Howard, the Duke of Norfolk.

Mynn was a Member (MP) of the Parliament of England for Bramber in 1558, Horsham in 1559, New Shoreham in 1563, Morpeth in 1571 and Castle Rising in 1572.

In 1558, the Duke of Norfolk sent him to Rome to secure a dispensation for Norfolk's second marriage. By 1560, he had moved to Little Walsingham. Nothing further is known about him after 1572.

Editorial summary

This brief starts where responsible research should: with the source description of “Nicholas Mynn” as english politician. Everything that follows is an evidence route, not borrowed authority.

Editorial reviewA useful biographical orientation record, particularly for establishing names, roles and a first chronology. The current lead gives the account dated anchors—1558, 1572, 1559, 1563—that can be checked directly. The selected authority fields contribute no independent date. The account is most persuasive where Nicholas, Mynn and English can be independently traced.
Editorial analysis

Why this record matters

The subject matters to the people & ideas register because the source frames it as english politician. Its deeper value depends on whether names, dates, institutions and citations support that framing.

Evidence profile

Chronology provides the most reliable spine for this subject; interpretation should follow only after identities and dates are secure. The source revision retrieved here is dated Mar 6, 2026. The linked authority identifier is Q16227792. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1558, 1572, 1559 and 1563.

Critical limits

A concise life account rarely captures disputed attribution, private networks or the changing language used to describe a career. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Read biographical claims against dates, named institutions and the cited references. Distinguish a subject’s later reputation from evidence produced during their lifetime.

Best used for
  • Establishing names and roles
  • Building a first chronology
  • Locating cited institutions
Verify next

Personal papers, civil or court records, institutional files and the scholarship cited by the source.

Three-step research path

  1. Establish the record: confirm the title “Nicholas Mynn”, its source revision and the description used here.
  2. Expand the search: follow Nicholas Mynn primary sources, Nicholas Mynn archive and Nicholas research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Nicholas Mynn”?
  2. Which claims depend on a single source or contested interpretation?
  3. Which primary records establish identity, chronology and institutional ties?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Nicholas Mynn” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.