Project

General

Profile

Actions

feature request #8489

open

Further issues for DB preferences

Added by Andreas Müller over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
New
Category:
taxeditor
Target version:
Start date:
Due date:
% Done:

50%

Estimated time:
Severity:
normal

Description

  • Common names vocabulary select list:
    • has no "allow override" (as not yet present in local preferences)
    • selected vocabularies should be shown without opening the dialogue
    • both could be implemented similar to distribution data
    • => this is implemented analogue to the term selection pages (also for named area vocabularies for distributions)
  • Distribution data-vocabulary selection:
    • table is not yet updated after new status selection
  • ABCD:
    • Map UnitID ... => should be a dropdown
    • See also #8494
  • Ranks, Nomenclatural Status (and probably other such lists):
    • Restore default in local preferences does not set the values to DB pref values but selects the complete list
    • "Use default settings" does not show the default settings in the list (and disables the list(?))
  • Adapt menu to local prefs menu (use same structure)
  • TBC

Files

picture028-1.png (85.2 KB) picture028-1.png Andreas Kohlbecker, 10/17/2019 06:32 PM

Related issues

Related to EDIT - bug #8385: Open issues in DB preferencesClosedKatja Luther

Actions
Related to EDIT - bug #8389: Correct handling of default values with allowOverride=falseResolvedAndreas Müller

Actions
Related to EDIT - bug #8494: Better ABCD Preferences Page In ProgressKatja Luther

Actions
Related to EDIT - bug #8382: Local Supplemental Data Source Preferences should reflect the state of admin preferencesClosedKatja Luther

Actions
Copied to EDIT - task #8818: Remaining issues for DB preferencesNewKatja Luther

Actions
Actions #1

Updated by Andreas Müller over 4 years ago

  • Related to bug #8385: Open issues in DB preferences added
Actions #2

Updated by Andreas Müller over 4 years ago

  • Related to bug #8389: Correct handling of default values with allowOverride=false added
Actions #3

Updated by Andreas Müller over 4 years ago

  • Related to bug #8494: Better ABCD Preferences Page added
Actions #4

Updated by Andreas Müller over 4 years ago

  • Description updated (diff)
Actions #5

Updated by Andreas Müller over 4 years ago

  • Description updated (diff)
Actions #6

Updated by Katja Luther over 4 years ago

  • Description updated (diff)
Actions #7

Updated by Katja Luther over 4 years ago

  • Description updated (diff)
Actions #8

Updated by Katja Luther over 4 years ago

  • Description updated (diff)
Actions #9

Updated by Katja Luther over 4 years ago

  • Description updated (diff)
Actions #10

Updated by Katja Luther over 4 years ago

  • Description updated (diff)
Actions #11

Updated by Katja Luther over 4 years ago

  • Description updated (diff)
Actions #12

Updated by Katja Luther over 4 years ago

  • Description updated (diff)
Actions #13

Updated by Katja Luther over 4 years ago

  • Description updated (diff)
  • Status changed from New to In Progress
Actions #14

Updated by Katja Luther over 4 years ago

  • Description updated (diff)
Actions #15

Updated by Katja Luther over 4 years ago

  • Related to bug #8382: Local Supplemental Data Source Preferences should reflect the state of admin preferences added
Actions #16

Updated by Katja Luther over 4 years ago

  • Target version changed from Release 5.10 to Release 5.11

move to 5.11 for a last review whether all (wanted) preferences are available as db preferences

Actions #17

Updated by Andreas Kohlbecker over 4 years ago

I have some more probelms for which I did not find mentioned in here:

Further Problem:

  • when I set the subject to for example "Germany" I find no means to reset it to "Default" except of using the delete Button
  • The function of the Delete button seems a bit strange: The Predicate is only set to Deleted. A general user would expect the whole thing to be vanished.
  • Restore Default has no effect, what should happen when there are multiple properties?

  • I found out that after using the Status Selection Button a new property is being created. Does this happen when the first entry is not the default one?

  • Showing the predicate string makes not much sense since this is always the same.

Actions #18

Updated by Andreas Müller over 4 years ago

Andreas Kohlbecker wrote:

  • when I set the subject to for example "Germany" I find no means to reset it to "Default" except of using the delete Button

deleting the preference equals setting it to default

  • The function of the Delete button seems a bit strange: The Predicate is only set to Deleted. A general user would expect the whole thing to be vanished.
  • Restore Default has no effect, what should happen when there are multiple properties?

What do you mean by "properties"? Subjects? Preferences?
In general the semantics of "restore default" for a given page is that ALL data available on the page is set to default (which is similar to all relevant preferences are deleted). But I have not checked if it is implemented such.

  • I found out that after using the Status Selection Button a new property is being created. Does this happen when the first entry is not the default one?

  • Showing the predicate string makes not much sense since this is always the same.

true, at least if ONLY 1 predicate type is edited on the page, which is not always the case, but at least in the table it should always be the case. Therefore a good label could replace the predicate table (anyway the current string should be replaced by a good label)

Actions #19

Updated by Katja Luther over 4 years ago

  • Target version changed from Release 5.11 to Release 5.12
Actions #20

Updated by Katja Luther about 4 years ago

  • Target version changed from Release 5.12 to Release 5.13
Actions #21

Updated by Andreas Müller about 4 years ago

  • Status changed from In Progress to Resolved
  • Assignee changed from Katja Luther to Andreas Müller
  • Target version changed from Release 5.13 to Release 5.10
  • % Done changed from 0 to 50

putting back to 5.10 for review, no changes since then. Follow up ticket for open issues: #8818.
During review put non-working/open issues to follow up ticket.

Actions #22

Updated by Andreas Müller about 4 years ago

  • Copied to task #8818: Remaining issues for DB preferences added
Actions

Also available in: Atom PDF