Allow user not to select a Content Model

[bondjimbond]

We have four options now with which to select objects' "find" parameters: CModel, namespace, collection, or date range. CModel should not be required - there are plenty of cases in which more than one CModel might be represented in a set of objects that need a find/replace operation.

Instead of making CModel required, we should check for the presence of any one of the conditions in order to run the batch operation.

[DiegoPino]

My only question could be book pages? Never part of a collection, namespaces can be quite intriguing too when dealing with them. That said, i agree with you, it makes selecting mixed cmodel collections a mess (too many iterations). What i would like to have is an option to use a Arbitrary Solr query applied to find and replace. Like an option that uses an existing search query from the main search interface (adding a tiny button) and feeds that one into this module. Anyway, So yeah, lets remove that CMODEL required condition and lets allow cmodel to be optional. +1 on that

[bondjimbond]

What i would like to have is an option to use a Arbitrary Solr query applied to find and replace.

You could snip that code out of https://github.com/ulsdevteam/islandora_datastreams_io pretty easily, I imagine.

Like an option that uses an existing search query from the main search interface (adding a tiny button) and feeds that one into this module.

Now that would be cool; I've found it a bit tough to create by hand working Solr queries for these sorts of modules.

[DiegoPino]

Wonder if you still need this? since i'm doing stuff here...

[bondjimbond]

Yep, it's still a nice option.

[DiegoPino]

Ok. So if you can test that new #14 pull If all is well i will add Will's undo/revert batch pull and that extra "no CMODEL" option.