Open jmurugan-fzj opened 10 months ago
I don't mean to speak for @JR-1991 but I believe this is supported by EasyDataverse: https://github.com/gdcc/easyDataverse
@pdurbin, thanks for raising this. The latest version of EasyDatavere now handles metadata configs dynamically, so you can easily get metadata schemes as classes and populate them like any other Python/PyDantic dataclass.
I've tested your use case and created a Jupyter Notebook that shows how to upload metadata to Demo Dataverse. Also, find a small documentation of other features in the flexible-connect
branches Readme file.
Let me know if you have any questions 😊
I don't mean to speak for @JR-1991 but I believe this is supported by EasyDataverse: https://github.com/gdcc/easyDataverse
@pdurbin Thanks for the suggestion, does that mean that I have to switch to easyDataverse instead of pyDataverse? Also I guess, there won't be any future pyDataverse extension planned for this support?
@JR-1991 I will try this solution also, thanks for the detailed explanation with the snippets too :+1:
@jmurugan-fzj - For the time being, I suggest using EasyDataverse to work around the issue. However, in the future, you can continue to use PyDataverse since we are currently planning the next version of PyDataverse. This will address a multitude of issues and PRs filed within this repository.
we are currently planning the next version of PyDataverse
Please see https://dataverse.zulipchat.com/#narrow/stream/377090-python/topic/PyDataverse.20Re-Vamp/near/404845745 and https://docs.google.com/document/d/15cd_I2caOX5ekJrGI_kTe2KibenMk6kZ4qy9y135_60/edit?usp=sharing
Bug report
The latest version of dataset-create-new-all-default-fields.json allows also "astrophysics" & "biomedical" related metadata to be populated for a newly created data set. But the present version of src/pyDataverse/models.py does not seem to be capable of handling these metadata blocks.
1. Describe your environment
2. Actual behaviour:
3. Expected behaviour:
4. Steps to reproduce
5. Possible solution