CACrown ArchivesThe cinema collection
Menu
Research dossier · General Reference

Thomas Mellish

cricketer (1773-1837)

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionDec 25, 2025
Entity authorityQ7792375
Source-derived summary

Thomas Mellish (1773 – 29 July 1837 in Uxbridge, Middlesex) was an English amateur cricketer who made 52 known appearances in important matches between 1791 and 1815.

He was an early member of Marylebone Cricket Club (MCC) whose teams he most often represented. He was an occasional patron of cricket, his own T Mellish's XI being active in a number of matches between 1801 and 1807.

He was educated at Eton but surprisingly little is known about Mellish, although he was undoubtedly a prominent amateur player of his time. He is not mentioned in Scores & Biographies except in the scorecards.

Editorial summary

This brief starts where responsible research should: with the source description of “Thomas Mellish” as cricketer (1773-1837). Everything that follows is an evidence route, not borrowed authority.

Editorial reviewA concise reference frame for defining the subject, testing terminology and identifying the institution closest to the evidence. The current lead gives the account dated anchors—1773, 1837, 1791, 1815—that can be checked directly. The linked authority record independently contributes the date 1773-01-01. The account is most persuasive where Thomas, Mellish and cricketer can be independently traced.
Editorial analysis

Why this record matters

The subject matters to the general reference register because the source frames it as cricketer (1773-1837). Its deeper value depends on whether names, dates, institutions and citations support that framing.

Evidence profile

Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Dec 25, 2025. The linked authority identifier is Q7792375. None of the 1 selected statements returned an explicit reference. The first chronological checks are 1773, 1837, 1791 and 1815.

Critical limits

Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “Thomas Mellish”, its source revision and the description used here.
  2. Expand the search: follow Thomas Mellish primary sources, Thomas Mellish archive and Thomas 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 “Thomas Mellish”?
  2. Which cited source is closest to the event, object or claim?
  3. What terminology or title could unlock a more precise catalogue search?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Thomas Mellish” 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.