A more efficient Clipboard-generated custom filter

Regarding a special case for this:
making custom filters from the Clipboard

When you select a set of objects in the Gramps objects, one of the context menu options is to “Create Filter from the <object type> selected…”

And it creates an RegEx based ID search custom filter using the “<object type> with Id containing <text>” rule.

A RegEx string match against IDs seems very computationally expensive given that the Clipboard (and List Views) already have a list of the handles for all those objects. And the custom filter happens last in the Filter Gramps. A (pre-sorted) list of handles seems as though it could do a huge row reduction as the first step… before any of the other Filter Gramplet parameters were applied.

Note: I often have “worklists” of People, Events, or Places that have to be processed. I would like to be able to work a “list of objects” without the long reprocessing inherent to the Filter Gramplet every time an object is changed. It would be more intuitive if the Worklist could be “viewed/subtracted from/added to” in a window using an object-list table like that of the Clipboard.

Another use case for “sets”. :slight_smile:

Would a “named clipboard” work? For example, just a persistent clipboard saved/loaded by name?

[@emyoulation This is off-topic from the thread started in 2024. It would be much better if we started new topics, even if perhererially related to an old topic. You can link to the old topic if you think it is related. In this example, it is not.]

Strangely, no, it would not provide full function.

It is often necessary to use that Clipboard-generated (worklist pre-filter?) Custom Filter in combination with other Filter Gramplet items, reports, exports, or with Gramplets in the list view. So having a faster, earlier Handle-based Custom Filter available in all those places will increase flexibility and performance. But a familiar “Named Clipboard” interface for adding, sorting, and removing Handles list would make it more user-friendly.

Use case:

I import a GEDCOM and it adds a crapload of duplicate Places. So I clipboard all the newly modified records from the Places Flat view sorted on Last Changed column. This is my worklist.

I apply it as a filter to the Place Tree view mode in the Places and use it for navigation in (“walking through”) the worklist. Then use the flat list Places view mode to look for pre-existing Places to merge.
For remaining unmerged Places in the Worklist, I will use the References gramplet in the bottom bar for each place and ponder whether there are enough justify adding a new Place to the Place hierarchy with assistance of the Place Cleanup addon.

For one-off references, I might decide to transcribe the new part of the Place Title in the Event description and use an Enclosing Place for the Event’s Place selection. Then delete the Worklist Place which no longer has any references.