D-Net

better mapping to ckan for Datasets

Mapping to ckan refined for PE1_Services

Better mapping Projects into the catalogue

Also query for maintained stuff + formatting

Updated crmdig namespace

Assuming prefixes are defined at virtuoso side.

Based on FORTH feedback there are no direct rels between entities and the provider apart from services.

Added provider label

Included PP2_provided_by in sparql template for actors

The activitytype must be taken explicitly by URI prefix on types

The availability type must be taken explicitly by URI prefix on types

Type and Ting should not be queried

Added crm:P2_has_type for all sparql query templates

Yes, let's use union everywhere

Looks like using UNION is much more performant than using OPTIONAL. See http://www.snee.com/bobdc.blog/2014/10/dropping-optional-blocks-from.html

Using specific queries for Software and Dataset: the one for DigitalObject has been deleted as it could not be executed because of timeout exception during tests. I do not want to run such heavy query on the production virtuoso

added missing namespace

removed wrong } in service sparql template

Let's try to get the providers for all types of resources

provider must come with at least the title

Let's get also the maintaining RI as provider (so they will also be added as groups)

Added missing dots in sparql templates

fixed sparql template

Resolved TODOs in sparql query templates

removed duplicate line and re-order for haspart rels

curation plan in sparql template

subjects and coverages in sparql template

provided service

actor members

has_maintaining_team with optional contact points

PP1 currently offers

Curates relationships

curation relationships

Fixed hosted_by

formatting

Thanks to sprql template activitytype can be accessed as literal

Thanks to sparql template service competence can be accessed as a simple label

Optional rdfs:label in sparql templates

optional description in sparql templates

Because of how we construct the RDF that we read from Virtuoso (see sparql templates), the title is always a literal.

resolved TODOs

Enrich the values to add to a resource in the catalogue

Can't use jena Query because does not support inference rule, can't use jena HttpEngine because it does not support long queryif we do not use Query: hence let's query with handmade post request to the sparql endpoint.

sparql queries are now freemarker templates where the subjectURL can be injected

Comments in sparql are identified by #, not //

Added declaration to use inference rules

logging jena package

Additional methods needed by the JRR publishing workflow

Can't find a way to use the DEFINE virtuoso pragma using the jena connector.

SPARQL queries

SPARQL queries that will be used to get the info for the JRR and catalogue

instructions to create inference rule based on parthenos model

Let's throw exceptions!

openaire exporter package is not applicable here :-)

Updated properties

Added client for CKAN Catlaogue and refactoring

Async implementation of the controller

Added properties for gcube registry connection

Gcube resource json example from luca

getting ready to use the GCube Parthenos Registry

API for storing on virtuoso

keep playing with virtuoso

JobNodes to work with Virtuoso

VirtuosoClient and some tests assuming there is a local virtuoso server (hence ignored)

First tests with Virtuoso.

project structure