If you wish to publish your population data in a journal and in the YHRD and a YHRD accession number for publication is requested, we need information on the competence and proficiency of your lab concerning Y chromosome typing. You have different options:
1) Submit a document on a passed forensic proficiency test which includes YSTRs (e.g. GEDNAP, GHEP-ISFG, GITAD, CTS, SERI, IQAS or others).
If you have not yet participated in a forensic proficiency test, please see the following links to get started:
2) A laboratory accreditation certificate stating the labs competence in forensic DNA typing methods issued by a national accreditation service.
3) Whether you belong to an academic institution or to a forensic laboratory we require original electropherograms (epg) in order to guarantee the quality and concordance of the analysis method:
- an epg (PDF file) with the positive kit control (PTC)
- an epg (PDF file) with the negative kit control (NTC)
- an epg (PDF file) with the full allelic ladder provided by the kit supplier
The files must be provided along with your data table(s).
When you prepare population data for submission/publication, please make sure your submissions comply with the Updated guidelines on Y-STR Analysis of the International Society for Forensic Genetics - ISFG, The guidelines of the journal International Journal of Legal Medicine - IJLM and the Guidelines of the Journal Forensic Science International:Genetics You are welcome to use our example file to prepare your submission file.
You or your lab has to analyze the population samples. It is not possible to submit data of another lab or collected data found somewhere on the internet.
Check your population data using the YHRD Data File Validator and review all failures, errors and warnings.
Please send an email to Lutz Roewer (email@example.com) with the following data and information:
- Your certificate of a passed forensic proficiency test which includes YSTRs (GEDNAP, GHEP-ISFG, GITAD, CTS, SERI, IQAS and maybe others) and/or a laboratory accreditation document
- In case of already published population data, attach your publication or provide a link
- Information on your population data:
- Corresponding author (and coautors if any)
- Corresponding authors institution, address, email and phone and/or fax number
- Description of the population including geographic positioning (latitude/longitude), language and/or ethnic group if available
- Please provide information/confirmation on non-standard alleles (easily tracked if you are using the YHRD Data File Validator)
Please make sure that your submission table(s) has no gaps and all alleles for the concerned haplotype format are unequivocally called. Please use the following notation of non-standard alleles:
- Null allele = 0
- intermediate allele = x.1, x.2, x.3 and so on
- alleles at multi-copy loci = x,y or x,y,z and so on; please use only length information not peak height or area for your judgement; an exception is DYS385ab where at least two alleles need to be entered (e.g. “14” will be denoted as “14, 14”)
In case of gaps (e.g. due to degradation or insufficient DNA quantity) the haplotype will be skipped or reduced to the next lower resolution format.
You’ll receive an invitation and a link to submit your data by email. Please follow the steps and review all information given there until your file has been uploaded successfully.
As soon as the next release of the YHRD is published, you’ll be notified.
Bugs & Issues
If you feel that you’ve found a bug please first search for similar bugs and in case you didn’t find anything related to your experience please file a bug report. We are happy to receive your proposals of missing and/or new features as well!
Suggestions for Improvement
If you feel that a certain feature is missing or could be improved, please send a detailed email either to Sascha Willuweit (sascha[dot]willuweit[at]charite[dot]de) or to Lutz Roewer (lutz[dot]roewer[at]charite[dot]de) describing your thoughts. We’ll come back to you. But be aware that we’re focusing mostly on forensic users, meaning that fetching observed haplotype frequencies and derived values measuring the rareness is the main purpose here.