Moox Data
moox/data
as well as the Data Base Entity in Moox Core.
Background:
For Data packages like Incoterms we need a new base entity named "Data".
Entry is a mix of Record and Draft, or simply Draft without publish funcionality.
Most Data packages - if not all - will use Data as Base, what compared to records, adds the translatable functionality as well as some basic features to toggle status.
Fields and Features:
Package (to copy)
- ID
- Slug
- Title
- Code (specify)
- Common name
- Localized name (translation)
- Synonyms (translation?)
- Data
Base (Features)
- is_active (to query)
- is_default (e. g. EUR = default)
- is_system (all from API)
- is_custom (all manually created)
- is_locked (should not be overwritten by Job)
- valid_from
- vaild_until
- sort_order (table sortable)
- source (e. g. Incoterms)
- source_url (e. g. wikipedia/incoterms)
- source_version (e. g. 2020)
- timestamps + differenciate between api/manual + user_id who created or changed
- created_at
- updated_at
- created_by
- created_by_type
- updated_by
- updated_by_type
- activity_log_id (tbd)
Moox Data
moox/data
as well as the Data Base Entity in Moox Core.
Background:
For Data packages like Incoterms we need a new base entity named "Data".
Entry is a mix of Record and Draft, or simply Draft without publish funcionality.
Most Data packages - if not all - will use Data as Base, what compared to records, adds the translatable functionality as well as some basic features to toggle status.
Fields and Features:
Package (to copy)
Base (Features)