This release is a pre-release and may not be stable for production use.
Faculty Staff Directory: Core
Faculty Staff Directory is a personnel directory that provides a way of creating and grouping personnel.
This package is a part of the next generation FacultyStaffDirectory. It will only work with Plone 4.1 and greater.
The fsd.core package provides three types of content: Person, Group and Person Group Data. The Person and Group content-types makes up the majority of the functionality required to build a rudimentary personnel directory.
The Person Group Data content-type is used to provide metadata about the Person to Group relationship (e.g. Affiliation -> ‘President’, Title -> ‘Store Manager’). This content-type is not directly addable through the Plone interface. Group data can only be applied through the Person or Group edit forms.
The provided content-types of purposely lean to increase the reusability of the types. The fsd.classic package can be used to add common personnel fields (and fields commonly found in FacultyStaffDirectory) to the Person content-type.
Changelog
1.0a1 (2011-10-20)
Initial release. [cah190, esteele, pumazi]
1 maintainer
Metadata
1 maintainer
Release files for fsd.core 1.0a1
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 |
|---|---|---|---|---|
| fsd.core-1.0a1.tar.gz | 19.5 kB | Without provenance | Details for fsd.core-1.0a1.tar.gz |
Release files / fsd.core-1.0a1.tar.gz
| Download URL | fsd.core-1.0a1.tar.gz |
|---|---|
| Size | 19.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6214abdf55613b311f943601266d1723eb26e87f30b4e5c2970cf6caeffcb64d
|
|
BLAKE2b-256 checksum How to use checksums |
d872a08c503748d14dd5c4cbdfa26b3f61f9200e029d0e3e27ce8c36218ec07a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for fsd.core 1.0a1
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.
