SC2 Workshop 1: A global linked and open data infrastructure for agricultural development

A global linked and open data infrastructure for agricultural

development Valeria Pesce

Global Forum on Agricultural ResearchFood and Agriculture Organization of the United

nations

BDE proposed infrastructure

• ICT infrastructure• Computing infrastructure

• One re-depolyable generic infrastructure, n “Domain-specific Big Data Integrator Instances”

• These tools may all be thought of as generic tools and they will be available as options in the generic plat-form. However, individual domains are likely to need more specialised tools and datasets

The ag-data context• Different actors have built several infrastructural

components over the years under the umbrellas of different initiatives and projects

• Mostly vocabularies, authority data, online tools, APIs; mostly for non-big data

• Little work on computational services

IGAD group

“Positioning” this infrastructure within the ag-data context

• Open data for agricultural development is big and non-big data

• Beyond all the additional features (the 3 Vs) of being “big”, big data still also have the same features as other non-big data

• A dedicated big data infrastructure should be aware of and interlink with other existing infrastructural elements in a distributed and inter-linked ecosystem

5

Re-usablesoftware

Interoperable vocabularies

Authority

Some existing infrastructural components

Registries

6



Authority

Registries

Re-usable software

Registries

Description vocabulariesDarwin CoreINSPIREDCATetc.

7

Interoperable vocabulariesRe-usable

software


Registries

AGROVOCNALTGACSGene OntologySoil TermsLocal KOSsControlled listsetc.

Description vocabularies

KOSs

Darwin CoreINSPIREDCATetc.

8


software


Registries



KOSs


9


software

AuthorityPersonsInstitutionsProjectsetc.

Auth

ority


APIs

Registries



KOSs


10


software

Vocabulary toolsVocBench


Auth

ority

Vocabulary APIsAgrovoc WSClimate Tagger


APIs

Registries



KOSs


11


software

Vocabulary toolsVocBench


Auth

ority



APIs

Registries



KOSs


12


software


Auth

ority


Cloud / SaaS toolsVocabulary tools

CM / DM tools

VocBench


APIs

Registries



KOSs


13


software


Auth

ority



CM / DM tools

VocBench

Processing APIsagINFRABioCatalogue

APIs



APIs

Registries



KOSs


14


software


Auth

ority



CM / DM tools

VocBench


APIs


Datasets

Vocabularies

APIs


APIs

Registries

Cloud / SaaS tools

Shared URIs



KOSs


15


Datasets

Vocabularies

APIs

Re-usable software

Vocabulary tools

CM / DM tools

VocBench


Auth

ority


APIs



APIs

Registries

Cloud / SaaS tools

Shared URIs

Grid jobsGrid workflows



KOSs


16


Datasets

Vocabularies

APIs

Re-usable software

Vocabulary tools

agINFRA

CM / DM tools

VocBench


Auth

ority


APIs



APIs

Registries

Cloud / SaaS tools

Shared URIs




KOSs


17


Datasets

Vocabularies

APIs

Re-usable software

Vocabulary tools

agINFRA

CM / DM tools

VocBench


Auth

ority


APIs



BDE software stack

BDE in context

• An infrastructure that minimises the disruption to current workflows

• An adaptable, easy to deploy and use solution, which will allow the interest-ed user groups and stakeholders to extend their Big Data solutions or introduce Big Data technology to their business processes

Big Data Aggregator platform

APIs

Registries

Cloud / SaaS tools

Shared URIs

Infrastructural components




KOSs


20


Datasets

Vocabularies

APIs

Re-usable software

Vocabulary tools

agINFRA

CM / DM tools

VocBench


Auth

ority


APIs


BDE platform

BDE platform in ag-data infrastructure

APIs

Cloud / SaaS tools

Shared URIs

Re-usable software

Vocabulary tools

CM / DM tools

VocBench


APIs


Registries


agINFRA Inte

rope

rabl

e vo

cabu

larie

sAu

thor

ity

BDE approach• One re-depolyable generic infrastructure, n “Domain-specific Big

Data Integrator Instances”• Provide a comprehensive test-beds for the evaluation of the BDE

Aggregator Platform according to the requirements of the respective societal domain;

• Carefully select pilot use cases, across different domains, so that they are adequate test beds but self-sustainable systems beyond the action’s end;

• These tools may all be thought of as generic tools and they will be available as options in the generic plat-form. However, individual domains are likely to need more specialised tools and datasets

Conclusion

• We would like the new big data infrastructure to be interlinked with existing infrastructural components

Thank you

Valeria PesceGlobal Forum on Agricultural Research

Food and Agriculture Organization of the United nations

Data & Analytics

SC2 Workshop 1: A global linked and open data infrastructure for agricultural development