========
yabadaba
========
The yabadaba package (short for "Yay, a base database!") is meant to make it
easy to design user-friendly Python packages that can access and store content
in a variety of database types. This is accomplished by defining mid-level
abstractions of databases and database records.
The conceptual ideas behind yabadaba and what it intends to accomplish are
- FAIR data exists in a variety of open access databases. While the FAIR
data principles provide guidelines for how to make the data more accessible
in general, there are no specifics about standardizing database
infrastructure, query APIs, or data schemas. This results in a complex
ecosystem where anyone wishing to access data from such a database must
become familiar with the data and database infrastructure used.
- Developing, implementing and enforcing standardization of data and databases
is a complex task that requires agreement with a large number of separate
entities even within the same community. Additionally, it may place too
many limitations on further data evolution and/or be difficult for smaller
groups to adhere to.
- Alternatively, the problem can be solved at a higher level. Rather than
force uniformity at the data level, tools can be developed that are
capable of transforming data between different representations. This is
what yabadaba aims to do.
- By managing database interactions and data transformations, yabadaba makes it
possible to interact with data from multiple databases and database
infrastructures in similar ways. This increases the accessibility of the
data as users of the data do not need to become experts in every database
infrastructure and every data schema.
Package design
--------------
The yabadaba package itself is not meant to be an end-user package per-se, but
a toolset for data generators and maintainers to easily create their own
packages that serve as user-friendly APIs to their own data. To this end,
yabadaba defines a number of base and utility classes that allow those
yadabada-based packages to build upon yabadaba in a modular fashion.
The core base classes defined by yabadaba are
- **Database** defines common method calls for interacting with the
records in a database, such as querying, adding, modifying, and deleting
entries. Child classes of Database are then defined that implement the
universal interaction methods for a given database infrastructure.
- **Record** defines methods that allow for the interpretation and
transformation of a single database entry of a given schema to/from different
data representations. Notably, the record interprets the data into python
values and objects that are easy for users to interact with while also making
the data accessible in and convertible to different raw storage formats.
At the bare minimum, child classes of Record specify the data values
contained within a specific schema so the methods in the base Record class
can properly work. One way to think about this is that you create a
python object to represent and allow users to interact with some of your
data and you simply allow it to inherit from the base Record class to
provide the framework for saving and loading the content.
- **Value** defines methods that allow for the interpretation and
transformation of the component values contained within a record. Child
classes of Value specify how to perform those operations for different
data types and structures, and can specify one or more default query
operations to build for the value. Each Record subclass defines a dict of
Value objects providing a schema for the data and the basis for performing
the data transformations.
- **Query** defines methods that build database query operations for the
different database infrastructures. The child classes of Query focus on one
specific query operation and define different methods to efficiently perform
that operation in the different database infrastructures. Query objects are
typically associated with Value objects to specify how to query based on the
values of specific elements in a Record.
- **ModuleManager** provides a common interface for managing the various
subclasses of Database, Record, Value, and Query in a modular way. The
ModuleManager objects dynamically import the subclasses such that they are
fully integrated with each other and the features of yabadaba. Packages that
build on yabadaba can then add their own subclasses to the managers and take
advantage of yabadaba's capabilities.
- **Settings** provides a means of saving and loading settings across different
python settings. Primarily, this is used to store database access and
authentication information for databases that are frequently used. This
class can easily be extended to manage other settings for yadabada-based
projects.
- **UnitConverter** provides simple tools for managing unit conversions.
Installation
------------
The yabadaba package can easily be installed using pip or conda-forge
pip install yabadaba
or
conda install -c conda-forge yabadaba
Documentation
-------------
Documentation and demonstration Notebooks for yabadaba can be found in the
doc folder in the github repository.
For support, post a issue to github or email lucas.hale@nist.gov.
Raw data
{
"_id": null,
"home_page": "https://github.com/usnistgov/yabadaba",
"name": "yabadaba",
"maintainer": null,
"docs_url": null,
"requires_python": null,
"maintainer_email": null,
"keywords": "database, mongodb, CDCS",
"author": "Lucas Hale",
"author_email": "lucas.hale@nist.gov",
"download_url": "https://files.pythonhosted.org/packages/cc/bc/9b59f1615d05c755b69dc1993e02fb960d68d9cd9712bc7ff407d35e075b/yabadaba-0.3.0.tar.gz",
"platform": null,
"description": "========\nyabadaba\n========\n\nThe yabadaba package (short for \"Yay, a base database!\") is meant to make it\neasy to design user-friendly Python packages that can access and store content\nin a variety of database types. This is accomplished by defining mid-level\nabstractions of databases and database records.\n\nThe conceptual ideas behind yabadaba and what it intends to accomplish are\n\n- FAIR data exists in a variety of open access databases. While the FAIR\n data principles provide guidelines for how to make the data more accessible\n in general, there are no specifics about standardizing database\n infrastructure, query APIs, or data schemas. This results in a complex\n ecosystem where anyone wishing to access data from such a database must\n become familiar with the data and database infrastructure used.\n- Developing, implementing and enforcing standardization of data and databases\n is a complex task that requires agreement with a large number of separate\n entities even within the same community. Additionally, it may place too\n many limitations on further data evolution and/or be difficult for smaller\n groups to adhere to.\n- Alternatively, the problem can be solved at a higher level. Rather than\n force uniformity at the data level, tools can be developed that are\n capable of transforming data between different representations. This is\n what yabadaba aims to do.\n- By managing database interactions and data transformations, yabadaba makes it\n possible to interact with data from multiple databases and database\n infrastructures in similar ways. This increases the accessibility of the\n data as users of the data do not need to become experts in every database\n infrastructure and every data schema.\n\nPackage design\n--------------\n\nThe yabadaba package itself is not meant to be an end-user package per-se, but\na toolset for data generators and maintainers to easily create their own\npackages that serve as user-friendly APIs to their own data. To this end,\nyabadaba defines a number of base and utility classes that allow those\nyadabada-based packages to build upon yabadaba in a modular fashion.\n\nThe core base classes defined by yabadaba are\n\n- **Database** defines common method calls for interacting with the \n records in a database, such as querying, adding, modifying, and deleting\n entries. Child classes of Database are then defined that implement the\n universal interaction methods for a given database infrastructure.\n\n- **Record** defines methods that allow for the interpretation and\n transformation of a single database entry of a given schema to/from different\n data representations. Notably, the record interprets the data into python\n values and objects that are easy for users to interact with while also making\n the data accessible in and convertible to different raw storage formats.\n At the bare minimum, child classes of Record specify the data values\n contained within a specific schema so the methods in the base Record class\n can properly work. One way to think about this is that you create a\n python object to represent and allow users to interact with some of your\n data and you simply allow it to inherit from the base Record class to\n provide the framework for saving and loading the content.\n\n- **Value** defines methods that allow for the interpretation and\n transformation of the component values contained within a record. Child\n classes of Value specify how to perform those operations for different\n data types and structures, and can specify one or more default query\n operations to build for the value. Each Record subclass defines a dict of\n Value objects providing a schema for the data and the basis for performing\n the data transformations.\n\n- **Query** defines methods that build database query operations for the\n different database infrastructures. The child classes of Query focus on one\n specific query operation and define different methods to efficiently perform\n that operation in the different database infrastructures. Query objects are\n typically associated with Value objects to specify how to query based on the\n values of specific elements in a Record.\n\n- **ModuleManager** provides a common interface for managing the various\n subclasses of Database, Record, Value, and Query in a modular way. The\n ModuleManager objects dynamically import the subclasses such that they are\n fully integrated with each other and the features of yabadaba. Packages that\n build on yabadaba can then add their own subclasses to the managers and take\n advantage of yabadaba's capabilities.\n\n- **Settings** provides a means of saving and loading settings across different\n python settings. Primarily, this is used to store database access and\n authentication information for databases that are frequently used. This\n class can easily be extended to manage other settings for yadabada-based\n projects.\n\n- **UnitConverter** provides simple tools for managing unit conversions.\n\nInstallation\n------------\n\nThe yabadaba package can easily be installed using pip or conda-forge\n\n pip install yabadaba\n\nor\n\n conda install -c conda-forge yabadaba\n\nDocumentation\n-------------\n\nDocumentation and demonstration Notebooks for yabadaba can be found in the\ndoc folder in the github repository.\n\nFor support, post a issue to github or email lucas.hale@nist.gov.\n",
"bugtrack_url": null,
"license": null,
"summary": "Yay, a base database! An abstraction layer allowing for common interactions with Mongo, CDCS and local directory databases and records.",
"version": "0.3.0",
"project_urls": {
"Homepage": "https://github.com/usnistgov/yabadaba"
},
"split_keywords": [
"database",
" mongodb",
" cdcs"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "a1600b6c99a6e68ac216666fb71d3457a1daea65833a0282a197eede8cc05016",
"md5": "48176990166c8e05942301414ae178fd",
"sha256": "e233c97f0eeff47d6c4289df14f5520d11ea3f05dbd2be144a5a8bbfbcf7367b"
},
"downloads": -1,
"filename": "yabadaba-0.3.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "48176990166c8e05942301414ae178fd",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": null,
"size": 89089,
"upload_time": "2025-02-14T18:19:42",
"upload_time_iso_8601": "2025-02-14T18:19:42.289097Z",
"url": "https://files.pythonhosted.org/packages/a1/60/0b6c99a6e68ac216666fb71d3457a1daea65833a0282a197eede8cc05016/yabadaba-0.3.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "ccbc9b59f1615d05c755b69dc1993e02fb960d68d9cd9712bc7ff407d35e075b",
"md5": "6e62389e3a709c3b1eeab05b5c61cfbf",
"sha256": "53ddedeb4ad4083ff026cc943b1966349de757822eb616842df722c7606a99b4"
},
"downloads": -1,
"filename": "yabadaba-0.3.0.tar.gz",
"has_sig": false,
"md5_digest": "6e62389e3a709c3b1eeab05b5c61cfbf",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 58415,
"upload_time": "2025-02-14T18:19:44",
"upload_time_iso_8601": "2025-02-14T18:19:44.056201Z",
"url": "https://files.pythonhosted.org/packages/cc/bc/9b59f1615d05c755b69dc1993e02fb960d68d9cd9712bc7ff407d35e075b/yabadaba-0.3.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-02-14 18:19:44",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "usnistgov",
"github_project": "yabadaba",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"lcname": "yabadaba"
}
JSON
