1 / 16

use cases

use cases. A tool to create Linked Data providers and consumers. Valeria Pesce Global Forum on Agricultural Research (GFAR). The AgriDrupal community.

linus-vasquez
Download Presentation

use cases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. use cases A tool to create Linked Dataproviders and consumers Valeria Pesce Global Forum on Agricultural Research (GFAR)

  2. The AgriDrupal community • The AgriDrupal community is made up of people who work in the community of agricultural information management specialists and have been experimenting with IM solutions with the Drupal CMS • The community interacts using the AIMS community platform: http://aims.fao.org/community/home

  3. AgriDrupal solutions and “demo tool” • One or more “reference” installations of AgriDrupal including all or only selected functionalities can be made available • for testing purposes • for adoption by Institutions looking for a full-fledged tool for integrated information management and dissemination

  4. Drupal as a LOD provider 1. Content types, metadata and RDF • In-built capacity to treat any kind of user-defined content type: from simple web pages to events, contacts, bibliographical records or any custom content types • For each content type, a suitable metadata set can be designed with no programming • Each content type can be mapped to an RDF class from any vocabulary; each field in the metadata set can be mapped to an RDF property from any vocabulary • Content types = classes. Nodes = entities, instantiation of content types / classes. Nodes’ URLs are the entities’ URIs. • All structured contents - Custom RDF vocabularies- URIs

  5. Mapping metadata to RDF vocabularies

  6. Using recommended vocabularies Example: recommendations for AGRIS (from Imma’s slides) Implement the recommendations in Drupal Analyze this decisional workflow, apply the scenario you prefer custom content model mapping of fields/elements to RDF properties

  7. Drupal as LOD provider 2. Views and SPARQL engine • Drupal has the in-built capacity to provide any number and type of views over the stored contents: from simple lists of news to tables with selected columns to calendars to feeds and XML/RDF or Json exports • Drupal can make available a SPARQL engine to query the whole triple store • RDF outputs available in different notations (e.g. RDF/XML for Agris)- RDF store exposed through a SPARQL engine

  8. Example of view: RDF feed

  9. Drupal as a SPARQL endpoint Drupal website Query run on a Drupal website from a Virtuoso test environment at http://demo.openlinksw.com/sparql_demo/ RDF triples SPARQL endpoint

  10. Drupal as LOD provider • External authority control: • web services and SPARQL queries can be used to access external authority control sources; • URIs can be stored in the system together with useful literal values in different fields; • Links to external resources with URIs already in the system- RDF outputs include external URIs

  11. Authority control: authors Internal authority control Drupal data entry Search and reference Create and reference

  12. Authority control: journals Next step: shared authority records Workbenchweb services Drupaldata entry Now: internal authority records

  13. Authority control: subject: Agrovoc Drupal data entry Agrovoc web services client popup >> click << Drupal search interface

  14. Drupal as LOD consumer 2. Feed aggregation and SPARQL views • Drupal can aggregate RDF feeds and store their items even with full custom metadata • Drupal can run SPARQL queries on remote endpoints and display the results • Aggregated RDF records can be either stored or displayed on the fly- Dynamic SPARQL queries can be run on any SPARQL engine

  15. Drupal as a SPARQL client Remote SPARQL engine Drupal Views interface: SPARQL View plugin Drupal block

  16. use cases Thank you

More Related