📝 Change "Children IRIs" to "Parent IRI" in excel table

[schumannj]

Observed in version

No response

Description

Currently it is a bit cumbersome to add new concepts and assign them to the right "Parent IRI". I have to search in the table to find the right parent concept and add the new IRI to a long list of Children IRIs, which is difficult to display in the excel table format.
My Suggestion: Instead of specifying the "Children IRIs" in the excel table, it might be better to specify the "Parent IRI". This should only be one IRI under the new structure guideline, and I can get the right reference URI directly from the website.

[dalito]

Interesting idea and it could make a lot of sense to change now as all new concepts will have a parent in form of a top-level concept. This was not the case when we started...

The change sounds so simple but it affects a lot of code, tests, docs, template-files etc. - in this repo, in voc4cat-tool and voc4cat-template. Before proceeding, I would also like to discuss with Nikos (back next week).

It may be interesting to analyze how many concepts have how many parents/children at the moment.

[dalito]

We plan to include this change from ChlidrenIRIs to ParentIRIs in the next version of the xlsx-template. Thanks for the idea!

We have to modify the python-package voc4cat-tool which is doing conversion, validation etc., before you will be able to use the new template here. The required changes are quite large and require detailed understanding of the package.

To track progress, follow the issues nfdi4cat/voc4cat-tool#252, nfdi4cat/voc4cat-tool#124 and any future ones tacked with milestone 1.0.0.

[dalito]

We have now changed the code to work with a "Parent IRIs"column in the xlsx-files (nfdi4cat/voc4cat-tool#291).

So far the changes are only available in the development branch dev-1.0.0 of voc4cat-tool. It will take some more time (and careful testing) until we update the voc4cat production pipelines in this repository to this new form of hierarchy-expression.