Skip to content
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

Closed
wants to merge 18 commits into from

Conversation

markdoerr
Copy link
Contributor

No description provided.

@dalito
Copy link
Member

dalito commented Feb 21, 2024

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.

@markdoerr
Copy link
Contributor Author

Hi @dalito,
I am puzzled - I thought, I used the current template from your template directory ...
anyway, I will change the version and re-submit ...

@dalito
Copy link
Member

dalito commented Feb 21, 2024

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.

@markdoerr
Copy link
Contributor Author

yes, true, @dalito ,
but for this test, I re-wrote the demo in the recent template provided by the repo ...
anyway, I made a new one and submitted it...

@markdoerr
Copy link
Contributor Author

@dalito,
there is some issue with the URI parsing:

        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  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)

@dalito
Copy link
Member

dalito commented Feb 21, 2024

There are some small issues:

Please find attached the fixed xlsx: biocatalysis_demo.xlsx

@markdoerr
Copy link
Contributor Author

Hi @dalito,
where is this URI https://example.org/voc4cat_biocatalysis/ in the pipeline error message coming from ?

@dalito
Copy link
Member

dalito commented Feb 21, 2024

In the pipeline we validate the URIs used against what is configured in IDrange.toml (in upstream main) to detect if someone changed the URIs, The config has

[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 https://example.org/voc4cat_biocatalysis/ or I can change IDrange.toml to w3id.org if you prefer that.

@markdoerr
Copy link
Contributor Author

I see, @dalito , :)
If you do not mind, please change it in the idrange.toml - the w3c IRI looks more realistic...

@dalito
Copy link
Member

dalito commented Feb 21, 2024

Done.

I saw that in the concept scheme sheet you have https://w3id.org/nfdi4cat/voc4cat_biocat: (with colon at the end). For full URIs a colon at the end is not required (I expect another validation error). Only CURIES need a colon v4c-bc: to be recognized correctly.

@markdoerr
Copy link
Contributor Author

I see, I will fix it an re-submit ...

@markdoerr
Copy link
Contributor Author

Hi @dalito ,
... I think, Fort Knox is easier to enter ... ;)
do you quickly see, what is going wrong now ?

@dalito
Copy link
Member

dalito commented Feb 21, 2024

In concept scheme sheet add https://w3id.org/nfdi4cat/voc4cat_biocat/ as Vocabulary IRI. (this cell may not be empty)

@markdoerr
Copy link
Contributor Author

sorry, this was a bug of OpenOffice - it somehow dropped my corrections ...

@dalito
Copy link
Member

dalito commented Feb 21, 2024

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 remote: Permission to LARAontologies/voc4cat-playground.git denied to github-actions[bot]. has to do with the missing right "Allow edits by maintainers" on this PR.

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.

@dalito
Copy link
Member

dalito commented Feb 21, 2024

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?

@markdoerr
Copy link
Contributor Author

@dalito , no I do not see a button to allow edits by the maintainer.

I will make a new PR.

@markdoerr markdoerr closed this Feb 22, 2024
@dalito
Copy link
Member

dalito commented Feb 22, 2024

@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 inbox-excel-vocabs-folder and the IDrange.toml-file in the same way as in CI.
Maybe such script is useful in the future but understanding the exact reason of an error may not always be so straight-forward.

@markdoerr
Copy link
Contributor Author

👍 Very good, @dalito ,
I was about to ask you, if there is something like a pre-check ....
I had to teach the whole day, so I will briefly re-submit tonight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants