The Impact Data module provides a structured way to log and manage data related to an organization’s impact. This module allows users to categorize, classify, and store impact-related data in a structured manner, ensuring better tracking and analysis.
Table of contents
Configuration
Navigate to Impact Data in the Odoo backend.
Configure Impact Data Categories to create hierarchical structures for data classification.
Define Impact Data Types to standardize data entry formats.
Start logging impact data with Impact Data Entries.
Usage
Logging Impact Data
Navigate to Impact Data → Impact Data Entries.
Click Create and enter: - Year of the entry. - Associated Analytic Account. - A Category and its related Parent Category (if applicable). - The Type of data being logged. - The Value of the impact measurement. - Additional comments (optional).
Save the entry to store the data.
Use pivot and graph views to analyze the data.
Known issues / Roadmap
There are no issues for the moment.
Bug Tracker
Bugs are tracked on GitLab Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Juan Manuel Regalado Gómez <juanmanuel.regalado@somit.coop>
Guillem Alborch <guillem.alborch@somit.coop>
Javier Carrillo <javier.carrillo@somit.coop>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-impact-data-registry 16.0.1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| odoo-addon-impact-data-registry-16.0.1.1.0.tar.gz | 41.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo_addon_impact_data_registry-16.0.1.1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 89.2 kB
Release files / odoo-addon-impact-data-registry-16.0.1.1.0.tar.gz
| Download URL | odoo-addon-impact-data-registry-16.0.1.1.0.tar.gz |
|---|---|
| Size | 41.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6017b0fa810187fd909a2d5f6b5fbb09e1a3935f298494cbd9adb7e218790678
|
|
BLAKE2b-256 checksum How to use checksums |
a5207e4344f1d72bbfce2902db5393f2bcb3a3519f71f63d07f79b7157ee8500
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.6
|
Release files / odoo_addon_impact_data_registry-16.0.1.1.0-py2.py3-none-any.whl
| Download URL | odoo_addon_impact_data_registry-16.0.1.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 47.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
54945fb63656761453512b8b342fa36f624f75de26be756b6e03fd68ec7a1748
|
|
BLAKE2b-256 checksum How to use checksums |
af4c233b492236392496b5701612daf1bb0ffcee10480cd6e5980be0652c9585
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.6
|
Security for odoo-addon-impact-data-registry 16.0.1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
