Open skasberger opened 3 years ago
Just discovered this issue and the idea seems to align very well to what has been done with EasyDataverse already. The library also utilizes PyDantic and generates objects according to the metadatablock schemes found at api/metadatablocks/blockname
.
Wouldnt it make sense to merge the functionality into PyDataverse? In my opinion having a single Python library makes more sense since both are heading in the same direction. What do you think @skasberger @pdurbin @poikilotherm?
I think a single library would be easier for the community, sure.
Agree on that, especially as pyDataverse is very lightweight and is made to build upon other, more specialized services/functions.
As discussed during the 2024-02-14 meeting of the pyDataverse working group, we are closing old milestones in favor of a new project board at https://github.com/orgs/gdcc/projects/1 and removing issues (like this one) from those old milestones. Please feel free to join the working group! You can find us at https://py.gdcc.io and https://dataverse.zulipchat.com/#narrow/stream/377090-python
Re-factor the models module.
Goals are:
Requirements
ACTIONS
0. Pre-Requisites
1. Research
Design
Schema
controlledVocabulary
: subject, authorIdentifierScheme, contributorType, country, journalArticleType, language, publicationIDTypemdb.citation
?Tools
main.create_model()
sqlalchemy_to_pydantic
DataverseDefault()
,DatasetDefault()
,DatafileDefault()
Architecture
BaseModel()
2. Plan
Prioritize
3. Implement
BaseModel()
visualize data flow / Architecture
draw all functions, paths etc.
models.py
4. Follow Ups