Testing latest method for publishing on JRR
fixed test which failed in local env for missing mocks and getter/setter
testing list and purge
Adapted to gcat API and implemented update
Removed redundant Ignore
Removed dep to gcube registry and ignore integration tests
updated parthenos resolver URL
Let the test compile
Increased major version as we are now using the Parthenos resolver
Fixes https://support.d4science.org/issues/11240#note-27: namespace dnet should not be used. The full namespace URL must be used when adding triples, otherwise it will be just a string, not a real name under the namespace as expected.
Based on the sparql templates e55type is a string, not a resource. Getter method updated accordingly, but we still support e55type resource just in case.
Updated to gcube registry 2.0.0-SNAPSHOT
Fixes #11240#note-21: changed names of provenance graph and properties to be URLs instead of plain strings.
Double check tests after latest updates
Do not load rdfs from remote URLs for testing and removed unused method.
Do not load rdfs from URLs for testing
throws exception if the data source name cannot be mapped into a ckan org by the CKANUtils class.
Removed tests for CRUD ops on groups
Fixed web param name and ignoring webmvc test
timeout is a string
Ignore integration test
Added new timeout parameter for anytime query
Removed test for deprecated method
updated call for deleting resources from the registry
Removed/deprecated unused methods
According to george's feedback, base types to be considered for the JRR are {Project, Service, Actors, Datasets, Software, Physical Collections, Standards} i.e. {PE35_Project, PE1_Service, E39_Actor, PE18_Dataset, D14_Software, E78_Collection, E29_Design_or_Procedure)....
An example with the OAI header
Test collection sparql template
Testing regexp for catalogue
New methods to get subjects with pagination given a datasource API
changes based on update about catalogue group
Changes based on updates about catalogue group
Use latest crmdig in test
No sparql template for E55_Type
fixed timespan for projects
Test with metashare service
better mapping to ckan for Datasets
Better mapping Projects into the catalogue
removed todos and namespaces for test query
Additional testing, especially for groups
Another test
Additional tests for catalogue groups
ignore integration test
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
Test adapted to previous commit
removed useless resource
Ignore tests that require a running virtuoso on localhost
Added @RunWith(JUnit4.class)
Deleted wrong RIOT writer
Cleanup after creating resources
fixed test
Annotation for tests
test to ensure the sparql template are well formed and once instantiated they are correctly processed by virtuoso
No need dedicated resource file in test to test the template loading
test
Registering providers as catalogue groups
Debugging "org.apache.jena.riot.RiotNotFoundException: Not found" and related(?) parsing issue
I think we must use an InfModel to process the rdf before registering it
Because of https://support.d4science.org/issues/11466, let's not throw exception, but let's try to continue, if possible.Purge method implemented and tested
without testing a woman can die
Debugging for unexpected NPE
Testing RecordParserHelper
Extract the rdf block from the record submitted for registration
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.
testing template loading
Fixed compilation for test
Fixed expected value
Response samples from the catalogue
Testing the registry library
ByPass QueryBuilder, otherwise the virtuoso pragma are not parsable
Playing with inference rules on the remote sparql endpoint
throws exception
Refactoring and deprecation for registration on catalogue and registry
testing
Updated test
Testing RDF XML serialization
API that read from Virtuoso
Testing Virtuoso DESCRIBE remote queries.
Creating json for the CKAN Catalogue
Fixed after refactoring classes
Sleep to make the test work with async controller
Async implementation of the controller
Test for illegal chars
Fixed virtuoso drop and added test
Ignoring old test to be revised
feeding the registry with resources and relationships
More mapping to gcube resources and facets
Refactoring
First mapping for services and tests
Playing with Jena API
Ignore test as it requires a running virtuoso server
API for storing on virtuoso
keep playing with virtuoso
JobNodes to work with Virtuoso