Hey Reinier,

On 8 March 2010 14:00, Reinier van den Born
<[email protected]>wrote:

> Hi Jasha,
>
> I see. But don't you have the same workflow problem with the search/replace
> action (which is supported right now, or isn't it)?
>
You're right about that. In most configurations we removed the button.


> Anyway, my users want this multiple delete functionality especially for
> assets for which we don't have workflow configured.
> So I could, for instance, only enable this functionality if the search is
> restricted to assets.
>
You could or you could just execute it for /binaries and not /content or
just for resources with type=asset

>
> Not sure what you mean by the clipboard, but it may be what I looking
> for.The functionality I am referring to was to have a checkbox in the
> search
> result,
> allowing the user to create a subselection to be subjected to an action
> (search/replace, or, as in my case, delete).
>
> There is some code in place intended to support these kind of selections
> that makes me optimistic. Some examples:
> layout.xsl: has actions selectAll, unselectAll, addToShelf (clipboard is
> menioned there as well, so...)
> searchReplaceAll.xsl makes a disctinction between a BATCHSCOPE_SELECTION
> and
> BATCHSCOPE_ALL.
>
> On the other hands in some places (sitemap) code is missing or (layout.xml)
> there is only a TODO...
> Feeding my fear that the implementation is incomplete. Or is it just a
> matter of enabling it?
>
> The clipboard itself should be completed (adding found resources to a
clipboard) but we have not implemented a general use for it (only customer
specific implementations).

Jasha

>
> Thanks,
>
> Reinier
>
>
>
> On Fri, Mar 5, 2010 at 4:36 PM, Jasha Joachimsthal <
> [email protected]> wrote:
>
> > Hi Reinier,
> >
> > the main reason not to implement this, is that if you do it in a clean
> way,
> > you have to check for each document if that user has the correct workflow
> > permission to actually delete it. Regular authors only have permission to
> > request deletion through the workflow but the repository itself doesn't
> > make
> > a distinction between write and delete permissions. Checking the workflow
> > for a huge amount of documents is a rather expensive operation.
> > There is indeed functionality to put search results in a clipboard.
> There's
> > no general implementation for it but it could be used to store the
> > documents
> > you want to delete.
> >
> > Jasha Joachimsthal
> >
> > [email protected] - [email protected]
> >
> > www.onehippo.com
> > Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
> > San Francisco - Hippo USA Inc. 185 H Street, suite B, Petaluma CA 94952
> +1
> > (707) 7734646
> >
> >
> >
> >
> > On 5 March 2010 14:45, Reinier van den Born
> > <[email protected]>wrote:
> >
> > > Hello Hippo community,
> > >
> > > Our content editors would like a more convenient way to delete large
> > > quantities of obsolete assets.
> > > Not without risk of course, but in an environment that has a lot of
> > quickly
> > > changing content, I can see their point.
> > >
> > > The best location to add functionality like that, I think, would be the
> > > Search tab.
> > >
> > > I guess it should not be too difficult to add a delete button (next to
> > > go-to
> > > and edit) to resources, but this doesn't improve much.
> > > It also doesn't seem hard to do a "delete all" of the resources in the
> > > search result, but it may be hard/impossible to tune the search so that
> > it
> > > will result in exactly the assets to be removed.
> > >
> > > So I am thinking there should be a way to select resources from the
> > search
> > > result and delete only them.
> > > Now in the Search tab implementation (6.05.08) I found (traces of) a
> > > mechanism allowing the user to select resources from the search results
> > and
> > > perform a search/replace on them. If it works it seems this mechanism
> > could
> > > be (re)used.
> > >
> > > My questions:
> > > - do you have any thoughts on the above? Was it ever
> considered/dismissed
> > > to
> > > add this functionality?
> > > - is the selection mechanism functional (for search/replace) and would
> > > there
> > > be a reason it cannot be used for deletions as well?
> > > - any other advice/suggestions?
> > >
> > > Thanks,
> > >
> > > Reinier
> > >
> > > Reinier van den Born
> > > HintTech B.V.
> > >
> > > T: +31(0)88 268 25 00
> > > F: +31(0)88 268 25 01
> > > M: +31(0)6 494 171 36
> > >
> > > Delftechpark 37i | 2628 XJ Delft | The Netherlands
> > > www.hinttech.com<javascript:void('http://www.hinttech.com');>
> > >
> > > HintTech is a specialist in eBusiness Technology ( .Net, Java platform,
> > > Tridion ) and IT-Projects.
> > > Chamber of Commerce The Hague nr. 27242282 | Sales Tax nr.
> > > NL8062.16.396.B01
> > > ********************************************
> > > Hippocms-dev: Hippo CMS 6 development public mailinglist
> > >
> > > Searchable archives can be found at:
> > > MarkMail: http://hippocms-dev.markmail.org
> > > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
> > >
> > >
> > ********************************************
> > Hippocms-dev: Hippo CMS 6 development public mailinglist
> >
> > Searchable archives can be found at:
> > MarkMail: http://hippocms-dev.markmail.org
> > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
> >
> >
>
>
> --
> Reinier van den Born
> HintTech B.V.
>
> T: +31(0)88 268 25 00
> F: +31(0)88 268 25 01
> M: +31(0)6 494 171 36
>
> Delftechpark 37i | 2628 XJ Delft | The Netherlands www.hinttech.com
>
> HintTech is a specialist in eBusiness Technology ( .Net, Java platform,
> Tridion ) and IT-Projects.
> Chamber of Commerce The Hague nr. 27242282 | Sales Tax nr.
> NL8062.16.396.B01
> ********************************************
> Hippocms-dev: Hippo CMS 6 development public mailinglist
>
> Searchable archives can be found at:
> MarkMail: http://hippocms-dev.markmail.org
> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
>
>
********************************************
Hippocms-dev: Hippo CMS 6 development public mailinglist

Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html

Reply via email to