Using mostly AGROVOC terms to annotate other semantic resources (hasDomain property)

[jonquet]

This issue is about changing AgroPortal to use mainly AGROVOC to annotate the hasDomain proprety (for submission objects). Note the hasDomain property (for ontology object will stay from a fixed short value set).

Using a unique standard vocabulary to annotate/describe all the ressources in AgroPortal will ease analytics, ressources recommandation and selection.

I have briefly presented the idea to the AGROVOC editorial team which is in principle ok for us to do this.

In fact, many semantic resources are already doing this with AGROVOC as illustrated:

To achieve this we have to:

• [ ] Update the metadata property validator. Related to (other issue to come).
• [ ] Update the edition UI so that the form relies on a autocomplete form based on AGROVOC.
• [ ] Design a specific UI somewhere (new Landscape page?) to visualize the results (relying on the hierachry from AGROVOC.

[jonquet]

@saubin78 opinion?

[saubin78]

Sounds a good idea as Agrovoc is actually largely used in the community. Let's add a couple of items in the task list:

• [ ] map domains used in AP with Agrovoc to check adequacy
• [ ] select a subset of Agrovoc concept to propose to fill the domains metadata.

Relating to item 2, would the "subject" branch of Agrovoc make sense? https://agrovoc.fao.org/browse/agrovoc/en/page/?uri=http%3A%2F%2Faims.fao.org%2Faos%2Fagrovoc%2Fc_330829 or do we need more?