v2.3.0

[MBueschelberger]

With this PR, we will be able to:

• also allow strings as value types in quantity graphs, but raise a warning if it cannot be converted into float or int
• add alias choices for several field names
• fix the behaviour if the retrieved value from the mapping is None or np.nan
• also allow quantity graphs / property graph in the mappings in case of custom relations.

---

In the following, you will find a test sceanrion in case of an quantity graph / property graph in the custom relations mapping.

The data may look like this:

data = {
    "data": [
        {
            "name": "specimen_1",
            "youngs_modulus": 100,
            "material": "material_1",
        },
        {
            "name": "specimen_2",
            "youngs_modulus": "200-300", # note this cannot be converted into float/int
            "material": "material_2",
        },
    ]
}

The mapping looks like this

mapping = [
    {
        "iri": "https://w3id.org/steel/ProcessOntology/Specimen",
        "suffix": "name",
        "source": "data[*]",
        "suffix_from_location": True,
        "custom_relations": [
            {
                "object_location": "youngs_modulus",
                "relation": "https://w3id.org/steel/ProcessOntology/hasYoungsModulus",
                "object_type": {
                    "iri": "https://w3id.org/steel/ProcessOntology/YoungsModulus",
                    "unit": "GPa",
                },
            },
            {
                "object_location": "material",
                "relation": "https://w3id.org/steel/ProcessOntology/hasMaterial",
                "object_type": {
                    "iri": "https://w3id.org/steel/ProcessOntology/Material",
                    "value_relation": "https://w3id.org/steel/ProcessOntology/hasIdentifier",
                },
            },
            {
                "object_location": "name",
                "relation": "https://w3id.org/steel/ProcessOntology/hasIdentifier",
            },
        ],
    }
]

The expected graph will look like this:

@prefix ns1: <https://w3id.org/steel/ProcessOntology/> .
@prefix ns2: <http://qudt.org/schema/qudt/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix: ex: <https://example.org#> .

ex:specimen_1 a ns1:Specimen ;
    ns1:hasIdentifier "specimen_1"^^xsd:string ;
    ns1:hasMaterial ex:Material_specimen_1 ;
    ns1:hasYoungsModulus ex:YoungsModulus_specimen_1 .

ex:specimen_2 a ns1:Specimen ;
    ns1:hasIdentifier "specimen_2"^^xsd:string ;
    ns1:hasMaterial ex:Material_specimen_2 ;
    ns1:hasYoungsModulus ex:YoungsModulus_specimen_2 .

ex:Material_specimen_1 a ns1:Material ;
    ns1:hasIdentifier "material_1"^^xsd:string .

ex:Material_specimen_2 a ns1:Material ;
    ns1:hasIdentifier "material_2"^^xsd:string .

ex:YoungsModulus_specimen_1 a ns1:YoungsModulus ;
    ns2:hasUnit "http://qudt.org/vocab/unit/GigaPA"^^xsd:anyURI ;
    ns2:value 100 .

ex:YoungsModulus_specimen_2 a ns1:YoungsModulus ;
    ns2:hasUnit "http://qudt.org/vocab/unit/GigaPA"^^xsd:anyURI ;
    ns2:value "200-300"^^xsd:string .

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
data2rdf
__init__.py	5	0	100%
config.py	26	1	1	96%
utils.py	8	1	1	88%
warnings.py	2	0	100%
data2rdf/models
__init__.py	3	0	100%
base.py	54	5	5	91%
graph.py	116	7	7	94%
mapping.py	45	1	1	98%
utils.py	58	14	14	76%
data2rdf/modes
__init__.py	4	0	100%
data2rdf/parsers
__init__.py	6	0	100%
base.py	135	11	11	92%
csv.py	168	20	20	88%
excel.py	183	17	17	91%
json.py	216	37	37	83%
utils.py	90	10	10	89%
data2rdf/pipelines
__init__.py	2	0	100%
main.py	82	9	9	89%
data2rdf/qudt
__init__.py	0	0	100%
utils.py	42	12	12	71%
TOTAL	1245	145	88%

Tests	Skipped	Failures	Errors	Time
120	0 💤	0 ❌	0 🔥	2m 57s ⏱️