Ticket #11025 (closed PLIP: wontfix)
Content Batch Editing
Reported by: | javimansilla | Owned by: | javimansilla |
---|---|---|---|
Priority: | minor | Milestone: | 4.1 |
Component: | User Experience and Interface | Version: | |
Keywords: | Cc: | plip-advisories@… |
Description (last modified by javimansilla) (diff)
Proposer: Javier Mansilla
Seconder: Horacio Duran
Motivation
Administrators and users of plone sites usually need to apply the same change to hundreds of items dispersed in the site. Current options for doing such a task are very poor, mainly because they imply doing the change once per item.
It is very common for users and site administrators to encounter a need to edit metadata fields on many content items at once. For example:
- The content taxonomy for a site may change, and it may become necessary to re-taxonomize a large number of items.
- It may be necessary to adjust created and/or effective dates for a group of items.
- The writing style guidelines for a site may change, making it necessary to retitle a large number of articles.
- There may turnover in the userbase for a site, making it necessary to change the owner of a large number of items.
- A site administrator may want to enable or disable comments on a batch of items.
- A site administrator may want to write missing descriptions for a batch of items.
Plone currently forces content editors to do this one item at a time, which involves a huge number of mouse clicks and slow page refreshes.
Plone Batch Editing is a response for those users that usually needs to perform hundreds of administrative tasks to the content items spread in their sites; providing:
- A search form for selecting the items to edit, and in search
results, the possibility of editing every item on a particular field
Assumptions
The code should be able to edit fields of standard Archetype items, or based on zope schema fields. Although this functionality may be integrated with the folder_contents view, we are not contemplating such integration right now.
Proposal & Implementation
It's needed to:
- port existent code to last Plone release
- review/discuss/improve user interface
- Extend tests coverage
Deliverables
- Unit tests
- Localization
- Documentation
Risks
The bigger challenges are:
- the fact that, so far, the current code uses plone.app.z3cfom with I'm not very sure if it's planned to be incorporated to plone main branch.
- end up with a intuitive and easy to use interface.
Participants
Proposer: Javier Mansilla (javimansilla)
Seconder: Horacio Duran (perrito666)
Progress
There is a good piece of this already implemented during the summer of code 2008 project, available here http://plone.org/products/plone-app-batch/releases/0.1 I started to do the plone 4 port, but it's just started.
Change History
comment:3 Changed 6 years ago by elvix
Note that this could probably be implemented simpler than before with the inclusion of #9327 It would be cool to see if this plip could benefit from it.
comment:4 Changed 6 years ago by robgietema
I've installed the product and can see a usecase for this but I do think the UI needs some work. Currently the only batched editing we have is the "Change State" option in the folder listing. This proposal should incorporate that method of editing so we don't have 2 ways of doing batched editing. I also don't like the extra tab on top. The batch edit screen should either be triggered using a "Batch Edit" button in the folder contents or by adding a "Batch Edit" button to advanced search.
comment:6 Changed 6 years ago by esteele
- Status changed from new to closed
- Resolution set to wontfix
This PLIP has been declined for consideration for Plone 4.1.
Framework Team voting on this PLIP was:
Alec -1 Craig +0 Elizabeth -1 Laurence +0 Martijn -1 Matthew +0 Rob +0 Ross -
The Framework Team felt that this feature should be developed as an add-on at this time.