collective.dms.scanbehavior
Features
This behavior adds some metadata related to scanning: * scan_id : scan identification as a barcode * version : version number * pages_number : pages number * scan_date : scan date * scan_user : scan user * scanner : scanner or pc information
Translations
This product has been translated into
English
French
Installation
Install collective.dms.scanbehavior by adding it to your buildout:
[buildout]
...
eggs =
collective.dms.scanbehavior
and then running “bin/buildout”
Contribute
Support
If you are having issues, please let us know.
License
The project is licensed under the GPLv2.
Contributors
Franck NGAHA, franck.o.ngaha@gmail.com
Stephan GEULETTE, stephan.geulette@imio.be
Changelog
1.3.3 (2026-04-14)
Removed scan_id column. [sgeulette]
1.3.2 (2025-12-16)
Removed ‘to_sign’ and ‘signed’ fields from the behavior. [chris-adam]
Fixed behavior name to collective.dms.scanbehavior.behaviors.IScanFields to avoid behavior name changed when code is refactored. [gbastien]
1.3.1 (2024-03-01)
Corrected behavior zcml definition to avoid message when Plone starts. [sgeulette]
1.3.0 (2023-09-07)
Improved date range. [sgeulette]
Cleanup: isort, use unittest instead unittest2, removed dependency on ecreall.helpers.testing. [gbastien]
1.2 (2023-07-20)
fix : [DMS-949] min & max for scan_date [bleybaert]
1.1 (2018-01-04)
Added field to_sign to the behavior. [gbastien]
1.0 (2017-05-30)
Moved version attribute to the scan tab. [gbastien]
Move the signed attribute from IDmsFile schema [mpeeters]
Added signed index [sgeulette]
0.4 (2016-04-20)
Add version attribute. [sgeulette]
0.3.3 (2015-11-24)
Don’t store None in catalog. [sgeulette]
0.3.2 (2015-06-05)
Corrected MANIFEST [sgeulette]
0.3.1 (2015-06-05)
Modified scan_id index [sgeulette]
0.3 (2014-11-28)
Added scan_id as index [sgeulette]
0.2.1 (2014-09-02)
Updated changes.
Corrected manifest.
0.2 (2014-04-15)
renamed IScan in IScanFields.
changed zcml description of behavior
translate the title and description of the behavior in the interface.
delete the folder content.
moved the zcml definition of import step in profile.
correct the manifest.
renamed “scan_user” to “operator”.
0.1 (2014-04-14)
Initial release. [fngaha]
Metadata
Release files for collective.dms.scanbehavior 1.3.3
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_dms_scanbehavior-1.3.3.tar.gz | 19.0 kB | Without provenance | Details for collective_dms_scanbehavior-1.3.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective_dms_scanbehavior-1.3.3-py3-none-any.whl | Python 3 | none | any | Details for collective_dms_scanbehavior-1.3.3-py3-none-any.whl |
Total release size: 35.8 kB
Release files / collective_dms_scanbehavior-1.3.3.tar.gz
| Download URL | collective_dms_scanbehavior-1.3.3.tar.gz |
|---|---|
| Size | 19.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
61825c89a98fcf292888b81cd793df00d883e19a78259f7808503ee57ba85830
|
|
BLAKE2b-256 checksum How to use checksums |
4552e290ae9066a28cd70ddb74fa83ace5a3a2321e1e7590cbeb0628b558df1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Release files / collective_dms_scanbehavior-1.3.3-py3-none-any.whl
| Download URL | collective_dms_scanbehavior-1.3.3-py3-none-any.whl |
|---|---|
| Size | 16.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
45cbb94443a0ffac5c4a408615706bd71a0082bab4c802b6ebdb9505a1ea576d
|
|
BLAKE2b-256 checksum How to use checksums |
2ef707a37d54124e2be5358f0f81c65330de5f46622aa7a2473ba231d4d8c82c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Security for collective.dms.scanbehavior 1.3.3
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.