Ticket #184 (Clôturé Amélioration: Résolu)
Archive system
| Reported by: | gdelannay | Owned by: | |
|---|---|---|---|
| Priority: | Haute | Milestone: | PloneMeeting 1.2 |
| Component: | Produit PloneMeeting | Severity: | Non bloquant |
| Keywords: | Cc: |
Description
We need to implement a system for archiving decisions. I guess we should do the following: (1) define one more state "archived" for meetings; (2) define 3 more states "delayed_archived", "confirmed_archived" and "refused_archived" for items.
A new permission "PloneMeeting?: Read archives" should allow more users to access archived meetings and items.
EGW needs this: once things will be archived, a WebDAV user having permission "PloneMeeting?: Read archives" will access archive data, copy it in its DB, index the content of all annexes, and let more users search among archives through another web UI.
Change History
Note: See
TracTickets for help on using
tickets.

Done. For items, only one state "itemarchived" has been added. Indeed, thanks to the workflow_history, it is possible to go back to the previous state (confirmed, delayed or refused); 3 distinct states were not needed (thanks, guys from the PloneGov? Belgian Parliaments!).
Instead of a permission, a new role has been added: "MeetingArchiveObserver?". This role has permissions "View" and "Access contents information" when a meeting is archived.