This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

Introduction

This is an add-on for Plone to provide some content management metadata essentials.

Even if they are several fields, they complement each other to build a set of useful features for managing and maintaining websites.

Responsible person

It may come as a surprise to some that we don’t have this in Plone already. We store and index the creator of content (a mostly useless value) and we manage an owner role on content, a permission rule not indexed for practical use. The responsible person is the person that owns the content and is responsible for keeping it updated.

Validity date

The expiry date field in Plone is not very useful and not often used beyond checkboxes in feature comparisons. This field, the validity date, is more useful: It is always set when saving an object (like the versioning note) from a vocabulary of dates in the future (1 week, 1 month, 3 months, 6 months, 1 year from now). Whenever the object is saved, the date is set in the future.

When the date approaches, the responsible person will be notified that his content is about to expire. It will also be visible in her review lists. For updating it, all she needs to do is to open the content and save it again, effectively setting the expiry date some time in the future. If the content does expire, it will, according to site policy, either be archived/made unavailable/hidden, or visibly marked as obsolete/unmaintained.

Views and actions needed

  • My content
    a screen of content i am responsible for and its status Perhaps batch operations on it perhaps batch assign to someone else
  • New document byline
    the responsible person, not the creator alternatively a portlet with a photo and contact details of the responsible person
  • a new ownership form which sets this field along with the owner role
  • a global change ownership form for when you delete/deactivate users.

Changelog

1.1 (2011-12-06)

  • Prevent the default value to be set during indexing, to prevent breaking ZCatalog internal structures. [mj]

Important

You’ll need to run http://url.to.your/plone-site/@@cleanup-catalog-ghosts to repair a broken ZCatalog after upgrade.

1.0 (2011-08-09)

  • Initial release [ggozad]
Release History

Release History

1.1

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
collective.contentgovernance-1.1.zip (31.9 kB) Copy SHA256 Checksum SHA256 Source Dec 6, 2011

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting