terminusdb
Checking if all Python tutorials work in the latest version
We have made our TerminusDB more powerful and ready for sharing data and collaborating on Hub. It means that the old python code may not work in the latest TerminusDB and Python client. 😞 We need people to help to check if the tutorial codes are good 👍🏻 Could you help us out? 🙏🏻
-
Install the latest versions of TerminusDB following the instructions here. You will need to have Docker. 🐳
-
Create a new Python environment (optional), install the Python client (
pip install terminusdb-client[dataframe]) and Jupyter notebook (pip install notebook) -
Pick a tutorial (folder) that you want to test form here: https://github.com/terminusdb/terminus-tutorials
-
Check the comment below that no one is working on it, then you can claim it to yours. Make sure you let people know by writing a comment 💬
-
If there's any problem, open a new issue and let us know. In the issue, please stay clearly which versions of the database and the client you are using (latest as of 4th October 2020 is Terminusdb v3.0.7 and Python client 0.4.0), and the file that fail ❌
-
(optional) update the file and send a PR to close the issue in step 5.
-
If nothing's wrong, comment below to say which file you checked and it's a-okay 👌🏻 Also, stay clearly which versions of the database and the client you are using.
Thanks a lot ☺️
Dublin voting example with python client does not add the csv data to the database. Running the script returns many dicts that include possible error messages in the following format:
"@type":"vio:InstanceCardinalityRestrictionViolation", "vio:cardinality": {"@type":"xsd:string", "@value":"1"}, "vio:message": { "@type":"xsd:string", "@value":"Cardinality does not match for restrction: terminusdb://admin/dublin_voting/schema#similar_to_cardinality"
Thanks Jametron - there was a bug in the schema - it should be max(2) not cardinality(2) - it fails because of self-similarity measures. I fixed the schema now.
