Project

General

Profile

Actions

feature request #10284

closed

Allow term trees as filters for named area dialogues

Added by Andreas Müller over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Highest
Assignee:
Category:
taxeditor
Target version:
Start date:
Due date:
% Done:

70%

Estimated time:
Severity:
major
Tags:

Description

... and others if others exist.
In future, the filter should only work on term trees.
This is needed for eFloraMex as here we use distribution areas from multiple vocabularies.


Related issues

Related to EDIT - task #10283: Add mapping for non-mexican areas for eFloraMexNewAndreas Müller

Actions
Related to EDIT - feature request #6794: Improve term structureIn ProgressAndreas Müller

Actions
Related to EDIT - bug #9504: Changing term tree title is not persistedClosedKatja Luther

Actions
Actions #1

Updated by Andreas Müller over 1 year ago

  • Related to task #10283: Add mapping for non-mexican areas for eFloraMex added
Actions #2

Updated by Andreas Müller over 1 year ago

Actions #3

Updated by Andreas Müller about 1 year ago

  • Priority changed from New to Highest
  • Target version changed from Release 5.49 to Release 5.37
  • Severity changed from normal to major

We should have a look if this can be included in current milestone as urgently needed for eFloraMex

Actions #4

Updated by Andreas Müller about 1 year ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 70

This works well for the filtering. Maybe some little fine tuning can be done for the preference (DB+local) + filter handling.

E.g. if a DB pref without "allow override" exists it should not be possible to select not selected term collections via the filter. Also the defaults for the local preferences should adapt to the DB prefs in case of "allow override". But this can be handled in a new ticket maybe.

Actions #5

Updated by Andreas Müller about 1 year ago

  • Related to bug #9504: Changing term tree title is not persisted added
Actions #6

Updated by Katja Luther about 1 year ago

  • Status changed from Resolved to Closed

Andreas Müller wrote in #note-4:

This works well for the filtering. Maybe some little fine tuning can be done for the preference (DB+local) + filter handling.

E.g. if a DB pref without "allow override" exists it should not be possible to select not selected term collections via the filter. Also the defaults for the local preferences should adapt to the DB prefs in case of "allow override". But this can be handled in a new ticket maybe.

I would create a new ticket so we can release.

Actions

Also available in: Atom PDF