feature request #7517
openMake search parameters like wildcards configurable
0%
Description
For edaphobase users are used to use whitespace as wildcard.
We should make search parameters project and/or client configurable.
Possible parameters are:
- handle whitespace as wildcard
- add wildcard at end of search string (MatchMode "Beginning")
- add wildcard at start of search string
- mask %
- case sensitivity
- ...
HINT:
Consider using eu.etaxonomy.cdm.persistence.dao.common.Restriction<T extends Object>instead of criteria in case wildcards need to be supported for arbitrary fields and related entities.
CdmEntityDaoBase.list(Class<? extends T> type, List<Restriction<?>> restrictions, Integer limit, Integer start, List<OrderHint> orderHints, List<String> propertyPaths) may serve you as an example for using the Restrictions.
Related issues
Updated by Andreas Kohlbecker about 6 years ago
- Assignee deleted (
Katja Luther)
I strongly suggest creating a profound specification for this before anything is being implementing for this issue!
I am also removing the assignee as this ticket is in the milestone for unassigned tickets.
Updated by Andreas Kohlbecker about 6 years ago
- Related to bug #5868: re-establish support for wildcard at start of query string (includes the query string '*' ) added
Updated by Andreas Kohlbecker about 6 years ago
- Related to bug #7525: IdentifiableServiceBase findByTitle(), and listByTitle() methods support cdm Restrictions and Criteria added
Updated by Andreas Kohlbecker about 6 years ago
- Tags changed from edapho to edapho, search
- Subject changed from Make search parameters configurable to Make search parameters like wildcards configurable
Updated by Andreas Kohlbecker about 6 years ago
- Description updated (diff)
- Status changed from New to Feedback
- Assignee set to Andreas Müller
I guess this is more a cdmlib issue than something to be implemented in the taxeditor. The service methods need to offer the option and the taxeditor will simply use them.
Or was setting the category to taxeditor by purpose?
Updated by Andreas Müller about 6 years ago
- Status changed from Feedback to New
- Assignee changed from Andreas Müller to Katja Luther
- Target version changed from Unassigned CDM tickets to Release 5.2
no, this is purely a taxeditor ticket. The service layer already offers many of these configurations but they can't be configured in the taxeditor. If further cdmlib methods are needed we need another ticket or implement them as needed.
Updated by Andreas Müller about 6 years ago
- Target version changed from Release 5.2 to Release 5.3
Updated by Katja Luther almost 6 years ago
- Target version changed from Release 5.3 to Release 5.4
Updated by Andreas Müller almost 6 years ago
- Target version changed from Release 5.4 to Release 5.5
Updated by Andreas Müller over 5 years ago
- Target version changed from Release 5.5 to Release 5.6
Updated by Katja Luther over 5 years ago
- Priority changed from New to Priority14
- Target version changed from Release 5.6 to Release 5.7
Updated by Katja Luther over 5 years ago
- Target version changed from Release 5.7 to Reviewed Next Major Release
Updated by Andreas Müller over 5 years ago
- Related to feature request #8058: Further issues for (local) preferences added