TREC
Event series Rating
| median | worst |
|---|---|
|
|
List of all ratings can be found at TREC/rating
Excel series Import and Export
| TREC | |
|---|---|
Text Retrieval Conference
| |
Categories: Data mining
| |
| DblpSeries: | trec |
| Bibliography: | dblp.uni-trier.de/db/conf/trec/ |
| Avg. acceptance rate: | 0 |
| Avg. acceptance rate (last 5 years): | 0 |
| Table of Contents | |
Text Retrieval Conference (TREC) has an average acceptance rate of 0% (last 5 years 0%).
Events
There are 26 events of the series TREC known to this wiki: TREC 1992, TREC 1993, TREC 1994, TREC 1995, TREC 1996, TREC 1997, TREC 1998, TREC 1999, TREC 2000, TREC 2001, TREC 2002, TREC 2003, TREC 2004, TREC 2005, TREC 2006, TREC 2007, TREC 2008, TREC 2009, TREC 2010, TREC 2011, TREC 2012, TREC 2013, TREC 2014, TREC 2015, TREC 2016, TREC 2020
| OrdinalThis property of the datatype Number represents the ordinal number of an event within an event series. Thereby it informs about the age of an event series. This property is not needed for the DOI registration process via DataCite and is optional. | Year | FromThis property is of the datatype Date and it is being used to provide the start date of an academic event or a project.</br>This property is aligned with icaltzd:dtstart. It is a mandatory property when describing an academic event and it is needed for the DOI registration process via DataCite. | ToThis property is of the datatype Date and it is being used to provide the end date of an academic event or a project.</br>This property is aligned with icaltzd:dtend.</br>It is a mandatory property when describing an academic event and it is needed for the DOI registration process via DataCite. | CityThe property Has location city can be used to specify the city where a street, building, event, etc. is located in.</br>It is of the datatype Page and a special case of the Property:Located in. Other properties for specifying locations are: property:Has location country, property:Has location state and property:Has location address.</br>When specifying the city in which an academic event takes or took place, using this property is not needed for the DOI registration process via DataCite but strongly recommended. | CountryThe property Has location country is used to describe the country where something is located in.</br>It is of the datatype Page and a special case of the Property:Located in. Other properties for specifying locations are: property:Has location city, property:Has location state and property:Has location address.</br>When specifying the country in which an academic event takes or took place, using this property is not needed for the DOI registration process via DataCite but strongly recommended. | presence | HomepageThis property is of the datatype URL and it is being used to provide the official website of an academic event or an event series.</br>It is a recommended property when describing an academic event or event series and it is not needed for the DOI registration process via DataCite. | TibKatId | GNDThis property of the datatype External identifier is used to provide the identifier with which an entity is indexed in the Integrated_Authority_File (GND). Its external formatter URI is http://d-nb.info/gnd/$1.</br>In Open Research it is mostly used to identify an academic event or event series within the GND. </br>The use of this property is optional.</br>It is not necessary for the DOI registration process via DataCite. | dblpThis property of the datatype External identifier is used to provide the identifier with which an entity is indexed in dblp. Its external formatter URI is https://dblp2.uni-trier.de/db/conf/$1.</br>In Open Research it is mostly used to identify an academic event within dblp. </br>The use of this property is optional. It is not necessary for the DOI registration process via DataCite. | WikiCFPThis property of the datatype External identifier is used to provide the identifier with which an entity is indexed in WikiCFP. Its external formatter URI is http://www.wikicfp.com/cfp/servlet/event.showcfp?eventid=$1.</br>In Open Research it is used to identify an academic event or event series within WikiCFP. </br>The use of this property is optional. It is not necessary for the DOI registration process via DataCite. | WikidataThis property of the datatype External identifier is used to provide the identifier with which an entity is indexed in Wikidata. Its external formatter URI is https://www.wikidata.org/entity/$1.</br>In Open Research it is mostly used to identify an academic event or event series within Wikidata. </br>The use of this property is optional. It is not necessary for the DOI registration process via DataCite. | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TREC 2020 | 2020 | Nov 18 | Nov 20 | US/MD/Gaithersburg | US | https://trec.nist.gov/pubs/call2020.html | |||||||
| TREC 2016 | 2016 | Nov 15 | Nov 18 | US/MD/Gaithersburg | US | ||||||||
| TREC 2015 | 2015 | Nov 17 | Nov 20 | US/MD/Gaithersburg | US | ||||||||
| TREC 2014 | 2014 | Nov 19 | Nov 21 | US/MD/Gaithersburg | US | ||||||||
| TREC 2013 | 2013 | Nov 19 | Nov 22 | US/MD/Gaithersburg | US | ||||||||
| TREC 2012 | 2012 | Nov 6 | Nov 9 | US/MD/Gaithersburg | US | ||||||||
| TREC 2011 | 2011 | Nov 15 | Nov 18 | US/MD/Gaithersburg | US | ||||||||
| TREC 2010 | 2010 | Nov 16 | Nov 19 | US/MD/Gaithersburg | US | ||||||||
| TREC 2009 | 2009 | Nov 17 | Nov 20 | US/MD/Gaithersburg | US | ||||||||
| TREC 2008 | 2008 | Nov 18 | Nov 21 | US/MD/Gaithersburg | US | ||||||||
| TREC 2007 | 2007 | Nov 5 | Nov 9 | US/MD/Gaithersburg | US | ||||||||
| TREC 2006 | 2006 | Nov 14 | Nov 17 | US/MD/Gaithersburg | US | ||||||||
| TREC 2005 | 2005 | Nov 15 | Nov 18 | US/MD/Gaithersburg | US | ||||||||
| TREC 2004 | 2004 | Nov 16 | Nov 19 | US/MD/Gaithersburg | US | ||||||||
| TREC 2003 | 2003 | Nov 18 | Nov 21 | US/MD/Gaithersburg | US | ||||||||
| TREC 2002 | 2002 | Nov 19 | Nov 22 | US/MD/Gaithersburg | US | ||||||||
| TREC 2001 | 2001 | Nov 13 | Nov 16 | US/MD/Gaithersburg | US | ||||||||
| TREC 2000 | 2000 | Nov 13 | Nov 16 | US/MD/Gaithersburg | US | ||||||||
| TREC 1999 | 1999 | Nov 17 | Nov 19 | US/MD/Gaithersburg | US | ||||||||
| TREC 1998 | 1998 | Nov 9 | Nov 11 | US/MD/Gaithersburg | US | ||||||||
| TREC 1997 | 1997 | Nov 19 | Nov 21 | US/MD/Gaithersburg | US | ||||||||
| TREC 1996 | 1996 | Nov 20 | Nov 22 | US/MD/Gaithersburg | US | ||||||||
| TREC 1995 | 1995 | Nov 1 | Nov 3 | US/MD/Gaithersburg | US | ||||||||
| TREC 1994 | 1994 | Nov 2 | Nov 4 | US/MD/Gaithersburg | US | ||||||||
| TREC 1993 | 1993 | Aug 31 | Sep 2 | US/MD/Gaithersburg | US | ||||||||
| TREC 1992 | 1992 | Nov 4 | Nov 6 | US/MD/Gaithersburg | US |
Submission/Acceptance
Locations
The Text REtrieval Conference (TREC), co-sponsored by the National Institute of Standards and Technology (NIST) and U.S. Department of Defense, was started in 1992 as part of the TIPSTER Text program. Its purpose was to support research within the information retrieval community by providing the infrastructure necessary for large-scale evaluation of text retrieval methodologies. In particular, the TREC workshop series has the following goals:
- to encourage research in information retrieval based on large test collections;
- to increase communication among industry, academia, and government by creating an open forum for the
exchange of research ideas;
- to speed the transfer of technology from research labs into commercial products by demonstrating
substantial improvements in retrieval methodologies on real-world problems; and
- to increase the availability of appropriate evaluation techniques for use by industry and academia,
including development of new evaluation techniques more applicable to current systems.
TREC is overseen by a program committee consisting of representatives from government, industry, and academia. For each TREC, NIST provides a test set of documents and questions. Participants run their own retrieval systems on the data, and return to NIST a list of the retrieved top-ranked documents. NIST pools the individual results, judges the retrieved documents for correctness, and evaluates the results. The TREC cycle ends with a workshop that is a forum for participants to share their experiences.
This evaluation effort has grown in both the number of participating systems and the number of tasks each year. Ninety-three groups representing 22 countries participated in TREC 2003. The TREC test collections and evaluation software are available to the retrieval research community at large, so organizations can evaluate their own retrieval systems at any time. TREC has successfully met its dual goals of improving the state-of-the-art in information retrieval and of facilitating technology transfer. Retrieval system effectiveness approximately doubled in the first six years of TREC.
TREC has also sponsored the first large-scale evaluations of the retrieval of non-English (Spanish and Chinese) documents, retrieval of recordings of speech, and retrieval across multiple languages. TREC has also introduced evaluations for open-domain question answering and content-based retrieval of digital video. The TREC test collections are large enough so that they realistically model operational settings. Most of today's commercial search engines include technology first developed in TREC.
A TREC workshop consists of a set tracks, areas of focus in which particular retrieval tasks are defined. The tracks serve several purposes. First, tracks act as incubators for new research areas: the first running of a track often defines what the problem really is, and a track creates the necessary infrastructure (test collections, evaluation methodology, etc.) to support research on its task. The tracks also demonstrate the robustness of core retrieval technology in that the same techniques are frequently appropriate for a variety of tasks. Finally, the tracks make TREC attractive to a broader community by providing tasks that match the research interests of more groups.
Each track has a mailing list. The primary purpose of the mailing list is to discuss the details of the track's tasks in the current TREC. However, a track mailing list also serves as a place to discuss general methodological issues related to the track's retrieval tasks. TREC track mailing lists are open to all; you need not participate in TREC to join a list. Most lists do require that you become a member of the list before you can send a message to it.
The set of tracks that will be run in a given year of TREC is determined by the TREC program committee. The committee has established a procedure for proposing new tracks.