Personnel Roster
collective.roster aka Personnel Roster provides highly customizable personnel listing, which can be extended easily with custom file system developed add-ons.
Adding a new roster
Adding a new person
Alphabetical listing
Groups listing
Gallery listing
Person view
Person viewlets manager
Available behaviors
Changelog
2.3.1 (2017-12-18)
Fix groups behavior to not acquire person groups from roster when dexterity implicit attribute lookup is disabled and groups attribute is missing [datakurre]
2.3.0 (2017-10-27)
Change english translation for subject from studysubject to subject [Grrandi]
2.2.1 (2017-10-03)
Fixed SimpleTerm creation. [iham]
2.2.0 (2017-04-04)
Add option for groups behavior to mark person a groups leader and sort leaders before others in grouped views [datakurre]
2.1.4 (2017-04-04)
Fix issue where group links on gallery depended on current URL and might have been broken [datakurre]
2.1.3 (2017-03-29)
Fix to require plone.app.registry>=1.2.5 [fixes #6] [datakurre]
2.1.2 (2017-01-12)
Fix issue where groups adapter returned None [datakurre]
2.1.1 (2017-01-11)
Fix biography to be primary field [datakurre]
2.1.0 (2016-12-19)
Make roster views aware of possibly enabled RichText-behavior [datakurre]
2.0.3 (2016-12-16)
Fix issue where group anchors on groups_view were broken [datakurre]
2.0.2 (2016-12-07)
Fix alphabetical listing to sort using locale aware sortable title [datakurre]
2.0.1 (2016-11-08)
Fix issue where empty value for JS bundle broke Plone bundle merge on a new site [datakurre]
2.0.0 (2016-11-04)
Allow short number to be anything between 100 and 9999 [datakurre]
Plone 5 compatibility: Optionally import checkEmailAddress and EmailAddressInvalid from CMFPlone respectively CMFDefault. [thet]
Add file type checking for person portrait image [Grrandi, datakurre]
Change studysubject behavior label from ‘Studysubject’ to ‘Subject’ [Grrandi, datakurre]
Refactored grokless public release. [datakurre]
Metadata
Release files for collective.roster 2.3.1
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.roster-2.3.1.tar.gz | 512.6 kB | Without provenance | Details for collective.roster-2.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective.roster-2.3.1-py3-none-any.whl | Python 3 | none | any | Details for collective.roster-2.3.1-py3-none-any.whl |
Total release size: 570.9 kB
Release files / collective.roster-2.3.1.tar.gz
| Download URL | collective.roster-2.3.1.tar.gz |
|---|---|
| Size | 512.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25ca00418150518c749e62d61e7bc867e2a3882f91f4fe1dbc293fcd5e06b397
|
|
BLAKE2b-256 checksum How to use checksums |
b9fd27e1c9d14d22140d75eb6e5017f327a0b2a64d32f00e404a4ea60a68ced5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / collective.roster-2.3.1-py3-none-any.whl
| Download URL | collective.roster-2.3.1-py3-none-any.whl |
|---|---|
| Size | 58.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cdd45fadc79d993ef244fd135ac7fa5022579d6cee50ce03ac5dbe202f29a956
|
|
BLAKE2b-256 checksum How to use checksums |
e4420142726c4fb7a11ba3660d46ab5afb41cdcd5eec2a6f8df95e3b5fb9b8b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.roster 2.3.1
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.