Project

General

Profile

task #2342

Open issues for DwC-A export

Added by Andreas Müller over 8 years ago. Updated over 1 year ago.

Status:
New
Priority:
Priority14
Category:
cdmadapter
Start date:
04/21/2011
Due date:
% Done:

0%

Severity:
major
Tags:

Description

wiki:DarwinCoreArchive

Open issues:

  • check that all best practices from http://code.google.com/p/gbif-ecat/wiki/BestPractices are included

  • investigate why relatedResources do not get into metaData.xml for cichorieae export

  • include used vocabularies in metadata.xml

  • fix eml.xml (it currently doesn't validate)

  • allow more configuration/filtering -> partly handled in #6754

  • Check all parameters again

  • document problems and configuration

  • document/implement missing parameters

  • allow higher classification handling -> first implementation: d2f7f487

  • remove always empty fields

  • ~refine progress monitoring~ -> #6799

  • implement logging that can be used by an Editor user -> first version #6754

  • ~large exports (split in parts)~ -> #6754

  • refactor such that metadata is created in the beginning

  • during export of cichoriea sometimes a "data too complex for specimen facade" error occurred (strange as we edit and import all data via the facade)

  • originalNameUsageId should link to the according concept (if it exists)

  • data needs to be consistent: if exporting while data are edited the set of core data needs to be fixed at the beginning

  • implement default fields such as the source field in core

  • correct handling of references (#7211)

<field default="http://wp6-cichorieae.e-taxonomy.eu/portal/?q=cdm_dataportal/taxon/{ID}" term="http://purl.org/dc/terms/source"/>

see also #2455 and #2457


Related issues

Related to Edit - feature request #6755: Make DwcA export available for annosys via web services Closed 06/26/2017
Related to Edit - task #6754: Adapt DwcA Export to CDM light export strategy Closed 06/26/2017
Related to Edit - bug #6799: Implement progress monitor for DwC A export Closed 07/11/2017
Related to Edit - bug #6984: withHeader is not yet working in DwC-A export Closed 09/26/2017
Related to Edit - task #7211: Strategy for DwC-A Export of references New 01/23/2018

Associated revisions

Revision d2f7f487 (diff)
Added by Andreas Müller almost 2 years ago

ref #2342 first implementation of higherClassification handling in DwC-A export

Revision 818cfd67 (diff)
Added by Andreas Müller almost 2 years ago

ref #2342 fix bug in higherClassification handling in DwC-A export and adapt tests

Revision 3429c491 (diff)
Added by Andreas Müller almost 2 years ago

ref #2342 ref 6755 fix some issues in higherClassification handling in DwC-A export

Revision f0c1c939 (diff)
Added by Andreas Müller almost 2 years ago

ref #2342 ref 6755 fix DwC-A export test

History

#1 Updated by Andreas Müller about 8 years ago

  • Priority changed from Highest to Priority14
  • Severity changed from critical to major
  • Tracker changed from feature request to bug

#2 Updated by Andreas Müller about 8 years ago

Wir wollten einen standard haben in dem der record den "join" von konzept/taxon und name darstellt.

Ein usage, ein Gebrauch eines Namens, ist daher recht unterschiedlich. Wenn ein taxonomicStatus oder parent/acceptedUsage(ID) gegeben ist, ist es definitiv ein taxon. Aber der name alleine mit nomenclaturalStatus und publishedIn kann auch rein nomenklatorisch genutzt werden.

Wie ist denn dann die BestPractice für die CoreIDs beim Export von Daten, die wie das CDM Identifier für beides hat, Konzepte und Namen. Ich habe jetzt erstmal idR die Identifier der Konzepte verwendet und alle Informationen, also nomenklatorische und konzeptbezogene in einen Record zu bekommen, bekomme dabei aber die genannten Probleme. Gleichzeitig hat das natürlich auch eine Reihe Vorteilen beim verarbeiten der Daten durch Applikationen, die keine Trennung zwischen Namen und Konzepten implementieren.

Alternativ wäre es natürlich denkbar, jeweils einen Datensatz für das Konzept und einen für den Namen (als das Nominalkonzept) zu verwenden.

Ideal wäre immer to konzekt id zu benutzen wenn vorhanden. Falls es nur einen namen gibt könnten man evtl ein Nominalkonzept on the fly erzeugen?

Also auf jeden Fall keine 2 Records, richtig? Nominalkonzept wäre kein Problem, ein Name, an dem bereits eine nomRef steht ist ja quasi schon ein Konzept. Ich nehme dann einfach die ID des Namens und fertig.

Markus

#3 Updated by Andreas Müller about 8 years ago

Replying to a.mueller:

ja, genau so wäre es perfekt! (Markus)

#4 Updated by Andreas Müller almost 2 years ago

#5 Updated by Andreas Müller almost 2 years ago

  • Description updated (diff)
  • Private changed from Yes to No

#6 Updated by Andreas Müller almost 2 years ago

  • Description updated (diff)

#7 Updated by Andreas Müller almost 2 years ago

  • Description updated (diff)

#8 Updated by Andreas Müller almost 2 years ago

  • Related to task #6754: Adapt DwcA Export to CDM light export strategy added

#9 Updated by Andreas Müller almost 2 years ago

  • Description updated (diff)

#10 Updated by Andreas Müller almost 2 years ago

  • Related to bug #6799: Implement progress monitor for DwC A export added

#11 Updated by Andreas Müller almost 2 years ago

  • Description updated (diff)

#12 Updated by Andreas Müller almost 2 years ago

  • Description updated (diff)

#13 Updated by Andreas Müller almost 2 years ago

  • Tracker changed from bug to task

#14 Updated by Andreas Müller over 1 year ago

  • Tags set to dwca
  • Subject changed from Implement DwC-A export to Open issues for DwC-A export

#15 Updated by Andreas Müller over 1 year ago

  • Description updated (diff)

#16 Updated by Andreas Müller over 1 year ago

  • Related to bug #6984: withHeader is not yet working in DwC-A export added

#17 Updated by Andreas Müller over 1 year ago

  • Related to task #7211: Strategy for DwC-A Export of references added

#18 Updated by Andreas Müller over 1 year ago

  • Description updated (diff)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)