GACS Working Group and GACS Beta

GACS Beta is a multilingual thesaurus resulting from the work the GACS Working Group, active in 2014-2016 and formed by FAO, CABI, and the National Agricultural Library of the USDA (NAL). GACS Beta was released in May 2016.  

 
Starting from April 2017, the work of the GACS Working Group continues as a Working Group within the umbrella of GADAN, with an enlarged membership. Currently, the basic foundational documents for the group are under development: a vision document, a technical workplan and a business model. 
 

The GODAN/GACS Working Group - interoperability and semantics in agriculture

 
The starting point of the GACS working group in 2014 was that each organization was using different thesauri to index their documents, and so creating information silos, despite a large overlap in their contents. For this reason, they explored the possibility of identifying a set of concepts common to the three thesauri, for the purpose of improving semantic interoperability, facilitate search across databases, and achieve efficiencies of scale.
Now, in 2017, the extended group of actors active in the production and use of agricultural data want to support a larger set of use cases related to data interoperability than (textual) documents indexing. 
 

GACS BETA 

The process  - the three organization selected the 10,000 concepts most frequently used in each respective thesaurus. These concepts were algorithmically mapped, mappings were checked by hand, and inconsistencies were resolved by discussion. 
 
The results - GACS Beta resulted in ~15,000 concepts with:
  • - multilingual labels, definitions, scope notes
  • - organized with thematic groups 
  • - URIs with namespace http://id.agrisemantics.org/gacs/
  • - represented in RDF, using the thesauri specific vocabulary SKOS
The editorial policies for GACS Core follow best practices of modern thesaurus design, as reflected in ISO 25964, "Thesauri and interoperability with other vocabularies".  
 

Remarks

Problems resulting from this integration process, such as overlapping labels, have been substantially fixed, though much detailed quality control remains to be done. 
The biggest task remains that of specifying a common hierarchical structure for GACS Core and bringing its concepts, with hierarchical relations inherited from the source thesauri, into compliance.  
 
GACS Beta may evolve with the addition of new concepts, or shrink slightly if core concepts are moved into GACS extension vocabularies, but the concepts listed in GACS Core Beta 3.1 are unlikely to disappear.