This release is a pre-release and may not be stable for production use.
udata-recommendations
This plugin acts as a bridge between uData and a recommendation system.
In our case (data.gouv.fr), it's a set of scripts living here https://github.com/etalab/piwik-covisits.
Recommendations are stored on datasets. Recommendations can come from various sources and are stored in a descending order, according to the provided score (from 1 to 100). The top recommendations are displayed at the bottom on the dataset page.
Compatibility
udata-recommendations requires Python 3.7+ and uData.
Installation
Install uData.
Remain in the same virtual environment (for Python).
Install udata-recommendations:
pip install udata-recommendations
Modify your local configuration file of udata (typically, udata.cfg) as following:
PLUGINS = ['recommendations']
RECOMMENDATIONS_SOURCES = {
'source-name': 'https://path/to/recommendations.json',
'other-source': 'https://path/to/other/recommendations.json',
}
RECOMMENDATIONS_NB_RECOMMENDATIONS = 4
RECOMMENDATIONS_SOURCES: A key-value dictionary of recommendation sources and URLs to fetch. Default:{}RECOMMENDATIONS_NB_RECOMMENDATIONS: The maximum number of recommendations to display on the dataset page. Default:4
Usage
Adding recommendations
You can fetch and store recommendations as a task, using your configuration in RECOMMENDATIONS_SOURCES, on a schedule if needed. By default, previous recommendations are cleaned before the importing new ones, but you're in control.
udata job run recommendations-add
# Don't clean each source before importing new recommendations
udata job run recommendations-add should_clean=false
Deleting recommendations
To clean all recommendations, you can run the following task.
udata job run recommendations-clean
Expectations
This plugin expects the following format to provide datasets recommendations:
[
{
"id": "dataset-id",
"recommendations": [
{
"id": "dataset-slug-1",
"score": 100
},
{
"id": "5ef1fe80f50446b8f41ba691",
"score": 1
}
]
},
{
"id": "dataset-id2",
"recommendations": [
{
"id": "5ef1fe80f50446b8f41ba691",
"score": 50
}
]
}
]
Dataset IDs can be IDs or slugs. Scores should be between 1 and 100, inclusive. You can validate your JSON using a JSON Schema.
Changelog
Current (in progress)
3.1.0 (2021-09-16)
- Change udata-gouvfr dependency to udata-front following renaming #188
3.0.0 (2021-08-12)
- Ensure compatibility with udata3 by changing imports and style #183
2.2.0 (2020-11-30)
- Add reuses support #153
2.1.1 (2020-10-16)
- Ignore recommendation of dataset itself #147
2.1.0 (2020-08-25)
- Add score to recommendations and support multiple recommendation sources #142
2.0.0 (2020-03-11)
1.0.1 (2018-08-03)
- Nothing yet
1.0.0 (2018-06-06)
- Allow slug instead of id for datasets #8
- Initial release
Metadata
Release files for udata-recommendations 3.1.1.dev647
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| udata_recommendations-3.1.1.dev647-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for udata_recommendations-3.1.1.dev647-py2.py3-none-any.whl |
Release files / udata_recommendations-3.1.1.dev647-py2.py3-none-any.whl
| Download URL | udata_recommendations-3.1.1.dev647-py2.py3-none-any.whl |
|---|---|
| Size | 11.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
2c74fd27e644192d4d408781c0fcdd4ed40b1cf6d0a005d7313b2e6f0a00c4c7
|
|
BLAKE2b-256 checksum How to use checksums |
ee233bf061b8e34b894dbb1344d9b9574f577b7e1c0447dfd0a267139acd11d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.8.3 requests/2.24.0 setuptools/65.1.0 requests-toolbelt/0.9.1 tqdm/4.64.0 CPython/3.7.6
|
Security for udata-recommendations 3.1.1.dev647
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.