Project

General

Profile

feature request #7810

DB preference to make all Specimen functionality/menu items invisible

Added by Katja Luther 10 months ago. Updated 3 months ago.

Status:
Feedback
Priority:
Highest
Assignee:
Category:
taxeditor
Target version:
Start date:
10/08/2018
Due date:
% Done:

50%

Severity:
normal
Tags:

Description

if the preference is set to false everything concerning specimen should be disabled:

  • imports
  • Specimen TypeDesignations
  • bulk editors
  • to be continued

picture585-1.png View (3.06 KB) Andreas Müller, 10/24/2018 12:12 AM


Related issues

Related to Edit - bug #7849: Improve DB Preferences handling and saving in TaxEditor Feedback 10/23/2018
Copied from Edit - feature request #7793: Master ticket for E+M editor issues Feedback 09/27/2018

Associated revisions

Revision 3b975922 (diff)
Added by Katja Luther 10 months ago

ref #7793: add DB preferences to hide specimen and import issues and smaller changes in db preferences

Revision 69be3e73 (diff)
Added by Katja Luther 10 months ago

ref #7793: add preference to hide all specimen related issues

Revision 53d9aad0 (diff)
Added by Patrick Plitzner 10 months ago

fix #7810 Fix saving of specimen DB preferences

  • failed to save when initally no preferences were set

Revision 4e6f2196 (diff)
Added by Katja Luther 10 months ago

fix save of db preferences not available in db before

Revision c4c36f8e (diff)
Added by Patrick Plitzner 10 months ago

ref #7810 Fix creation of local specimen preferences

Revision f662104a (diff)
Added by Patrick Plitzner 10 months ago

ref #7810 Fix setting of specimen admin prefs

Revision 06ae687f (diff)
Added by Patrick Plitzner 6 months ago

ref #7810 Fix preference check for "Open in Specimen Editor"

  • remove unused IPreferenceKey

Revision d8ff3161 (diff)
Added by Patrick Plitzner 6 months ago

ref #7810 Fix preference check for "Open in Specimen Editor"

  • remove unused IPreferenceKey

History

#1 Updated by Katja Luther 10 months ago

#2 Updated by Katja Luther 10 months ago

  • Status changed from New to In Progress

#3 Updated by Andreas Müller 10 months ago

  • Status changed from In Progress to Resolved
  • Assignee changed from Katja Luther to Andreas Müller
  • % Done changed from 0 to 60

I think this was mostly fixed in the master ticket. Put to resolved to do the review if something is still missing. I added also 2 of the master ticket commits to this ticket.

#4 Updated by Andreas Müller 10 months ago

Currentyl can't test because preference can not be stored. See also #7849

#5 Updated by Andreas Müller 10 months ago

  • Status changed from Resolved to Feedback

#6 Updated by Andreas Müller 10 months ago

  • Related to bug #7849: Improve DB Preferences handling and saving in TaxEditor added

#7 Updated by Patrick Plitzner 10 months ago

  • Status changed from Feedback to Resolved
  • % Done changed from 60 to 50

#8 Updated by Katja Luther 10 months ago

the check for the existence of the preference is needed to check whether the page was opened or not, because the preference framework run the performOK() method on all pages also if they are not changed before. BUt I added the creation of a new preference object if there was no in db before if the page is opened.

#9 Updated by Andreas Müller 10 months ago

Specimen imports are still shown.

Note: this might be easier to handle if we group imports by type as mentioned some time ago. Than we need only to disable the "specimen" submenu which includes all specimen imports then.

Exports for specimen we currently do not have.

#10 Updated by Andreas Müller 10 months ago

TermEditor term types DnaMarker, DeterminationModifier, KindOfUnit can also be disabled (maybe we can implement this by letting the terms know if they are relevant only for specimen).

#11 Updated by Andreas Müller 10 months ago

In preferences we could disable the Taxonomic-TypeDeignations(Specimen) part.

#12 Updated by Andreas Müller 10 months ago

In name details view for all names of rank species and below we could remove the type designations section

#13 Updated by Andreas Müller 10 months ago

In Facts View we could remove all Features that need specimen support, or at least remove support for IndividualsAssociation Fact type. I think we should not remove support for Specimen/Observation/MaterialsExamined freetext support as this could be too restrict.
Features should be restricted via other functionalities.

#14 Updated by Andreas Müller 10 months ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Andreas Müller to Katja Luther

Also we may want to disable the "Derivatives" perspective.

#15 Updated by Andreas Müller 10 months ago

Also it is not yet possible to select "allow override" if specimen are switched off in DB preferences.

#16 Updated by Andreas Müller 10 months ago

In lokal preferences the "Specimens and FieldUnits" page is now always empty, even if showSpecimen = true. What was there before.

#17 Updated by Andreas Müller 10 months ago

Bulk Editor-"ShowFieldUnits in Specimen Editor (list) should be disabled.
However, we need move this to an other page for anyway. (We should have a page for each bulk editor where we can define specific bulk editor behaviour. If specimens are switched of, the complete page and menu entry should be invisible.

#18 Updated by Andreas Müller 10 months ago

  • Tags set to euro+med

#19 Updated by Patrick Plitzner 6 months ago

@Katja: Can you take a look at my last commit please taxeditor|06ae687fc2061c691d70c87b1da7e8b41b903385

@all: Why is this ticket still open? What is left to do?

#20 Updated by Katja Luther 6 months ago

Patrick Plitzner wrote:

@Katja: Can you take a look at my last commit please taxeditor|06ae687fc2061c691d70c87b1da7e8b41b903385

looks correct.

@all: Why is this ticket still open? What is left to do?

#21 Updated by Andreas Müller 6 months ago

Patrick Plitzner wrote:

@all: Why is this ticket still open? What is left to do?

Isn't this quite obvious. See comments #9 - #17

#22 Updated by Patrick Plitzner 6 months ago

Andreas Müller wrote:

Patrick Plitzner wrote:

@all: Why is this ticket still open? What is left to do?

Isn't this quite obvious. See comments #9 - #17

I see. Sorry, the question was rather "Why is this on Release 5.4?"

#23 Updated by Andreas Müller 6 months ago

Because some major issues were implemented in 5.4. However, I think we should split the ticket for all remaining issues, rename this so that it describes what was done and close it then.

#24 Updated by Katja Luther 3 months ago

  • Description updated (diff)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)