In the light of #5889 I suggest we create a new module "dataverse-schemas" where we collect Java code that can be use to marshal/unmarshal metadata schemas. Then let's use these to map from/to our internal model... See https://github.com/IQSS/dataverse/issues/5889#issuecomment-2047223997 for some first sample code using DataCite 4.5 kernel.
@Oliver Bertuch great demo at tech hours today! Very impressive!
Thx. It's no impressive tech at all... Normal business. The hard work is done by the folks writing these generators.
Well, I appreciate all the time DataCite and DDI put into writing xsd files. Maybe we should do this for Dataverse. :sweat_smile:
Urgh... no please don't
Let's do a solid Json schema
Sure. We have a start, at least.
At distribits we heard that might be harder then we think it is :sweat_smile:
yeah
Thanks for explaining this idea in the GitHub issue for laymen like me Oliver!
I'd like to help make sure we're aware of the scope of that issue. Do y'all think this is a dependency for #5889? It was given a 33 and added to sprint ready, I'm assuming based on how exports are created now.
Was Jim Myers on this tech hours call? He assigned himself to that issue, too.
Hi @Julian Gautier, yes, Jim was on the call. He said it might not be immediately relevant for the current work of reorganizing the exporters. But if we need to rewrite some of the exporter in order to support more relevant data being sent to DataCite, using this model based approach might come in handy.
So for now we can let it sit and wait for a while. It wasn't much resources put into it, but does show promising results.
Ah okay ๐๐ฝ
Last updated: Nov 01 2025 at 14:11 UTC