documentation: adding new properties

[rmfranken]

Hi there,

I'm very actively working using your tool, and am trying to add another property to the list of properties that get's read and displayed.

In your documentation, I see I need to change 3 files to add a property (types.js, context.js and queries.js). However, since I'm not able to make it work with just those three, I'm wondering if there are more places where I need to introduce changes. If I take an existing property like "scope note", I already see many more files where this is mentioned, and I assume would need to be changed if I wanted to make a change to scope note or add another property.

Is that correct, or should it really only be those three files? In which case - what information can I provide you with to best help me debug why the property I add is not rendered or even mentioned anywhere in any of the html files?

Kind regards,
Robin

[acka47]

Hi @rmfranken, thanks for your request. Generally, @sroertgen has done most of the development in the past and he would be the right person to address your question, however, he apparently does not have any resources at the moment to work on SkoHub, so I am stepping in.

(Generally, I am more like a product owner for SkoHub who also hasn't been doing very much in the past months. However, to get development going again on SkoHub, at least for some small fixes, I will work on organizing regular open development meetings (currently rather for the German-speaking SkoHub user group which is the biggest anyway, see https://metadaten.community/t/naechstes-skohub-entwicklungstreffen/881. Feel free to chime in the forum discussion if you are interested in participating.)

With regard to your current enquiry, it might be best to mimic a past PR for adding a new field, e.g. this one for adding three note fields: https://github.com/skohub-io/skohub-vocabs/pull/293/files In this case, six files were adjusted two of them being test-related. Does this help to find your way?

[rmfranken]

Will make a branch on https://github.com/sdsc-ordes/skohub-vocabs to show how I interpret the documentation

[acka47]

As discussed in today's meeting, @rmfranken will provide a link to the pull request with his attempt to add a new property so that we can check where the problem is.

[rmfranken]

Hi there, I've added my first experiment, which is just replacing an existing property with another one:

https://github.com/sdsc-ordes/skohub-vocabs/tree/new-prop-test

I figured if that's possible, I might be able to add a new property too. For this example, I tried to replace skos:scopeNote with skos:unit. ( I know skos:unit does not exist, but I wanted to avoid any prefix issues to begin with)

You can see in my arema ontology turtle that I have added a value for skos:unit for http://example.org/taxonomy/AbsorptionCoefficientAt500hz - which I would expect to show up. scopeNote was working before I made these changes.

[acka47]

Thanks, @rmfranken , @Phu2 will take a look at your implementation.

[rmfranken]

note: the arema ontology is in the demo folder