Project

General

Profile

bug #7340

OderedVocabularies are initialised with DefinedTerms

Added by Patrick Plitzner 9 months ago. Updated 7 months ago.

Status:
Closed
Priority:
Priority14
Category:
cdmlib
Target version:
Start date:
03/29/2018
Due date:
% Done:

100%

Severity:
normal
Found in Version:

Description

In Campanula production I tried adding a new term for all term vocabularies.
This fails for OrderTermVocabularies because the fallback, when creating a new term, is creating a DefinedTerm which results in a ClassCastException when adding to an OrderedTermVocabulary (TermType.getEmptyDefinedTermBase()).
This happens for:

  • DeterminationModifier:
  • Modifier:
  • Stage:
  • Sex:
  • Scope:

Additionally, in Campanula production, for the following term types a class cast exception happens because they are initialised with DefinedTerms although they are OrderedTermVocabularies:

  • Sex
  • Determination Modifier

Related issues

Related to Edit - bug #6343: TermVocabularies of OrderedTerms must be OrderedVocabularies In Progress 01/18/2017

Associated revisions

Revision 5c0f124f (diff)
Added by Andreas Müller 7 months ago

ref #7340 make DeterminationModifier and Sex default vocabularies unordered

History

#1 Updated by Andreas Müller 7 months ago

  • Related to bug #6343: TermVocabularies of OrderedTerms must be OrderedVocabularies added

#2 Updated by Andreas Müller 7 months ago

  • Status changed from New to Resolved
  • Assignee changed from Andreas Müller to Patrick Plitzner
  • Priority changed from New to Priority14
  • Target version changed from Unassigned CDM tickets to Release 5.1

By definition these terms and there vocabularies should not be ordered. The following attributes are all of type DefinedTerm and NOT DefinedTermBase and therefore are NOT ordered.

SpecimenOrObservationBase.sex
SpecimenOrObservationBase.lifeStage
DeterminationEvent.modifier
DescriptionElementBase.modifier
StateData.modifiers
StatisticalMeasurementValue.modifiers
IIdentificationKey.getScopeRestrictions
TaxonDescription.scopes

I did set all vocabularies and their terms to non-ordered on all DBs on production, test and integration. An according update script for other database will run within #6343. The according SQL statements to update local databases before can be found there.

The csv files for Sex and Determination Modifier needed to be updated (see changeset)

#3 Updated by Andreas Müller 7 months ago

  • % Done changed from 0 to 50

#4 Updated by Patrick Plitzner 7 months ago

  • Status changed from Resolved to Closed
  • Assignee changed from Patrick Plitzner to Andreas Müller
  • % Done changed from 50 to 100

I tried creating a new term for the above mentioned vocabularies and everything worked fine.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)