Updated the concept hierarchy to cater for vocab API changes

[jamiefeiss]

The PropTableView & ConceptComponent components have been updated to reflect the vocabulary API changes in RDFlib/prez#134 following the design outlined in #84.

Resolves #84.

[edmondchuc]

I know this is in draft still but just wanted to point out that on initial review and testing, I think I've found a bug.

To reproduce on IDN's "IDN Themes" vocabulary:

• Expand a few top concepts (Australia and Law)
• Click the top concept's "Load more" button
  • This action appears to collapse all the top concepts that have been expanded and resets their expanded button (from - back to +)
  • The two narrower concepts under Australia and Law are now moved to the top concepts level
  • Because we had some top concepts expanded, when clicking "Load more", we loaded Aborigines in history, which has a narrower concept. Thing is, it is loaded in an unexpanded state but with the button in the expanded state (-). My guess here is, due to the label having a lang tag here, it is sorted near the top of the list and coincidentally moves into a node position which we have already placed into the expanded state.

[edmondchuc]

@jamiefeiss looks like the ordering of concepts by casting to string in the SPARQL query (described in this comment https://github.com/RDFLib/prez/pull/134#issuecomment-1652968653) has fixed the issue I mentioned in the last comment above.

[edmondchuc]

I've been thinking from a UX perspective whether clicking on a concept should open in a new tab or open the page in a modal.

Imagine the scenario where a user is browsing a very large vocabulary and they finally find the term they want, either far down the list by clicking "Load more" or expanding terms to a narrower concept. Currently, if the user clicks a concept, it opens the new page. If the user presses the browser back button, it loads them back to the vocabulary page with the concept hierarchy page back in its initial state. It might get annoying really fast if they have to then drill down to where they were at in the concept hierarchy again.

What do you think @jamiefeiss?

[edmondchuc]

@jamiefeiss should we set the default PER_PAGE variable to a larger value? I'm thinking maybe 100?

[jamiefeiss]

Yeah we could have concepts open in a new tab maybe. It would need to be consistent with how other links are opened in other pages though (e.g. resources under a catalog, etc).

For concepts yeah 100 seems less annoying for users. The PER_PAGE variable should be split into 2 config variables - one for concepts and one for regular pagination (e.g. listing vocabs)

[edmondchuc]

Probably only comment is a question on whether we should couple the hasFewChildren comparison to the conceptPerPage config value or make it a separate config value.