ability to select by [field] and perform [action] on all returned entries

[deborah]

Title:
ability to select by [field] and perform [action] on all returned entries

Area:
entries

Summary:
I'd like to be able to select a set of entries which correspond to some searchable field (e.g. tag, date range) and perform one of something in an allowed set of actions on the returned set (e.g. change privacy, add tag, delete entry).

Description:
Currently, you can edit privacy on entries within a given date range. I was initially going to make a request to add the feature of editing privacy on entries with a specific tag, but there is a desirable general possible feature.

There is a select number of fields for which it is reasonable for a user to grab a selection set of entries. Date range and tag are the two that come to mind for me, but possibly others might want userpic, mood, or some other field. In theory there could also be fulltext search on subject or body, but that could get a lot more complex, and I'm trying to think through the implementation in any reasonable way.

There is also a select number of actions for which it is reasonable that a user might want to act en masse on the returned set. Edit privacy, delete entry, add tag, change userpic... I can't think of any others off the top of my head, but there probably are some.

My use case is that I would like to change the privacy of all entries with a specific tag, but I can definitely see more expansive use cases.

This seems like a good candidate for a paid feature, because it could get fairly processor intensive depending on its popularity.

Poll #6508 ability to select by [field] and perform [action] on all returned entries

Open to: Registered Users, detailed results viewable to: All, participants: 63

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
43 (68.3%)

Should be implemented with changes. (please comment)
7 (11.1%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
13 (20.6%)

(Other: please comment)
0 (0.0%)

Comments

[poulpette]

With change: as long as either the entry deletion isn't possible, or has strict limitations (not more than a handful of entries perhaps) I think this could be extremely useful.

[turlough]

+1

[feathertail]

+1.

[arethinn]

as long as either the entry deletion isn't possible, or has strict limitations

I disagree - I can see the use of deleting all entries which had a specific tag, for instance. Should perhaps be double-confirm, though.

[zvi]

mass deletion is generally disfavored, in case of a security breach, where a malicious person gets hold of your account. most other mass actions would have limited damage, but mass deletion would be permanent.

[poulpette]

As zvi said, allowing mass entry deletion has too great a potential for loss of content in case of a compromised account to allow it.

I'm not completely against it though, which is why I suggested very limited deletion possibilities. I know it's cumbersome to have to go and delete entries one by one, but I'd rather have to do this than facilitate a hacker's ability to wreak havoc with my entries.

[briar_pipe]

Mass setting to private would probably cover most of the needs of a mass deletion? Except import issues, I suppose. But from a security standpoint, it's less risky.

[delladea]

+1