-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-Submission of the Demo Biocatalysis Vocabulary #8
Conversation
The version number of the Excel template marks the structure (not formatting). It has to stay at "0.4.3". The version is stored in sheet "Introduction", cell J11. |
Hi @dalito, |
I vaguely remember that you proposed some changes to the template in December and therefore increased the version number. Maybe that is how 0.4.4 got in. |
yes, true, @dalito , |
@dalito, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "pydantic/main.py", line 339, in pydantic.main.BaseModel.__init__
File "pydantic/main.py", line 1100, in pydantic.main.validate_model
File "/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/voc4cat/models.py", line 102, in check_uri_vs_config
iri, *_fragment = values["uri"].split("#", 1) |
There are some small issues:
Please find attached the fixed xlsx: biocatalysis_demo.xlsx |
Hi @dalito, |
In the pipeline we validate the URIs used against what is configured in [vocabs.biocatalysis_demo]
id_length = 7
permanent_iri_part = "https://example.org/voc4cat_biocatalysis/" You can either change the prefix definition (in prefix sheet) to point to |
I see, @dalito , :) |
Done. I saw that in the concept scheme sheet you have |
I see, I will fix it an re-submit ... |
Hi @dalito , |
In concept scheme sheet add |
sorry, this was a bug of OpenOffice - it somehow dropped my corrections ... |
The vocabulary parsing & conversion went fine now! Only the last step the auto-update of the PR-branch failed, which wants to make a commit that removes xlsx and adds ttl-files. I wonder if In nfdi4cat/voc4cat#55 it worked fine a few hours ago but there "Allow edits by maintainers" was activated. If this proofs correct we need to point out to keep "Allow edits by maintainers" activated when submitting a PR. Just to be sure that this is the real reason: Did you change anything in the repository settings of your fork? Reduced action permissions or additional branch protection rules could also cause also the commit failure. |
I think it is not possible to set "Allow edits by maintainers" after PR creation or do you see such option as the PR author? If you can't change it, can you maybe submit a new PR just with the last version of the xlsx file and activate "Allow edits by maintainers" in the new PR? |
@dalito , no I do not see a button to allow edits by the maintainer. I will make a new PR. |
@markdoerr I just added shell scripts for unix (test_xlsx_locally.sh) and windows (test_xlsx_locally.bat) to locally test a vocabulary xlsx-file in the |
👍 Very good, @dalito , |
No description provided.