DOI: 10.5281/zenodo.3746595
title: MESINESP: Medical Semantic Indexing in Spanish - Development dataset

description: <em><strong>Please use the MESINESP2 corpus (the second edition of the shared-task) since it has a higher level of curation, quality and is organized by document type (scientific articles, patents and clinical trials).</strong></em> <strong>Introduction</strong> The Mesinesp (Spanish BioASQ track, see https://temu.bsc.es/mesinesp) development set has a total of 750 records indexed manually by seven experienced medical literature indexers. Indexing is done using <em>DeCS codes, a sort of Spanish equivalent to MeSH terms</em>. Records were distributed in a way that each article was annotated, at least, by two different human indexers. The data annotation process consisted in two steps: Manual indexing step. DeCS codes were manually assigned to each record following the DeCS manual indexing guidelines. Manual validation and consensus. The joined set of manually indexed DeCS codes generated by both indexers were manually revised and corrections were done. These annotations were analyzed, resulting in an agreement using the Jaccard index. Records consisted basically in medical literature abstracts and titles from the IBECS and LILACS databases. <strong>Zip structure</strong><br> The zip file contains two different development sets: <em>Official development set</em>, which has the union of the annotations, with an agreement of macro = 0.6568 and micro = 0.6819. This set is composed by all the different (unique) DeCS codes that have been added by any annotator for each document; and <em>Core-descriptors development set</em>, which has the intersection of the annotations, with an agreement of macro = 1.0 and micro = 1.0. This set is composed of the common DeCS codes that have been added by two or more annotators for each document. <strong>Corpus format</strong> Each dataset is a JSON object with one single key named "articles", which contains a list of documents. So, the raw format of the file is one line per document plus two additional lines (the first and the last) to enclose that list of documents and the expected type of data is as follows: <pre><code class="language-json">{"articles":[ {"abstractText":str,"db":str,"decsCodes":list,"id":str,"journal":str,"title":str,"year":int}, ... ]}</code></pre> To clarify, the order of appearance of the fields in each document is as follows (note that this example it is pretty printed for readability purposes): <pre><code class="language-json">{ "articles": [ { "abstractText": "Content of the abstract", "db": "Name of the source database", "decsCodes": [ "code1", "code2", "code3" ], "id": "Id of the document", "journal": "Name of the journal", "title": "Title of the document", "year": 2019 } ] }</code></pre> Note: The fields "db", "journal" and "year" might be null. Copyright (c) 2020 Secretaría de Estado de Digitalización e Inteligencia Artificial
description: Funded by the Plan de Impulso de las Tecnologías del Lenguaje (Plan TL).
description: {"references": ["Krallinger M, Krithara A, Nentidis A, Paliouras G, Villegas M. BioASQ at CLEF2020: Large-Scale Biomedical Semantic Indexing and Question Answering. InEuropean Conference on Information Retrieval 2020 Apr 14 (pp. 550-556). Springer, Cham."]}