SDG Metadata

10-7-3

	Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
	English MIT		0	0	0	0	2	0	0

	Arabic MIT	0%	31	4,636	36,366	31	0	0	0

	French MIT	0%	31	4,636	36,366	30	0	0	0

	Portuguese MIT	0%	31	4,636	36,366	31	0	0	0

	Russian MIT	0%	31	4,636	36,366	31	0	0	0

	Spanish MIT	0%	31	4,636	36,366	31	0	0	0

Please sign in to see the alerts.

Overview

Project website	github.com/worldbank/sdg-metadata
Instructions for translators	This project is limited to Russian translation only, for now. More detailed instructions to come.
Project maintainers	brockfanning
Translation license	MIT License
Translation process	Translations can be made directly. Translation suggestions are turned off. Any authenticated user can contribute. The translation uses monolingual files. The translation base language can not be edited.
Source code repository	`https://github.com/worldbank/sdg-metadata`
Repository branch	master
Last remote commit	Merge pull request #541 from weblate/weblate-sdg-metadata-1-1-1a `2bbcb9a225a` brockfanning authored 4 weeks ago
Last commit in Weblate	Translated using Weblate (French) `02091545123` deblsyl authored a year ago
Weblate repository	`https://hosted.weblate.org/git/sdg-metadata/1-1-1a/`
File mask	`translations-metadata/*/10-7-3.yml`
Monolingual base language file	`translations-metadata/en/10-7-3.yml`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		186		27,816		218,196
Source		31		4,636		36,366
Approved	0%	0	0%	0	0%	0
Waiting for review	0%	0	0%	0	0%	0
Translated	16%	31	16%	4,636	16%	36,366
Needs editing	1%	1	1%	1	1%	10
Read-only	16%	31	16%	4,636	16%	36,366
Failing checks	1%	2	5%	1,657	5%	12,298
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	82%	154	83%	23,179	83%	181,820

Last 12 months Previous

Activity in last 12 months


Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec	Jan	Feb

Quick numbers

27,816

Hosted words

186

Hosted strings

16%

Translated

0

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

—

Hosted strings

—

—

Translated

—

—

Contributors

—

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2023-02-25 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2023-02-25 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None New alert SDG Metadata / 10-7-3	Repository has changes. 7 months ago
None New strings to translate SDG Metadata / 10-7-3 — Russian	5 new strings to translate appeared to the translation. 7 months ago
None New strings to translate SDG Metadata / 10-7-3 — Portuguese	5 new strings to translate appeared to the translation. 7 months ago
None New strings to translate SDG Metadata / 10-7-3 — French	5 new strings to translate appeared to the translation. 7 months ago
None New strings to translate SDG Metadata / 10-7-3 — Spanish	5 new strings to translate appeared to the translation. 7 months ago
None New strings to translate SDG Metadata / 10-7-3 — Arabic	5 new strings to translate appeared to the translation. 7 months ago
None Resource update SDG Metadata / 10-7-3 — Russian	The "`translations-metadata/en/10-7-3.yml`" file was changed. 7 months ago
None String updated in the repository SDG Metadata / 10-7-3 — Russian	English <p><strong>Data availability:</strong></p> <p>The MMP is a global project, and as such collects data in all regions of the world. However, as mentioned throughout this document, MMP data is only as robust as the data sources available, meaning that for remote geographies less data tends to be available. Generally, MMP’s coverage is strongest in the Mediterranean and the US-Mexico border, whereas for the rest of the world data coverage is believed to be poor. However, coverage should not be equated with data quality, as for example in the case of the Mediterranean Sea, many remains are lost and consequently the data on the identities (age, gender, country of origin, name) of the decedents is highly incomplete.</p> <p><strong>Time series:</strong></p> <p>2014-present (ongoing data collection)</p> <p><strong>Disaggregation:</strong></p> <p>Data on SDG 10.7.3 is aggregated by country and year per the SDG reporting standards. However, far more disaggregated data are available in the public database available on the <a href="https://missingmigrants.iom.int/">MMP website</a>. <a href="#_Table_2:_Variables">Table 2</a>, below, presents the list of variables that constitute the MMP database. While ideally all incidents recorded would include entries for each of these variables – as these inform both the situation in which a death occurred and the profiles of those who died – the lack of official data on deaths during migration, as described above, mean that this is not always possible. The minimum information necessary to record an incident in the MMP database is the date of the incident, the number of dead and/or the number of missing, and the location of death. If the information for other variables is unavailable, the cell is left blank or “unknown” is recorded, as indicated in the table below. </p> <h5>Table 2: Variables recorded in IOM’s Missing Migrants Project database</h5> <table> <tbody> <tr> <td> <p>Variable Name</p> </td> <td> <p>Description</p> </td> </tr> <tr> <td> <p>Incident ID</p> </td> <td> <p>An automatically generated number used to identify each unique entry in the dataset.</p> </td> </tr> <tr> <td> <p>Region of incident</p> </td> <td> <p>The region in which an incident took place. For more about regional classifications used in the dataset, <a href="https://missingmigrants.iom.int/regional-classification">click here</a>.</p> </td> </tr> <tr> <td> <p>Reported date</p> </td> <td> <p>Estimated date of death. In cases where the exact date of death is not known, this variable indicates the date in which the body or bodies were found. In cases where data are drawn from surviving migrants, witnesses or other interviews, this variable is entered as the date of the death as reported by the interviewee. At a minimum, the month and the year of death is recorded. In some cases, official statistics are not disaggregated by the incident, meaning that data is reported as a total number of deaths occurring during a certain time period. In such cases the entry is marked as a “cumulative total,” and the latest date of the range is recorded, with the full dates recorded in the comments.</p> </td> </tr> <tr> <td> <p>Reported year</p> </td> <td> <p>The year in which the incident occurred.</p> </td> </tr> <tr> <td> <p>Reported month</p> </td> <td> <p>The month in which the incident occurred.</p> </td> </tr> <tr> <td> <p>Number dead</p> </td> <td> <p>The total number of people confirmed dead in one incident, i.e. the number of bodies recovered. If migrants are missing and presumed dead, such as in cases of shipwrecks, it is left blank.</p> </td> </tr> <tr> <td> <p>Number missing </p> </td> <td> <p>The total number of those who are missing and are thus assumed to be dead. This variable is generally recorded in incidents involving shipwrecks. The number of missing is calculated by subtracting the number of bodies recovered from a shipwreck and the number of survivors from the total number of migrants reported to have been on the boat. This number may be reported by surviving migrants or witnesses. If no missing persons are reported, it is left blank.</p> </td> </tr> <tr> <td> <p>Total dead and missing</p> </td> <td> <p>The sum of the ‘number dead’ and ‘number missing’ variables.</p> </td> </tr> <tr> <td> <p>Number of survivors</p> </td> <td> <p>The number of migrants that survived the incident, if known. The age, gender, and country of origin of survivors are recorded in the ‘Comments’ variable if known. If unknown, it is left blank.</p> </td> </tr> <tr> <td> <p>Number of females</p> </td> <td> <p>Indicates the number of females found dead or missing. If unknown, it is left blank. This gender identification is based on a third-party interpretation of the victim's gender from information available in official documents, autopsy reports, witness testimonies, and/or media reports.</p> </td> </tr> <tr> <td> <p>Number of males</p> </td> <td> <p>Indicates the number of males found dead or missing. If unknown, it is left blank. This gender identification is based on a third-party interpretation of the victim's gender from information available in official documents, autopsy reports, witness testimonies, and/or media reports.</p> </td> </tr> <tr> <td> <p>Number of children</p> </td> <td> <p>Indicates the number of individuals under the age of 18 found dead or missing. If unknown, it is left blank.</p> </td> </tr> <tr> <td> <p>Age</p> </td> <td> <p>The age of the decedent(s). Occasionally, an estimated age range is recorded. If unknown, it is left blank.</p> </td> </tr> <tr> <td> <p>Name</p> </td> <td> <p>The name of the decedent(s). If unknown, it is left blank. Not available in the public dataset. </p> </td> </tr> <tr> <td> <p>Country of origin</p> </td> <td> <p>Country of birth of the decedent. If unknown, the entry will be marked “unknown”. Not available in the public dataset.</p> </td> </tr> <tr> <td> <p>Region of origin</p> </td> <td> <p>Region of origin of the decedent(s). In some incidents, region of origin may be marked as “Presumed” or “(P)” if migrants travelling through that location are known to hail from a certain region. If unknown, the entry will be marked “unknown”. Not available in the public dataset.</p> </td> </tr> <tr> <td> <p>Cause of death</p> </td> <td> <p>The determination of conditions resulting in the migrant's death i.e. the circumstances of the event that produced the fatal injury. If unknown, the reason why is included where possible. For example, “Unknown – skeletal remains only”, is used in cases in which only the skeleton of the decedent was found.</p> </td> </tr> <tr> <td> <p>Location description</p> </td> <td> <p>Place where the death(s) occurred or where the body or bodies were found. Nearby towns or cities or borders are included where possible. When incidents are reported in an unspecified location, this will be noted.</p> </td> </tr> <tr> <td> <p>Location coordinates</p> </td> <td> <p>Place where the death(s) occurred or where the body or bodies were found. In many regions, most notably the Mediterranean, geographic coordinates are estimated as precise locations are not often known. The location description should always be checked against the location coordinates.</p> </td> </tr> <tr> <td> <p>Migration route</p> </td> <td> <p>Name of the migrant route on which incident occurred, if known. If unknown, it is left blank.</p> </td> </tr> <tr> <td> <p>UNSD geographical grouping</p> </td> <td> <p>Geographical region in which the incident took place, as designated by the United Nations Statistics Division (UNSD) geoscheme. </p> </td> </tr> <tr> <td> <p>Information source</p> </td> <td> <p>Name of source of information for each incident. Multiple sources may be listed.</p> </td> </tr> <tr> <td> <p>Link</p> </td> <td> <p>Links to original reports of migrant deaths / disappearances if available. Multiple links may be listed.</p> </td> </tr> <tr> <td> <p>Source quality</p> </td> <td> <p>Incidents are ranked on a scale from 1-5 based on the source(s) of information available. Incidents ranked as level 1 are based on information from only one media source. Incidents ranked as level 2 are based on information from uncorroborated eyewitness accounts or data from survey respondents. Incidents ranked as level 3 are based on information from multiple media reports, while level 4 incidents are based on information from at least one NGO, IGO, or another humanitarian actor with direct knowledge of the incident. Incidents ranked at level 5 are based on information from official sources such as coroners, medical examiners, or government officials OR from multiple humanitarian actors.</p> </td> </tr> <tr> <td> <p>Comments</p> </td> <td> <p>Brief description narrating additional facts about the death. If no extra information is available, this is left blank. Not available in the public dataset.</p> </td> </tr> </tbody> </table> Russian 0 characters edited Current translation 7 months ago
None String updated in the repository SDG Metadata / 10-7-3 — Russian	English <p>MMP data are managed a team of experts based at IOM’s Global Migration Data Centre. Data cleaning is undertaken at least once annually. Incidents recorded in the MMP database are generally quite timely; however, given the dearth of official information on deaths during migration the database as a whole is both highly incomplete and individual records often have low accuracy, especially in terms of the identities of those who die during migration. </p> Russian 0 characters edited Current translation 7 months ago
None String updated in the repository SDG Metadata / 10-7-3 — Russian	English <p>Data on deaths during migration are fragmented, incomplete and scattered among many different sources. The MMP database provides a global overview of data on migrant fatalities, but it is primarily dependent on secondary sources of information. Information is gathered from diverse sources such as official records – including from coast guards and medical examiners – and other sources such as media reports, non-governmental organizations (NGOs), and surveys and interviews of migrants. The reliability and completeness of data vary greatly from region to region, from country to country and over time. In addition to undercounting the absolute number of deaths which occur during migration, MMP data also lack identifying information in many cases (incl. age, gender, country of origin) which are vital to providing closure to families searching for loved ones lost during migration.</p> <p><a href="#_Table_1:_Missing">Table 1</a> illustrates the wide variety of sources used in the MMP database, and gives some insight into the various advantages and disadvantages of each. For example, some of the data are collected directly from migrants who have survived a deadly incident, typically via NGO/humanitarian actors or surveys of migrants. Eyewitness testimonies are often the only source of information about migrant deaths, especially those which occur on remote routes or in the many areas of the world where no official data on deaths during migration is collected. However, eyewitness testimonies are nearly impossible to verify on remote routes, and there is a small risk of double-counting if migrants report the same incident when asked whether they are aware of a death or disappearance. Data from surveys are similarly invaluable due to the dearth of data on this topic, but are not representative as they typically capture only a small fraction of the total number of people on the move who may have witnessed a death. Similarly, media reports often provide information on migrant deaths that are not available from official sources, but may offer limited or even conflicting information, especially as the investigation and identification of bodies may occur after an initial report. As no State currently produces national-level data on deaths during migration (neither within their own territory nor of their nationals abroad) MMP data only represents documented, verified incidents and is best considered a very conservative estimate of the true number of lives lost during migration.</p> Russian 0 characters edited Current translation 7 months ago

Browse all component changes