Skip to content

notes.md

Latest commit

 

History

History
58 lines (46 loc) · 3.13 KB

notes.md

File metadata and controls

58 lines (46 loc) · 3.13 KB
Raw

Notes

Business logic

// TODO: deleted

Vocabulary

  • Validity check for vocabularies

    • A new vocabulary will be created as long as there is no conflict with other vocabularies. A conflict happens when there is already another vocabulary with the same name. This also checks deprecated and replaced vocabularies, it doesn't make sense to create a vocabulary that was already deprecated.
    • The name of a vocabulary cannot contain spaces or special characters.
    • The name of a vocabulary cannot be updated, since it's used in URIs.

  • Deleting a vocabulary

    A vocabulary cannot be deleted, only deprecated.

  • Deprecate a vocabulary

    • A vocabulary can be deprecated with or without replacement.
    • A vocabulary that has concepts cannot be deprecated unless we deprecate its concepts too- if we don't do so the concepts will still appear in the searches. There is an option to deprecate a vocabulary and all its concepts - concepts will be deprecated without replacement.
    • When deprecating a vocabulary with replacement, its concepts will NOT be reassigned to the replacement - if we would reassign them it will be like a duplicate of the vocabulary

  • Restoring a deprecated vocabulary

    • Fields deprecated, deprecatedBy and replacedBy are set to null.
    • There is an option to restore a deprecated vocabulary and all its deprecated concepts.

Concept

  • Validity check for concepts

    • A new concept will be created as long as there is no conflict with other concepts within the same vocabulary. A conflict happens when there is already another concept with the same name, label, alternative label in the same language or hidden labels within the same vocabulary. This also checks deprecated concepts, it doesn't make sense to create a concept that was already deprecated. This conflicts are also checked when updating a concept.
    • A concept and its children must belong to the same vocabulary.
    • A concept cannot be created with a deprecated parent or a deprecated vocabulary.
    • A concept cannot be updated to a deprecated parent.
    • A concept cannot be transferred to another vocabulary.
    • The name of a concept cannot contain spaces or special characters
    • The name of a concept cannot be updated, since it's used in URIs.

  • Deleting a concept

    A concept cannot be deleted, only deprecated.

  • Deprecating a concept

    • A concept can be deprecated with or without replacement. The replacement must belong to the same vocabulary.
    • Any children of the concept being deprecated will be reassigned as children of the target.
    • A concept can be deprecated with no replacement only if it has no children or if we deprecate all the children too. There is an option to deprecate a concept and all its children - children will be deprecated without replacement.

  • Restore a deprecated concept

    • Fields deprecated, deprecatedBy and replacedBy are set to null.
    • If the restored concept has a parent deprecated, we update it with the current replacement.
    • There is an option to restore a concept and all its deprecated children.
    • A deprecated concept cannot be restored if its vocabulary is deprecated.