feature request #8489
openFurther issues for DB preferences
50%
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 dialogueboth 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
Related issues
Updated by Andreas Müller over 3 years ago
- Related to bug #8385: Open issues in DB preferences added
Updated by Andreas Müller over 3 years ago
- Related to bug #8389: Correct handling of default values with allowOverride=false added
Updated by Andreas Müller over 3 years ago
- Related to bug #8494: Better ABCD Preferences Page added
Updated by Katja Luther over 3 years ago
- Description updated (diff)
- Status changed from New to In Progress
Updated by Katja Luther over 3 years ago
- Related to bug #8382: Local Supplemental Data Source Preferences should reflect the state of admin preferences added
Updated by Katja Luther over 3 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
Updated by Andreas Kohlbecker over 3 years ago
- File picture028-1.png picture028-1.png added
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.
Updated by Andreas Müller over 3 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)
Updated by Katja Luther over 3 years ago
- Target version changed from Release 5.11 to Release 5.12
Updated by Katja Luther about 3 years ago
- Target version changed from Release 5.12 to Release 5.13
Updated by Andreas Müller about 3 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.
Updated by Andreas Müller about 3 years ago
- Copied to task #8818: Remaining issues for DB preferences added