Actions
feature request #9539
openImplement availableFor for ExtensionType, MarkerType, AnnotationType and IdentifierType
Start date:
Due date:
% Done:
0%
Estimated time:
Severity:
major
Description
Similar to Features #9027
We may need to decide for all existing Types what they should support by default. Also we need to write an update script for the default values and for already existing uses (what ever usage exists in a database we expect the availableFor shold be set for the combination in this database).
The field should not be managed by term server.
Maybe we need a new DefinedTermBase subclass AvailableForTerm or even 2 AvailableForIndentEntity and subclassing from the previous AvailableForAnnotatableEntity. These may offer boolean methods for each availableFor class
Related issues
Updated by Andreas Müller over 3 years ago
- Related to feature request #9027: Implement Feature.availableFor added
Updated by Andreas Müller over 3 years ago
- Related to feature request #9079: Move supported and available for parts of feature detail element to sections added
Updated by Andreas Müller over 3 years ago
- Status changed from New to In Progress
Updated by Andreas Müller over 1 year ago
- Related to feature request #10260: Add resolve mechanism to (external) identifiers added
Updated by Andreas Müller over 1 year ago
- Related to task #8840: Display identifiers in the dataportal added
Updated by Andreas Müller 3 months ago
- Related to bug #10515: Display further identifiers in the dataportal added
Updated by Andreas Müller 2 months ago
- Related to task #10532: Remaining issues for Cichorieae WFO import added
Updated by Andreas Müller 2 months ago
- Target version changed from CDM UML 5.46 to Release 5.44
Updated by Andreas Müller about 2 months ago
- Target version changed from Release 5.44 to Release 5.46
Updated by Andreas Müller about 2 months ago
- Target version changed from Release 5.46 to Release 5.45
Updated by Andreas Müller 30 days ago
- Target version changed from Release 5.45 to Release 5.45a
Actions