Ticket #9576 (closed PLIP: wontfix)
Include batch editing
Reported by: | dukebody | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Future |
Component: | General | Version: | |
Keywords: | Cc: | grahamperrin@… |
Description (last modified by limi) (diff)
Polish plone.app.batch and include it on future plone releases
Proposed by
Javier Mansilla
Proposal type
User interface
Repository branch
trunk
State
being-discussed
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.
(This proposal is based on one that Jon Stahl posted here: http://plone.org/products/plone/roadmap/164)
Proposal
Plone Batch Editing is an answer for those users that usually needs to perform hundreds of administrative tasks to the content items spread in their sites; providing:
- A search form on every folderish object
- On search results, ability of choosing objects to edit, and fields name to edit.
- A form with every selected content and an input field for selected fields to edit
There are some future interesting things to discuss and decide:
- handle renaming
- handling cut-and-paste
- handling workflow transitions
- show folder contents by default?
- more ideas?
Implementation
This work has been started on plone.app.batch product in the 2008 Summer of Code program.
Participants
Jon Stahl: idea's father
Alex Limi: Summer of Code mentor
Javier Mansilla: Summer of code coder
Change History
comment:2 in reply to: ↑ description Changed 6 years ago by grahamperrin
That URL is no longer found.
< http://dev.plone.org/plone/report/24> 'Improvement Proposals' includes a reference to this #9576.
(This proposal is based on one that Jon Stahl posted here: http://plone.org/products/plone/roadmap/164)
That URL is no longer found. Do we have an alternative URL for Jon Stah's proposal? Or the name of the proposal?
Discussion:
• http://n2.nabble.com/-tp1363775p1363775.html 'new PLIP Include batch editing in Plone' in plone-developers
comment:3 Changed 6 years ago by limi
- Description modified (diff)
(Removed irrelevant link, confusing — description is in this ticket. :)
comment:4 Changed 6 years ago by yurj
Can I suggest an improvement? when batch editing a folder, It should be possible also to add an object. In this way, we could mimic a tipical sql/access interface in editing and adding data.
comment:5 Changed 5 years ago by rossp
- Status changed from new to closed
- Resolution set to wontfix
PLEASE READ THIS AND RE-OPEN VALID PLIPS!
As we launch the new PLIP process we'd like to see which PLIPs:
- are still appropriate/needed
- still have owners/proposers/champions
- still have available implementers
If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.