Stream: ui-dev

Topic: 2024-04-15 presentation

Philip Durbin 🚀 (Apr 18 2024 at 13:21):

A huge thank you to @Vera Clemens for an excellent talk on Monday. I missed it live but I watched the recording and it inspired me to kick off a couple topics about it:

• #containers > 2024-04-15 ui-dev meeting
• #python > 2024-04-15 ui-dev meeting

Philip Durbin 🚀 (Jan 07 2025 at 17:30):

@Balázs Pataki this is the talk by @Vera Clemens I mentioned where she's using fields in Dataverse that have arbitrary depth (or at least more than only two levels).

Philip Durbin 🚀 (Jan 07 2025 at 17:45):

@Balázs Pataki please see also this issue: Feature Request/Idea: Nested compound fields #9200

Philip Durbin 🚀 (Jan 07 2025 at 17:47):

Screenshot 2025-01-07 at 12.46.43 PM.png

Philip Durbin 🚀 (Jan 07 2025 at 17:48):

(complex nested data structure)

Balázs Pataki (Jan 07 2025 at 17:53):

Really nice UI and workflows! I could not really found a demo or mention of the nested data structure part. Would be really curious how it was implemented without changing Dataverse itself, using just its public API-s. Maybe using metadatablocks representing nested data and managing the relationship of the nesting in their own python backend? @Vera Clemens , can you maybe provide some details?

Vera Clemens (Jan 08 2025 at 15:10):

@Balázs Pataki I saw that Johannes already provided some more info in the comments of the GitHub PR #9200 :+1: As he said, the Dataverse backend is already capable of supporting any level of metadata field nesting. Only the UI cannot yet properly show it.

There are only two smaller issues on the backend side (which were non-critical for us):

1. OAI-ORE metadata export fails for deeply nested metadata: #10809
2. Bug in the Solr schema generation (described in #9200). I've just opened a PR with a fix here: #11136

Philip Durbin 🚀 (Jan 08 2025 at 15:15):

@Vera Clemens maybe I'm misremembering that presentation you gave. Did you demo any of your UI that has fields with deeper nesting than normal? If not, would you be able to share a screenshot of how it looks?

Vera Clemens (Jan 08 2025 at 15:20):

@Philip Durbin 🚀 Just to make sure we don't misunderstand each other, by "the UI" I meant the Dataverse (JSF) UI. I can share a screenshot of our UI in a minute.

Philip Durbin 🚀 (Jan 08 2025 at 15:20):

I meant your custom non-JSF UI.

Vera Clemens (Jan 08 2025 at 15:35):

Here's an example:

Underlying metadata structure:

• Resource.contributors: persons or organizations that have contributed to the dataset (allows multiples)
  • Resource.contributors.affiliations: organisations the contributor is affiliated with (allows multiples)
    • Resource.contributors.affiliations.identifiers: identifiers of that organisation (allows multiples)
      • Resource.contributors.affiliations.identifiers.scheme: e.g. ROR
      • Resource.contributors.affiliations.identifiers.identifier

Dataset page UI:

image.png

(see: https://health-study-hub.de/resource/nfdi4health-552)

Form UI:

image.png

Philip Durbin 🚀 (Jan 08 2025 at 15:41):

Interesting. Thanks!

Balázs Pataki (Jan 09 2025 at 06:40):

Vera Clemens said:

@Balázs Pataki I saw that Johannes already provided some more info in the comments of the GitHub PR #9200 :+1: As he said, the Dataverse backend is already capable of supporting any level of metadata field nesting. Only the UI cannot yet properly show it.

Thanks, Vera, I didn't know these fixes were already in place and you used that. So, you practically worked around the Dataverse UI not supporting nested fields in your own UI. Great!

Last updated: Nov 01 2025 at 14:11 UTC