HISCO - historical international standard classification of occupations - is a classification scheme of occupational activities worldwide.
See History of Work - HISCO for more background.
The HISCO Look-Up Service is based on the dataset Mandemakers, Kees; Mourits, Rick; Muurling, Sanne, 2018, "HSN_HISCO_release_2018_01", https://hdl.handle.net/10622/MUZMAL, IISH Data Collection, V2.
Update 12-10-2020: the API now uses the 2020 version of the dataset. Mandemakers, Kees; Hornix, Jan; Mourits, Rick; Muurling, Sanne, 2020, "HSN standardized, HISCO-coded and classified occupational titles, release 2020.02", https://hdl.handle.net/10622/88ZXD8, IISH Data Collection, V1.
https://api.coret.org/hisco/lookup.php is a HTTP GET request returning JSON. The service looks up the occupation (via ElasticSearch) and returns suggested matches in the HISCO dataset.
The following parameters are recognized:
Example output for https://api.coret.org/hisco/lookup.php?q=broodbakker&limit=1&pretty:
[ { score: 12.171061, hisco: { uri: "https://iisg.amsterdam/resource/hisco/code/hisco/77620", major_group: "Production and related workers, transport equipment operators and labourers", minor_group: [ "Food and Beverage Processors", "Bakers, Pastry Cooks and Confectionery Makers", "Bread Baker" ] }, standard: "broodbakker", original: "broodbakker@" } ]
The HISCO Look-Up Service is used on (the English version of) Open Archives. Open Archives shows the meta-data of archival records, which also include occupations (in A2A terms: profession). Each time a record is shown, like this Population register record, the occupations are looked up in order to provide additional information about the (Dutch) occupation.
When an occupation is not found, this occupation is stored. As the Open Archives dataset is to be used in the CLARIAH Plus infrastructure, the list of occupations which couldn't be found can be used to update the HISCO dataset.
https://api.coret.org/hisco/no_results.php is a HTTP GET request returning JSON. The service outputs the complete list of occupations which where not not found in the HISCO dataset. For each occupation a count is provided (how often the occupation was looked up) and a link to the search function of Open Archives which results in all person mentions with the specific occupation.
The following parameter is recognized:
Example output for https://api.coret.org/hisco/no_results.php?pretty:
[ { occupation: "kostleerling", count: "28", url: "https://www.openarch.nl/search.php?name=%25%22kostleerling%22" }, { occupation: "schoolleerling", count: "19", url: "https://www.openarch.nl/search.php?name=%25%22schoolleerling%22" }, { occupation: "huisvrouw", count: "18", url: "https://www.openarch.nl/search.php?name=%25%22huisvrouw%22" }, { occupation: "cadet sergeant", count: "13", url: "https://www.openarch.nl/search.php?name=%25%22cadet+sergeant%22" }, { occupation: "borgemeester", count: "12", url: "https://www.openarch.nl/search.php?name=%25%22borgemeester%22" }, ... ]
The HISCO Look-Up Service is used by Genealogy Online. When processing a GEDCOM to make a genealogical publication, the occupations (GEDCOM tag 'OCCU') are looked up. When an occupation is not found, this occupation is not stored for the 'No results' method (this is because occupation provided by genealogists are more "messy" than those found in archival records).
The HISCO information is added to the recognized occupations on each person page. Also the section 'Distribution of professions (based on the HISCO classification)' is created on the Statistics page (example) of each publication.
https://api.coret.org/hisco/publication_stats.php is a HTTP GET request returning JSON wrapped in a function. The service outputs the complete list of classified occupations (HISCO's) in Genealogy Online publications.
The zoomable sunburst visualization uses this API.
The following parameter is recognized:
Example output for https://api.coret.org/hisco/publication_stats.php?json:
{ name: "hisco", children: [ { name: "0 Professional, technical and related workers", children: [ { name: "0-11 Chemists", children: [ { name: "0-11.10 Chemist, General", size: 11 }, { name: "0-11.50 Analytical Chemist", size: 1 } ] }, { name: "0-12 Physicists", children: [ { name: "0-12.10 Physicist, General", size: 3 } ] }, ... ] }