Paul Boon (Aug 05 2025 at 13:12): Paul Boon (Aug 05 2025 at 13:12):Hi, In order to get a better understanding of the new SPA, I was building it and then deploying it on our own dev enviromment, which is a Rocky8 VM with Apache fronting Payara. The backend is our own prepopulated dev Dataverse on that VM. While I do get it to work, it is very limited; only the home page and root page work.
When I try to 'view' a dataset page, I get a 404 with the error mesage (console): "There was an error getting the dataset Error: Failed to get dataset by persistent ID: Incorrect Metadata block name key
". I traced it down to the toMetadataBlockName function. When it tries to find “citation” it works, but the next call is with “dansRights” an exception is thrown, because it is not in the MetadataBlockName enum. This "dansRights" is one of our custom metadata blocks.
Could it be that the SPA cannot handle custom metadata blocks or might it be that our backend Dataverse version 6.5 is incompattible?
Notification Bot (Aug 05 2025 at 13:19):A message was moved here from #ui-dev > Status of SPA by Philip Durbin 🚀.
Philip Durbin 🚀 (Aug 05 2025 at 15:36):@Paul Boon thanks @Germán Saracca figured out that there's a hard-coded list of metadata blocks here: https://github.com/IQSS/dataverse-frontend/blob/45fcee44e8923bfc0dc6d5bce9230824089f8226/src/metadata-block-info/domain/models/MetadataBlockInfo.ts#L11
He's planning a fix. Also, we were able to replicate the bug here. Thanks for letting us know!
Paul Boon (Aug 05 2025 at 15:36):When using a latest dev-env, I can reproduce this problem with the new 3d-object metadata; it is not in that list.
Philip Durbin 🚀 (Aug 05 2025 at 17:33):Right. Makes sense.
Paul Boon (Aug 06 2025 at 07:27):The question was originally in 'Status of SPA' because I was not sure if custom metadata was supported. That question remains; is it supported but somehow flawed, or is it not supported?
Germán Saracca (Aug 06 2025 at 11:10):Hi @Paul Boon , Germán here, I'm a frontend developer working on the SPA, thanks for detecting this. There was partial support for custom metadata, limited to the blocks you mentioned from the MetadataBlockName enum. We're currently working on a fix :wrench: for the SPA.
Philip Durbin 🚀 (Aug 06 2025 at 13:05):I'd say "not supported" at the moment. Certain blocks that are hard-coded work.
Philip Durbin 🚀 (Aug 07 2025 at 15:28):@Paul Boon for now, the fixes are going into the 0.1.0 release branch: https://github.com/IQSS/dataverse-frontend/compare/develop...release/0.1.0
I believe it's these three commits by @Germán Saracca:
Screenshot 2025-08-07 at 11.26.19 AM.png
(The PR at https://github.com/IQSS/dataverse-frontend/pull/777 is where we're merging the 0.1.0 release into the "main" branch, so the commits appear there as well.)
Basically, the plan is for these fixes to go into the 0.1.0 release, so thanks for reporting it!
These fixes will also make it into the develop branch at some point.
Philip Durbin 🚀 (Aug 07 2025 at 15:46):@Paul Boon oh and if you want, we can certainly rename this topic to "support for custom metadata blocks" or whatever. :smile:
Paul Boon (Aug 18 2025 at 12:45):@Philip Durbin 🚀 Just changed it as suggested
Philip Durbin 🚀 (Aug 18 2025 at 13:02):Looks great, thanks.
Paul Boon (Aug 19 2025 at 16:05):Pulled develop and build and then deployed it on our test VM, now I do get Datasset metadata with those custom blocks. Great work :+1: @Germán Saracca
Germán Saracca (Aug 19 2025 at 19:33):Nice! Happy it’s working with the custom blocks , thanks for testing and sharing the feedback :praise: @Paul Boon
Notification Bot (Sep 02 2025 at 19:09):Germán Saracca has marked this topic as resolved.
Last updated: Nov 01 2025 at 14:11 UTC