@myrmidon/cadmus-refs-asserted-ids 10.0.12 → 10.0.14
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -16,6 +16,8 @@ This project was generated using [Angular CLI](https://github.com/angular/angula
|
|
|
16
16
|
- [Asserted Composite ID](#asserted-composite-id)
|
|
17
17
|
- [Asserted Composite IDs](#asserted-composite-ids)
|
|
18
18
|
- [History](#history)
|
|
19
|
+
- [10.0.14](#10014)
|
|
20
|
+
- [10.0.13](#10013)
|
|
19
21
|
- [10.0.10](#10010)
|
|
20
22
|
- [10.0.9](#1009)
|
|
21
23
|
- [10.0.8](#1008)
|
|
@@ -93,6 +95,7 @@ Various components from this library provide a different level of complexity, so
|
|
|
93
95
|
- `assertion-tags` (for `assTagEntries`).
|
|
94
96
|
- `doc-reference-types` (for `refTypeEntries`).
|
|
95
97
|
- `doc-reference-tags` (for `refTagEntries`).
|
|
98
|
+
- `asserted-id-features` (for `featureEntries`).
|
|
96
99
|
- 🔥 output:
|
|
97
100
|
- `idChange` (`AssertedId`)
|
|
98
101
|
- `editorClose`
|
|
@@ -103,6 +106,8 @@ The asserted ID component allows editing a simple model representing a generic I
|
|
|
103
106
|
- **value**: the ID itself.
|
|
104
107
|
- **scope**: the context the ID originates from (e.g. an ontology, a repository, a website, etc.).
|
|
105
108
|
- an optional **tag**, used to group or classify the ID.
|
|
109
|
+
- an optional set of **features**, from a hierarchical thesaurus. For instance, these could be the role(s) of a person linked to an object, like customer, seller, creator, etc.
|
|
110
|
+
- an optional **note**.
|
|
106
111
|
- an optional **assertion**, used to define the uncertainty level of the assignment of this ID to the context it applies to.
|
|
107
112
|
|
|
108
113
|
The asserted ID component provides an internal lookup mechanism based on data pins and metadata conventions. When users want to add an ID referring to some internal entity, either found in a part or corresponding to an item, he just has to pick the type of desired lookup (when more than a single lookup search definition is present), and type some characters to get the first N pins starting with these characters; he can then pick one from the list. Once a pin value is picked, the lookup control shows all the relevant data which can be used as components for the ID to build:
|
|
@@ -184,6 +189,7 @@ An editable list of asserted IDs.
|
|
|
184
189
|
- `assertion-tags` (for `assTagEntries`)
|
|
185
190
|
- `doc-reference-types` (for `refTypeEntries`)
|
|
186
191
|
- `doc-reference-tags` (for `refTagEntries`)
|
|
192
|
+
- `asserted-id-features` (for `featureEntries`).
|
|
187
193
|
- 🔥 output:
|
|
188
194
|
- `idsChange` (`AssertedId[]`)
|
|
189
195
|
|
|
@@ -378,6 +384,14 @@ A collection of asserted composite IDs.
|
|
|
378
384
|
|
|
379
385
|
## History
|
|
380
386
|
|
|
387
|
+
### 10.0.14
|
|
388
|
+
|
|
389
|
+
- 2026-02-01: minor fix to pin target lookup component template.
|
|
390
|
+
|
|
391
|
+
### 10.0.13
|
|
392
|
+
|
|
393
|
+
- 2026-01-17: added `features` (from thesaurus `asserted-id-features`) and `note` to asserted IDs.
|
|
394
|
+
|
|
381
395
|
### 10.0.10
|
|
382
396
|
|
|
383
397
|
- 2025-09-15: refactored `AssertedIdsComponent` and `AssertedCompositeIdsComponent` dropping form.
|