Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vergleichen von \catalogue & \metadata-Endpunkt #34

Open
Schalwal opened this issue Jul 13, 2022 · 2 comments
Open

Vergleichen von \catalogue & \metadata-Endpunkt #34

Schalwal opened this issue Jul 13, 2022 · 2 comments
Assignees

Comments

@Schalwal
Copy link
Collaborator

No description provided.

@MarcoHuebner
Copy link
Collaborator

Suggestion/ Idea:
Use tools like itable for easier navigation (haven't used them before). This would however likely require a distinction between command line and Jupyter Notebook...

Further packages: Towards Data Science Post

@pmayd
Copy link
Collaborator

pmayd commented Aug 14, 2022

normally we try to reduce the number of dependencies to a bare minimum to keep the footprint of Python libraries small. For example, even when we have notebooks for documentation, jupyter notebooks would not be required to install the package, because it is not necessary to run and use the Genesis Python wrapper, only to access/run the documentation, so it's a developer dependency, not a required dependency. I like the idea of itable but I see little value in adding it to our library as we primarily serve the data not displaying it. The core feature of our library is to fetch data from GENESIS, it should be up to the data scientist how and with which tools to further analyze the data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants