collective.contact.duplicated
This add-on is part of the collective.contact.* suite. For an overview and a demo of these suite, see collective.contact.demo.
Add a view to manage contact duplications.
Install
For the moment, this needs collective.contact.faceted with batch actions allowed. Select two (or more) contacts (organization, held_position, person, etc) and click on “Merge duplicated” button.
It is also possible to pass a data field with data that do not come from an existing contact. Such data may be merged with the final contact.
Tests
Extend
Adapters of field objects that implements IFieldRenderer interface renders the content of a field on the compare screen. Create a new adapter if you have specific fields.
Contributors
Thomas Desvenain, thomas.desvenain@gmail.com
Eric Brehault, ebrehault@gmail.com
Simon Prévidente, simon.previdente@makina-corpus.com
Stephan Geulette, stephan.geulette@imio.be
Changelog
0.6 (2022-08-19)
Made buildout and tests running. [sgeulette]
Protect compare view against xss [sgeulette]
Avoided error in RelationList field when duplicated and canonical are set on the same field. We do not set a second RelationValue pointing to canonical. (ValueError: term values must be unique !)
0.5 (2018-01-04)
Optimized back references update. [thomasdesvenain]
Hide ‘merge persons’ option when we merge object with non-object. [thomasdesvenain]
Revert: do merge action with Manager role. It allowed to make actions without accurate permissions. [tdesvenain]
0.4 (2017-10-03)
Handle when field value is a ComputedAttribute (from an acqproperty) [thomasdesvenain]
Do not dismiss merge if only one UID + data [ebrehault]
Avoid error with field using plone.app.vocabularies [sgeulette]
Do merge action with Manager role to avoid security problems [sgeulette]
0.3.1 (2017-02-09)
Prevent fatal error when a back reference relation to a duplicated contact is out of sync with any actual content. [thomasdesvenain]
Prefer a 400 error than a 500 when user directly access to merge page without accurate params. [thomasdesvenain]
0.3.0 (2016-09-23)
Merge contacts with data [simon-previdente]
0.2 (2015-11-24)
Fix plone.protect compliancy [ebrehault]
Fix permission: anybody allowed to add contacts must be able to merge duplicates [ebrehault]
0.1 (2015-06-02)
Initial release. [tdesvenain]
6 maintainers
Metadata
6 maintainers
Release files for collective.contact.duplicated 0.6
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 | Actions |
|---|---|---|---|---|
| collective.contact.duplicated-0.6.tar.gz | 32.5 kB | Without provenance | Details for collective.contact.duplicated-0.6.tar.gz |
Release files / collective.contact.duplicated-0.6.tar.gz
| Download URL | collective.contact.duplicated-0.6.tar.gz |
|---|---|
| Size | 32.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
264b9a025de40e47348b00e01a29899f4aa065e1524dec62e70f11069af401b9
|
|
BLAKE2b-256 checksum How to use checksums |
599a0e034f0c51b13025596a54c3d1acd91b8f710935812f660471cc073f277d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Security for collective.contact.duplicated 0.6
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.
