dataset_transfer

git.splent.io/splent-io/splent_feature_dataset_transfer

v0.2.0 full governance

About

Offers of a dataset and its versions to another account (DL-17): an inbox in the account area, a mail with a signed link, one answer whether or not the account exists, offers that lapse, locked answers, one live offer per lineage and a daily limit per account

Provides

Models
DatasetTransferRequest
Services
TransferService
Routes
/datasets/<int:dataset_id>/transfer/transfers/transfers/<int:transfer_id>/accept/transfers/<int:transfer_id>/cancel/transfers/<int:transfer_id>/decline/transfers/offers/<token>
Hooks filled
dataset.view.actions
Translations
es

Configuration

Setting Default What it does
DATASET_TRANSFER_EXPIRY_DAYS 14 Days an offer waits for its answer. Past them it lapses: it is cancelled, it can no longer be accepted, and its lineage can be offered again.
DATASET_TRANSFER_MAX_OFFERS_PER_DAY 10 Offers an account makes in a day, whether or not they reach an account; one more is refused (429 in API v1). 0 for no limit.

These are the defaults. A product changes them in its own pyproject.toml, under [tool.splent.config], or in .env.deploy in production.

Dependencies

Used by
Listens to
user-deleting

In product lines

  • openhubs_spl Optional in this line Needs dataset auth mail

Extension points

Templates
dataset_transfer/inbox.htmldataset_transfer/offer.htmldataset_transfer/offer_page.htmlhooks/transfer_action.html
Services
TransferService
Models
DatasetTransferRequest
Routes
A refinement can add routes to its blueprint

Other features fill its hook slots. A refinement can override its templates and services or extend its models without forking it.

Compatibility

Python
>=3.13
SPLENT framework
>=1.30.0