Opened 5 years ago

Last modified 5 months ago

#562 _started enhancement

Allow to define "field transfer sets" in merge-tool / importer / exporter

Reported by: westram Owned by: westram
Priority: major Milestone: r18
Component: ARB_MERGE Version: SVN
Keywords: Cc:

Description (last modified by westram)

Feature should provide similar functionality as

ARB_MERGE/Transfer species/Source->Target/Define field transfer for gene-species

(only available in genome-DBs!)

Wanted procedure:

  • define "field transfer set" (FTS)
  • in merge-tool FTS can be used to
    • Transfer selected species
    • Transfer listed species
    • Transfer field of listed species (makes no sense)
  • in importer FTS can be used as post-import-transformation
  • in exporter FTS can be used as pre-export-transformation

Data stored for each FTS:

  • name + comment
  • list of transfer rules (TR)
  • whether to copy undefined fields (i.e. fields that are neither defined as target- nor as source-field in any TR)
    • list of fields to exclude from copying

Data stored for each TR:

  • source field(s), if multiple:
    • need defined order
    • need separator (default: "; ")
  • ACI to modify content (optional)
  • target field

GUI:

  • currently selected FTS (as button?) in
    • merge species window (merge-tool)
    • import window
    • export window

press that button ⇒ open FTS selection window

  • FTS selection window:
    • list of defined FTS
    • simple admin interface (delete, copy, create)
    • edit button (opens FTS definition window)
  • FTS definition window:
    • comment field
    • list of existing TR
    • GUI elements for TR (source field, ACI, target field)
      • either showing selected TR or defining new TR
    • toggle (copy undefined fields?)
      • comma-separated list of fields to never copy
    • simple admin interface (delete selected TR)

Usability:

It would be nice if fields could be selected from lists (additionally to specifying them via input filed). For that purpose the module shall be provided with callbacks to extract possible (or known) source- and target-fields.

when used in source-fields target-fields
merge tool fields existing in source DB fields existing in target DB
importer fields existing after import
(as test import does)
fields existing in DB
exporter fields existing in DB fields accessed by export-filter
too complicated

Change History (6)

comment:1 Changed 22 months ago by westram

  • Description modified (diff)
  • Milestone set to proposals
  • Owner changed from devel to westram
  • Status changed from new to accepted
  • Summary changed from Allow to define "field transfer sets" in merge tool to Allow to define "field transfer sets" in merge-tool / importer

comment:2 Changed 17 months ago by westram

  • Milestone changed from proposals to wishlist
  • Priority changed from normal to major

comment:3 Changed 17 months ago by westram

  • Description modified (diff)
  • Summary changed from Allow to define "field transfer sets" in merge-tool / importer to Allow to define "field transfer sets" in merge-tool / importer / exporter

comment:4 Changed 15 months ago by westram

  • Milestone changed from wishlist to r18

comment:5 Changed 6 months ago by westram

  • Status changed from accepted to _started

comment:6 Changed 5 months ago by westram

  • Description modified (diff)

multiple source-fields should be possible ⇒ need order and separator

Last edited 5 months ago by westram (previous) (diff)
Note: See TracTickets for help on using tickets.