This release is a pre-release and may not be stable for production use.
Introduction
collective.gtags provides Google Code style tagging for Plone. There is a control panel that lets administrators define a vocabulary of tags, where tags may have a “category” prefix. For example, “Department-IT” and “Department-HR” would both be tags in the “Department” category. A tag “Important” has no category.
The administrator may further decide whether users should be allowed to pick non-standard tags globally (if also enabled on a per-type basis), and list categories as required and/or unique.
zope.schema field
This is implemented via a custom zope.schema style field: collective.gtags.field.Tags. This is a sub-class of zope.schema.Set, with custom validation. It will only work once the package is installed, since it depends on the ITagSettings utility installed with this package to properly function.
The field is accompanied by a default z3c.form widget, which uses jQuery and the jQuery autocomplete widget to provide the user interface.
See tagging.txt in the package for a detailed doctest of the basic tags functionality.
Behavior
To use this field, you can either use the Tags field directly in your own schema, or use the collective.gtags.behaviors.ITags behavior in a Dexterity type or other type that supports plone.behavior. This behavior will place a tags field in the “Categorization” field set and store tags in the Subject Dublin Core metadata field, thus taking the place of the standard ‘keywords’ field.
Acknowledgements
Development of this package was sponsored by Deloitte Australia (http://deloitte.com.au).
Changelog
1.0b2 - 2009-07-12
Catch up with changes in plone.registry’s API. [optilude]
1.0b1 - June 23rd 2009
Initial release
1 maintainer
Metadata
1 maintainer
Release files for collective.gtags 1.0b2
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.gtags-1.0b2.tar.gz | 19.7 kB | Without provenance | Details for collective.gtags-1.0b2.tar.gz |
Security for collective.gtags 1.0b2
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.
