publicdata.au publicdata.au on GitHub

Tasmanian deaths index, 1803 to 1939

live
Publisher Libraries TasmaniaUpdated no longerLicence CC BY 4.0Latest 2024-11-28Rows 205,806Fields 27

The deaths and burials records of the Tasmanian Names Index kept by Libraries Tasmania, covering 1803 to 1939, one row per index record. Each row carries the record number and address, the name of the person, the year and date of death, the age, gender, place and year of registration, the burial date and cemetery where known, and, for some records, the parents, spouse, ship of arrival, military rank, will number or remarks. The publisher's XML file is read one row per record.

Also called: Tasmanian Names Index deaths, Tasmanian Deaths 1803-1939, Tasmania death index, Tasmanian burial records.

Before you use it
What is in each row?
One record from the deaths and burials part of the Tasmanian Names Index, with the person's name, the year and date of death or burial, the age, gender, place and year of registration, and the names of parents or spouse where the source gives them. Each row links to the record on the Libraries Tasmania site.
Why do some cells hold two values?
Where a record names a person more than once, or gives two years, the values are kept in the publisher's order and joined with a vertical bar.
Where are the links to the scanned pages?
The publisher's file nests the archive reference and the address of the scanned page inside each record. They are not carried here. The record address in each row leads to the same record on the Libraries Tasmania site, which shows the scanned page.
Is it complete?
The publisher describes it as people who died in Tasmania including some burial records, with burials for 1900 to 1939 only. Some records were compiled by the Tasmanian Family History Society, and the remarks say so on those rows. The series is closed.

Made for agents

Connect your AI agent

Any agent that connects to publicdata.au/mcp can find this dataset, read its 27 fields, count and filter across all 205,806 rows and diff its versions. Every answer names the version and carries Libraries Tasmania's attribution. No key.

Then ask it: What does Tasmanian deaths index, 1803 to 1939 hold, and what changed in the newest version?

claude mcp add --transport http publicdata https://publicdata.au/mcp

One command. No key, no account, no sign-up.

Download it as Excel, CSV, JSON and 6 more formats

Pick a format and a version. Excel is picked first because it opens in the tools most offices have. The URL is yours to keep. A dated version keeps its content.

Format
"Latest" redirects to the newest version and will change when the publisher releases again. A dated version keeps its content.
https://publicdata.au/d/tas-deaths-1803-1939/latest/data.xlsx
Download this file

One workbook with a records sheet of 205,806 typed rows, a fields sheet and a publicdata sheet with the provenance. Dates are real Excel dates. Opens in Excel, Numbers, LibreOffice and Sheets.

In your own tools

Use it in Excel, R, Python and more

Excel and Power BI read the CSV from its address and refresh from it. The R and Python packages take any dataset on this site by its slug, so a new dataset needs no new release. The DuckDB file attaches read-only over HTTPS, and a query reads only the blocks it touches.

The dated URL in the code never changes. https://publicdata.au/d/tas-deaths-1803-1939/latest/ redirects to the newest version.

https://publicdata.au/d/tas-deaths-1803-1939/latest/data.csv

In Excel choose Data, then From Web, and paste this address. Excel keeps it, so Refresh All reads the newest version. A sheet holds about a million rows; past that, load the query to the Data Model.

What is in it

Column names are made snake_case and the publisher's original header is kept beside each one. Blank cells are null. Nothing is added, removed, ranked or summarised. Headers were made snake_case. The publisher's element names are kept beside every field in schema.json. Rows were left alone.

FieldTypePublisher's headerNote
record_idinteger@idThe publisher's number for the record in the Tasmanian Names Index.
record_urlstringRECORD_URL
namestringNAMESurname, then given names. A second name the record gives follows a vertical bar.
yearstringYEARThe year of death or burial as the index gives it. A few records give two.
death_datestringDEATH_DATEAs the source gives it, which may be a full date, a month and year, or a year.
agestringAGEAs recorded, which may be in years or a phrase.
genderstringGENDER
reg_placestringREG_PLACE
reg_yearstringREG_YEAR
burial_datestringBURIAL_DATE
propertystringPROPERTY
property_indexstringPROPERTY_INDEX
where_diedstringWHERE_DIED
descstringDESC
desc_srstringDESC_SR
remarksstringREMARKS
fatherstringFATHER
motherstringMOTHER
spousestringSPOUSE
name_see_alsostringNAME_SEE_ALSO
name_see_also_spstringNAME_SEE_ALSO_SP
name_rankstringNAME_RANK
shipstringSHIP
ship_native_placestringSHIP_NATIVE_PLACE
admiss_datestringADMISS_DATE
birth_datestringBIRTH_DATE
will_nostringWILL_NO

Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json. The key is record_id.

A sample of 10 rows

Records from the newest year in the index, in the publisher's order, with every field. A blank cell is shown as null.

record_idrecord_urlnameyeardeath_dateagegenderreg_placereg_yearburial_datepropertyproperty_indexwhere_dieddescdesc_srremarksfathermotherspousename_see_alsoname_see_also_spname_rankshipship_native_placeadmiss_datebirth_datewill_no
1537531https://stors.tas.gov.au/NI/1537531Abbott, Barry1939null7nullnullnull31 Aug 1939Cornelian Bay CemeteryCornelian Bay CemeterynullLast known residence: 10 Yardley St, North HobartnullnullnullnullnullnullnullnullnullnullnullnullBU 36048
1537547https://stors.tas.gov.au/NI/1537547Abbott, Madeline Louisa1939null72nullnullnull22 Dec 1939Cornelian Bay CemeteryCornelian Bay CemeterynullLast known residence: Stowell Hospital, Battery PointnullnullnullnullnullnullnullnullnullnullnullnullBU 36350
1537565https://stors.tas.gov.au/NI/1537565Abel, Bridget1939null81nullnullnull20 Jun 1939Cornelian Bay CemeteryCornelian Bay CemeterynullLast known residence: St Johns Park, New TownnullnullnullnullnullnullnullnullnullnullnullnullBU 35811
1537587https://stors.tas.gov.au/NI/1537587Abrahams, Iris Moyna May1939null16nullnullnull02 Aug 1939Cornelian Bay CemeteryCornelian Bay CemeterynullLast known residence: LauncestonnullnullnullnullnullnullnullnullnullnullnullnullBU 35963
1537589https://stors.tas.gov.au/NI/1537589Abrahams, Samuel Richard193914 Jul 193974nullnullnullCremated 17 Jul 1939Cornelian Bay CemeteryCornelian Bay CemeterynullLast known residence: LindisfarnenullnullnullnullnullnullnullnullnullnullnullnullCR 35898
1537677https://stors.tas.gov.au/NI/1537677Adams, Thomas1939null74nullnullnull30 May 1939Cornelian Bay CemeteryCornelian Bay CemeterynullLast known residence: 39 Church St, North HobartnullnullnullnullnullnullnullnullnullnullnullnullBU 35754
1537690https://stors.tas.gov.au/NI/1537690Adcock, Walter1939null69nullnullnull04 Nov 1939Cornelian Bay CemeteryCornelian Bay CemeterynullLast known residence: Royal Hobart Hospital, HobartnullnullnullnullnullnullnullnullnullnullnullnullBU 36220
1537720https://stors.tas.gov.au/NI/1537720Agnew, Louis L193911 Jul 1939nullnullnullnullCremated 30 Sep 1939Cornelian Bay CemeteryCornelian Bay CemeterynullLast known residence: SydneynullnullnullnullnullnullnullnullnullnullnullnullCR 36133
1537799https://stors.tas.gov.au/NI/1537799Alcock, Annie Angelina1939null88nullnullnull10 Jan 1939Cornelian Bay CemeteryCornelian Bay CemeterynullLast known residence: 31 Mary StnullnullnullnullnullnullnullnullnullnullnullnullBU 35434
1537826https://stors.tas.gov.au/NI/1537826Aldred, Isaac1939null88nullnullnull18 Feb 1939Cornelian Bay CemeteryCornelian Bay CemeterynullLast known residence: 65 Barrack St, HobartnullnullnullnullnullnullnullnullnullnullnullnullBU 35522
The first row as JSON

As it appears in data.json.

GET https://publicdata.au/d/tas-deaths-1803-1939/latest/data.json
{
  "record_id": 470662,
  "record_url": "https://stors.tas.gov.au/NI/470662",
  "name": "Knowles, Edward",
  "year": "1873",
  "death_date": "Jan 1873",
  "age": null,
  "gender": null,
  "reg_place": null,
  "reg_year": null,
  "burial_date": null,
  "property": null,
  "property_index": null,
  "where_died": null,
  "desc": "Master of the 'North Fleet' - lost at sea January 1873",
  "desc_sr": null,
  "remarks": null,
  "father": null,
  "mother": null,
  "spouse": null,
  "name_see_also": null,
  "name_see_also_sp": null,
  "name_rank": null,
  "ship": null,
  "ship_native_place": null,
  "admiss_date": null,
  "birth_date": null,
  "will_no": null
}

Query it without downloading

The query API returns only the rows you ask for, as JSON, NDJSON or CSV, from the same typed rows as the files. It needs no key. Build a query here and run it, then copy the URL or the code into your own work.

Try rows or aggregate for this dataset. The query builder needs JavaScript.

How filters work

Each filter is field=operator.value in the query string, and every filter must match. A number or date field compares as a number or date, and a text field compares as text. Values are case-sensitive, except that like and ilike ignore case in the ASCII letters A to Z. Prefix not. to negate a filter, as not.eq.value.

OperatorWhat it matches
eq.valueEqual to the value.
neq.valueNot equal to the value. A blank cell does not match.
gt.valueGreater than the value.
gte.valueGreater than or equal to the value.
lt.valueLess than the value.
lte.valueLess than or equal to the value.
like.*text*Matches a pattern where * stands for any run of characters, ignoring case in the ASCII letters A to Z.
ilike.*text*The same as like. Both ignore case in ASCII letters only, so É and é differ.
in.(a,b,c)Equal to any value in the list. A value cannot contain a comma.
is.nullBlank in the source, or suppressed by the publisher.
ParameterWhat it does
selectFields to return, comma-separated. Every field when absent.
orderfield.asc or field.desc, comma-separated. When absent, rows come in the order of the file they are read from. For the newest versions that is the version's own data.parquet, which keeps the publisher's order unless the dataset sorted it. Any other version is read from the Parquet file the answer names in file, and when that file is sorted the answer names its sort in order, which ties follow too.
limitRows per page, 1 to 10,000. 100 when absent.
offsetRows to skip. The next URL in each answer sets it for you.
groupOn aggregate, fields to group by, comma-separated.
metricOn aggregate, count, sum.field, avg.field, min.field or max.field, comma-separated. count when absent.
formatjson, ndjson or csv. JSON carries the provenance header, and the others carry it in response headers.

Without a version the API answers from the newest version, and that answer changes when the publisher releases again. Put versions/<date>/ before rows or aggregate for an answer from that version alone. Every version with a table can be queried, and /api/v1/datasets/<slug>/versions lists them. A query on a version the database does not hold is read from its Parquet file, and one that would read too much of it is refused with DuckDB SQL that answers it from the file. The 1 newest version is loaded; versions lists them.

The API allows 60 requests in 10 seconds from one address. Above that it answers 429 for 10 seconds with a Retry-After header, a RateLimit-Policy header and a JSON body that gives the limit. Every API answer carries the same RateLimit-Policy. A client should wait the Retry-After seconds, or read the files, which have no limit. openapi.json describes this dataset's query paths for client generators and agents.

https://publicdata.au/mcp is a remote MCP server over Streamable HTTP with the same tools, defined in the same place, so a tool added to the pages is added here too. It needs no key and no account. Its row tools and the query API answer every version through one query path, so a tool's answer and the query URL it cites give the same rows. A query that would read too much of a file is refused with DuckDB SQL that answers it from the file. It also has search and fetch, the two tools ChatGPT's deep research and company knowledge call by name, which run search_datasets and read a dataset's record in the shapes those features expect. The row tools are held to the query API's limit of 60 queries in 10 seconds from one address, and each call is two queries because it also counts the matching rows. Add it to Claude Code with claude mcp add --transport http publicdata https://publicdata.au/mcp, add the URL in Claude as a custom connector, connect the publicdata.au plugin in ChatGPT, or give it to any client that connects to remote MCP servers. Each dataset with a table is also a resource at https://publicdata.au/d/<slug>/fields.json, which lists its fields with their types, the publisher's descriptions, their ranges and the values they hold, so an agent can read a dataset's shape before it writes a query.

What changed

One version for every release the publisher has made since this site started following the dataset. The date is the day the file changed on the portal.

  • 2024-11-28
    205,806 rows27 fieldsutf-8-sigfa067a1367ec

versions.json · changes.json · history.tar.zst (3.6 MB, every version's Parquet and manifest)

Questions

How do I download Tasmanian deaths index as a CSV file?

Open https://publicdata.au/d/tas-deaths-1803-1939/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/tas-deaths-1803-1939/v/2024-11-28/data.csv today. The same path serves Excel, JSON, Parquet, SQLite, DuckDB, NDJSON, Arrow. A dated URL never changes, so use it when the file must stay the same.

Can I open Tasmanian deaths index in Excel?

Yes. https://publicdata.au/d/tas-deaths-1803-1939/v/2024-11-28/data.xlsx is a workbook with the 205,806 rows on a records sheet, the field list on a second sheet and the provenance on a third. The CSV also opens in Excel. https://publicdata.au/d/tas-deaths-1803-1939/v/2024-11-28/data.csv.gz is the CSV at about a tenth of the size.

What years does Tasmanian deaths index cover?

The current version covers the years since 1803. Each release from Libraries Tasmania becomes a new dated version here, and earlier versions stay online.

How often is Tasmanian deaths index updated?

Libraries Tasmania no longer updates it. This site checks the portal every week and adds a dated version when the file changes.

Can I use Tasmanian deaths index commercially?

Yes. CC BY 4.0 allows commercial use, redistribution and derived works as long as the attribution is kept. The attribution string is in this page's side column and inside every file.

Is this the official source for Tasmanian deaths index?

No. The publisher is Libraries Tasmania, and its page is https://data.gov.au/data/dataset/tasmanian-deaths-1803-1939. National Digital converted the publisher's file to other formats. It renamed and typed the columns and kept only those the schema lists. National Digital made these changes, and the publisher is not responsible for them. The original sits beside every version as source.xml with its SHA-256, so the two can be compared.

What this site did to the data. Cells were typed, headers were renamed and the encoding was made UTF-8. Rows were left alone. The publisher's file sits beside every version as source.xml so the change can be checked.

Attribution and citation

The licence requires the publisher's attribution. We ask that you also name publicdata.au and link to the version you used.

Libraries Tasmania, Tasmanian Government, Tasmanian Deaths (1803-1939), https://data.gov.au/data/dataset/tasmanian-deaths-1803-1939, accessed 3 October 2026, licensed under CC BY 4.0. Serialised and versioned by National Digital at publicdata.au, https://publicdata.au/d/tas-deaths-1803-1939/v/2024-11-28/

The attribution alone is inside every file. Harvard is the author-date form a report or a brief asks for. Paste the HTML on a web page so the links carry.

Licence record

Libraries Tasmania states the licence, CC BY 4.0, on its own page, which was read and recorded here on 1 October 2026.

Every fetch reads the licence again and stops when it has changed. The fetch that made version 2024-11-28 read it from data.gov.au on 3 October 2026.

Also published on
  • Hugging Faceload_dataset("National-Digital/tas-deaths-1803-1939")
  • Kagglewith a starter notebook
  • ZenodoDOI 10.5281/zenodo.23123647

Each copy carries the same attribution and links back to this page.

For agents and tools

This page carries a schema.org Dataset record and is listed in /.well-known/ard.json and /catalog.json.

Source

Libraries Tasmania publishes this table on data.gov.au. Questions about the content go to the publisher. Questions about the files here go to corrections.

Fetched 3 October 2026. Source SHA-256 fa067a1367ec8dcf…

Improve this dataset

This page is built from register/tas-deaths-1803-1939.yaml on GitHub. Anyone can propose a fix to it, such as a clearer description or a field the publisher renamed, as a pull request.

Report a file that differs from the publisher's · How to contribute