Project

General

Profile

bug #9199

Adapt TaxEditor to switch to originalSource for remaining single sourced objects

Added by Andreas Müller 3 months ago. Updated 2 days ago.

Status:
Feedback
Priority:
Highest
Assignee:
Category:
taxeditor
Target version:
Start date:
07/02/2020
Due date:
% Done:

50%

Severity:
normal
Found in Version:

Description

copied from #9116

It handles the same as #9116 but for the other SingleSourcedEntities mentioned in #6581


Related issues

Related to Edit - feature request #6581: Make all microreferenced references OriginalSources Closed 04/24/2017
Related to Edit - feature request #9192: Layout issues for source in taxonnode details Feedback 08/14/2020
Related to Edit - feature request #9298: Preference for IDinSource, IdNamespace and original information in nomenclatural reference details view New 11/13/2020
Follows Edit - feature request #9116: Adapt Editor to switch to originalSource for TaxonNode and improve layout of TaxonNode dialogue Closed 07/01/2020
Copied to Edit - feature request #9328: Adapt Editor to switch to originalSource for taxon secundum New 11/25/2020

Associated revisions

Revision 869cb64b (diff)
Added by Andreas Müller 3 months ago

ref ##9199, ref #6581, #9194 adapt TaxEditor to ReferencedEntityBase removal (has open issues)

Revision 82d37a4c (diff)
Added by Katja Luther 3 months ago

ref #9199: adapt editor to SingleSourcedEntityBase

Revision d74515be (diff)
Added by Katja Luther 3 months ago

ref #9199: continue adapt editor to singleSourcedEntities

Revision 8d33320b (diff)
Added by Katja Luther 3 months ago

ref #9199: continue adapt editor to singleSourcedEntities

Revision 7ca24c6e (diff)
Added by Katja Luther 3 months ago

ref #9199: TaxonNode should extend SingleSourcedEntityBase

Revision ce14d229 (diff)
Added by Katja Luther 3 months ago

ref #9199: TaxonNode is SingleSOurcedEntity

Revision 58e0cf09 (diff)
Added by Katja Luther 3 months ago

ref #9199: TaxonNode is SingleSOurcedEntity

Revision 7cf8a967 (diff)
Added by Andreas Müller 3 months ago

ref #9199 fix TaxonNode issues with new super class

Revision fcccac41 (diff)
Added by Andreas Müller 3 months ago

ref #9199 fix TaxonNode issues with new super class (cont.)

Revision 20a37084 (diff)
Added by Katja Luther 3 months ago

ref #9199: layout issues

Revision e154bb27 (diff)
Added by Andreas Müller 3 months ago

ref #9199, ref #9194 remove IReferencedEntity

Revision cd024235 (diff)
Added by Katja Luther 3 months ago

ref #9199: adapt nomenclatural status to original source and layout issues

Revision 13360a1e (diff)
Added by Katja Luther 3 months ago

ref #9199: adapt nom. ref, nom. status, typedes. elements to original source

Revision 0c28ee9b (diff)
Added by Katja Luther 3 months ago

ref #9199: adapt TypeDesignationBase to usage of source

Revision 8f36abc7 (diff)
Added by Katja Luther 18 days ago

ref #9199: fix problems with nomenclatural reference details

History

#1 Updated by Andreas Müller 3 months ago

  • Due date set to 07/02/2020
  • Start date changed from 08/19/2020 to 07/02/2020
  • Follows feature request #9116: Adapt Editor to switch to originalSource for TaxonNode and improve layout of TaxonNode dialogue added

#2 Updated by Andreas Müller 3 months ago

#3 Updated by Andreas Müller 3 months ago

#4 Updated by Andreas Müller 3 months ago

  • Target version changed from Release 5.19 to Release 5.18

#5 Updated by Andreas Müller 3 months ago

  • Due date deleted (07/02/2020)

#6 Updated by Katja Luther 3 months ago

  • Status changed from New to In Progress

adapted are the following elements:

  • Nomenclatural Status
  • Nomenclatural Reference
  • Taxonrelationships/NameRelationships
  • Typedesignations

missing:

  • secundum reference

#7 Updated by Katja Luther 10 days ago

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

This is fixed for all sources listed above, for sec reference I create a new ticket or we create a new one when the secundum reference is moved to original source as well?

#8 Updated by Katja Luther 10 days ago

  • % Done changed from 0 to 50

#9 Updated by Andreas Müller 3 days ago

#10 Updated by Andreas Müller 3 days ago

  • Subject changed from Adapt Editor to switch to originalSource for remaining single sourced objects to Adapt TaxEditor to switch to originalSource for remaining single sourced objects

#11 Updated by Andreas Müller 3 days ago

  • Related to feature request #9298: Preference for IDinSource, IdNamespace and original information in nomenclatural reference details view added

#12 Updated by Andreas Müller 3 days ago

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

Can we adapt single source layout according to nomenclatural source layout?

So we

  • move External Link up and - by default - show it not in the "more" section.
  • remove bold from External Link label
  • Relabel External Link => Link or Link(s)
  • do not use indentation for "more"
  • remove bold from "more" (not sure if really required, please check what looks better, if possible at all)

Only NameInSource should stay where it is by default. This needs to be decided from case to case.

#13 Updated by Andreas Müller 3 days ago

... for TaxonNodes.source we should keep indentation of "more" as it is followed by "Related persons"

#14 Updated by Katja Luther 3 days ago

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

I think this is fixed now. Please review.

#15 Updated by Andreas Müller 2 days ago

  • Assignee changed from Andreas Müller to Katja Luther

Yes, this looks much better. Only for nom. sources "more" is still bold. Can you adapt it there, too?

#16 Updated by Andreas Müller 2 days ago

  • Status changed from Resolved to Feedback

But it should be adapted for all single sources like for TaxonNode.source. So indentation is needed everywhere, except for nom. source where the Section only contains source information (there we should not have indentation for "Detail" if we don't have for other elements.

#17 Updated by Andreas Müller 2 days ago

Another layout issue somehow related: In external link, can we move the URI to the top and the type below URI? URI is the most important. Also there could be some little space between URI and Type and the space to "Description" could be reduced a bit.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)