pyegeria 5.3.10__py3-none-any.whl → 5.4.0.dev2__py3-none-any.whl

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.
Files changed (69) hide show
  1. commands/cat/debug_log.2025-06-05_20-24-18_123924.log.zip +0 -0
  2. commands/cat/debug_log.2025-06-10_08-45-03_929921.log.zip +0 -0
  3. commands/cat/debug_log.2025-06-11_09-57-21_247890.log.zip +0 -0
  4. commands/cat/debug_log.2025-06-12_16-14-31_212042.log.zip +0 -0
  5. commands/cat/dr_egeria_md.py +32 -5
  6. commands/cat/list_collections.py +10 -4
  7. commands/cat/list_data_designer.py +171 -0
  8. md_processing/__init__.py +7 -2
  9. md_processing/data/commands.json +4666 -848
  10. md_processing/md_commands/data_designer_commands.py +840 -557
  11. md_processing/md_commands/solution_architect_commands.py +985 -0
  12. md_processing/md_processing_utils/common_md_proc_utils.py +262 -89
  13. md_processing/md_processing_utils/common_md_utils.py +11 -4
  14. md_processing/md_processing_utils/md_processing_constants.py +18 -16
  15. pyegeria/_client.py +39 -0
  16. pyegeria/classification_manager_omvs.py +1 -1
  17. pyegeria/collection_manager_omvs.py +248 -188
  18. pyegeria/data_designer_omvs.py +217 -9
  19. pyegeria/governance_officer_omvs.py +2349 -0
  20. pyegeria/output_formatter.py +24 -12
  21. pyegeria/solution_architect_omvs.py +4219 -1084
  22. pyegeria/utils.py +15 -2
  23. {pyegeria-5.3.10.dist-info → pyegeria-5.4.0.dev2.dist-info}/METADATA +2 -1
  24. {pyegeria-5.3.10.dist-info → pyegeria-5.4.0.dev2.dist-info}/RECORD +27 -62
  25. {pyegeria-5.3.10.dist-info → pyegeria-5.4.0.dev2.dist-info}/entry_points.txt +3 -0
  26. commands/cat/.DS_Store +0 -0
  27. md_processing/dr_egeria_inbox/archive/dr_egeria_intro.md +0 -254
  28. md_processing/dr_egeria_inbox/archive/dr_egeria_intro_more_terms.md +0 -696
  29. md_processing/dr_egeria_inbox/archive/dr_egeria_intro_part1.md +0 -254
  30. md_processing/dr_egeria_inbox/archive/dr_egeria_intro_part2.md +0 -298
  31. md_processing/dr_egeria_inbox/archive/dr_egeria_intro_part3.md +0 -608
  32. md_processing/dr_egeria_inbox/archive/dr_egeria_intro_part4.md +0 -94
  33. md_processing/dr_egeria_inbox/archive/freddie_intro.md +0 -284
  34. md_processing/dr_egeria_inbox/archive/freddie_intro_orig.md +0 -275
  35. md_processing/dr_egeria_inbox/archive/test-term.md +0 -110
  36. md_processing/dr_egeria_inbox/cat_test.md +0 -100
  37. md_processing/dr_egeria_inbox/data_field.md +0 -54
  38. md_processing/dr_egeria_inbox/data_spec.md +0 -77
  39. md_processing/dr_egeria_inbox/data_spec_test.md +0 -2406
  40. md_processing/dr_egeria_inbox/data_test.md +0 -86
  41. md_processing/dr_egeria_inbox/dr_egeria_intro_categories.md +0 -168
  42. md_processing/dr_egeria_inbox/dr_egeria_intro_part1.md +0 -280
  43. md_processing/dr_egeria_inbox/dr_egeria_intro_part2.md +0 -313
  44. md_processing/dr_egeria_inbox/dr_egeria_intro_part3.md +0 -1073
  45. md_processing/dr_egeria_inbox/dr_egeria_isc1.md +0 -44
  46. md_processing/dr_egeria_inbox/glossary_test1.md +0 -324
  47. md_processing/dr_egeria_inbox/rel.md +0 -8
  48. md_processing/dr_egeria_inbox/sb.md +0 -119
  49. md_processing/dr_egeria_inbox/search_test.md +0 -39
  50. md_processing/dr_egeria_inbox/solution-components.md +0 -154
  51. md_processing/dr_egeria_inbox/solution_blueprints.md +0 -118
  52. md_processing/dr_egeria_inbox/synonym_test.md +0 -42
  53. md_processing/dr_egeria_inbox/t1.md +0 -0
  54. md_processing/dr_egeria_inbox/t2.md +0 -268
  55. md_processing/dr_egeria_outbox/processed-2025-05-15 19:52-data_test.md +0 -94
  56. md_processing/dr_egeria_outbox/processed-2025-05-16 07:39-data_test.md +0 -88
  57. md_processing/dr_egeria_outbox/processed-2025-05-17 16:01-data_field.md +0 -56
  58. md_processing/dr_egeria_outbox/processed-2025-05-18 15:51-data_test.md +0 -103
  59. md_processing/dr_egeria_outbox/processed-2025-05-18 16:47-data_test.md +0 -94
  60. md_processing/dr_egeria_outbox/processed-2025-05-19 07:14-data_test.md +0 -96
  61. md_processing/dr_egeria_outbox/processed-2025-05-19 07:20-data_test.md +0 -100
  62. md_processing/dr_egeria_outbox/processed-2025-05-19 07:22-data_test.md +0 -88
  63. md_processing/dr_egeria_outbox/processed-2025-05-19 09:26-data_test.md +0 -91
  64. md_processing/dr_egeria_outbox/processed-2025-05-19 10:27-data_test.md +0 -91
  65. md_processing/dr_egeria_outbox/processed-2025-05-19 14:04-data_test.md +0 -91
  66. md_processing/md_commands/blueprint_commands.py +0 -303
  67. pyegeria/.DS_Store +0 -0
  68. {pyegeria-5.3.10.dist-info → pyegeria-5.4.0.dev2.dist-info}/LICENSE +0 -0
  69. {pyegeria-5.3.10.dist-info → pyegeria-5.4.0.dev2.dist-info}/WHEEL +0 -0
@@ -1,44 +0,0 @@
1
- # Creating Information Supply Chains
2
-
3
- We can also use Dr.Egeria to create information supply chains. Lets take a look at how.
4
-
5
- ___
6
-
7
- # Create Information Supply Chain
8
-
9
- ## Display Name
10
-
11
- ## Description
12
-
13
- ## Scope
14
-
15
- ## Purposes
16
-
17
-
18
-
19
-
20
- ___
21
-
22
-
23
- # Create Information Supply Chain Segment
24
-
25
- ## Display Name
26
-
27
- ## Description
28
-
29
- ## Scope
30
-
31
- ## Integration Style
32
-
33
- ___
34
-
35
- # Link Supply Chain Segments
36
-
37
- ## Segment 1 Name
38
-
39
- ## Segment 2 Name
40
-
41
- ## Link Label
42
-
43
- ## Link Description
44
-
@@ -1,324 +0,0 @@
1
- # Create Glossary
2
-
3
- ## Glossary Name
4
-
5
- Dr.Egeria Test
6
-
7
- ## Language
8
-
9
- English
10
-
11
- ## Description
12
-
13
- This glossary is for testing Dr.Egeria
14
-
15
- ## Usage
16
-
17
- Use Dr.Egeria commands to create elements.
18
-
19
- ## Version
20
-
21
- 1
22
-
23
- ## Qualified Name
24
-
25
- Glossary::Dr.Egeria Test
26
-
27
- ___
28
-
29
- Create a couple of categories for the glossary.
30
-
31
- ___
32
-
33
- # Create Category
34
-
35
- ## Category Name
36
-
37
- About Cats
38
-
39
- ## Owning Glossary
40
-
41
- Glossary::Dr.Egeria Test
42
-
43
- ## Description
44
-
45
- This category is about cats
46
-
47
- # Create Term
48
-
49
- ## Glossary Name
50
-
51
- Glossary::Dr.Egeria Test
52
-
53
- ## Term Name
54
-
55
- Calico
56
-
57
- ## Category
58
-
59
- About Cats
60
-
61
- ## Summary
62
-
63
- Calico cats
64
-
65
- ## Description
66
-
67
- Calico cats are common
68
-
69
- ## Abbreviation
70
-
71
- ## Examples
72
-
73
- My calico cat is naughty
74
-
75
- ## Usage
76
-
77
- As an adjective.
78
-
79
- ## Version
80
-
81
- 2
82
-
83
- ## Status
84
-
85
- DRAFT
86
-
87
-
88
- ___
89
-
90
- # Create Term
91
-
92
- ## Glossary Name
93
-
94
- Glossary::Dr.Egeria Test
95
-
96
- ## Term Name
97
-
98
- Siamese
99
-
100
- ## Summary
101
-
102
- Siamese cats are native from Thailand.
103
-
104
- ## Description
105
-
106
- The Siamese cat is one of the first distinctly recognised breeds of Asian cat. It derives from the Wichianmat landrace.
107
- The Siamese cat is one of several varieties of cats native to Thailand. The original Siamese became one of the most
108
- popular breeds in Europe and North America in the 19th century
109
-
110
- ## Categories
111
-
112
- Category::About Cats
113
-
114
- ## Version
115
-
116
- 3
117
-
118
- ## Status
119
-
120
- DRAFT
121
-
122
- ___
123
-
124
- # Create Term
125
-
126
- ## Glossary Name
127
-
128
- Glossary::Dr.Egeria Test
129
-
130
- ## Glossary Category
131
-
132
- About Cats
133
-
134
- ## Term Name
135
-
136
- Persian
137
-
138
- ## Summary
139
-
140
- A long hair cat
141
-
142
- ## Description
143
-
144
- The Persian cat, also known as the Persian Longhair, is a long-haired breed of cat characterised by a round face and
145
- short muzzle. The first documented ancestors of Persian cats might have been imported into Italy from Khorasan as early
146
- as around 1620, but this has not been proven.
147
-
148
- ## Version
149
-
150
- 4
151
-
152
- ## Status
153
-
154
- DRAFT
155
-
156
- ___
157
-
158
- Now lets update the glossary we are just creating with an updated description.
159
-
160
- ___
161
-
162
- # Update Glossary
163
-
164
- ## Glossary Name
165
-
166
- Dr.Egeria Test
167
-
168
- ## Language
169
-
170
- English
171
-
172
- ## Description
173
-
174
- This glossary is for testing Dr.Egeria
175
-
176
- ## Usage
177
-
178
- Use Dr.Egeria commands to create elements. We'll start by creating categories for cats and dogs.
179
-
180
- ## Version
181
-
182
- 1.1
183
-
184
- ## Qualified Name
185
-
186
- Glossary::Dr.Egeria Test
187
-
188
- ___
189
-
190
- Create and fill out a category for dogs
191
-
192
- ___
193
-
194
- # Create Category
195
-
196
- ## Category Name
197
-
198
- About Dogs
199
-
200
- ## Owning Glossary
201
-
202
- Glossary::Dr.Egeria Test
203
-
204
- ## Description
205
-
206
- This category is about dogs
207
-
208
- # Create Term
209
-
210
- ## Glossary Name
211
-
212
- Glossary::Dr.Egeria Test
213
- ## Categories
214
- About Dogs
215
- ## Term Name
216
-
217
- Labrador Retriever
218
-
219
- ## Summary
220
-
221
- Labs are perhaps the most popular dog in the US.
222
-
223
- ## Description
224
-
225
- The Labrador Retriever or simply Labrador is a British breed of retriever gun dog. It was developed in the United
226
- Kingdom from St. John's water dogs imported from the colony of Newfoundland (now a province of Canada), and was named
227
- after the Labrador region of that colony. It is among the most commonly kept dogs in several countries, particularly in
228
- the Western world.
229
-
230
- The Labrador is friendly, energetic, and playful.
231
- It was bred as a sporting and hunting dog but is widely kept as a companion dog. It may also be trained as a guide or
232
- assistance dog, or for rescue or therapy work.
233
-
234
- ## Abbreviation
235
-
236
- Labs
237
-
238
- ## Examples
239
-
240
- Leia was a mixed breed Lab
241
-
242
- ## Usage
243
-
244
- A kind of dog
245
-
246
- ## Version
247
-
248
- 2
249
-
250
- ## Status
251
-
252
- DRAFT
253
-
254
-
255
- ___
256
-
257
- # Create Term
258
-
259
- ## Glossary Name
260
-
261
- Glossary::Dr.Egeria Test
262
-
263
- ## Term Name
264
-
265
- Golden Retriever
266
- ## Glossary Category
267
- Category::About Dogs
268
- ## Summary
269
-
270
- Golden Retrievers are very popular dogs.
271
-
272
- ## Description
273
-
274
- The Golden Retriever is a Scottish breed of retriever dog of medium size. It is characterised by a gentle and
275
- affectionate nature and a striking golden coat. It is a working dog, and registration is subject to successful
276
- completion of a working trial.[2] It is commonly kept as a pet and is among the most frequently registered breeds in
277
- several Western countries; some may compete in dog shows or obedience trials, or work as a guide dog.
278
-
279
- The Golden Retriever was bred by Sir Dudley Marjoribanks at his Scottish estate Guisachan in the late nineteenth
280
- century. He cross-bred Flat-coated Retrievers with Tweed Water Spaniels, with some further infusions of Red Setter,
281
- Labrador Retriever and Bloodhound. It was recognised by the Kennel Club in 1913, and during the interwar period spread
282
- to many parts of the world.
283
-
284
- ## Version
285
-
286
- 3
287
-
288
- ## Status
289
-
290
- DRAFT
291
-
292
- ___
293
-
294
- # Create Term
295
-
296
- ## Glossary Name
297
-
298
- Glossary::Dr.Egeria Test
299
-
300
- ## Term Name
301
-
302
- Terrier
303
-
304
- ## Summary
305
-
306
- A vermin hunter
307
-
308
- ## Description
309
-
310
- Terrier (from Latin terra, 'earth') is a type of dog originally bred to hunt vermin. A terrier is a dog of any one of
311
- many breeds or landraces of the terrier type, which are typically small, wiry, game, and fearless. There are five
312
- different groups of terrier, with each group having different shapes and sizes.
313
-
314
- ## Version
315
-
316
- 4
317
-
318
- ## Status
319
-
320
- DRAFT
321
-
322
- ___
323
-
324
-
@@ -1,8 +0,0 @@
1
-
2
- # Create Term-Term Relationship
3
- ## Term 1 Name
4
- T1
5
- ## Term 2 Name
6
- T2
7
- ## Term Relationship
8
- Synonym
@@ -1,119 +0,0 @@
1
- <!-- SPDX-License-Identifier: CC-BY-4.0 -->
2
- <!-- Copyright Contributors to the Egeria project. -->
3
-
4
- # Rules
5
- * If this is a create, and qualfied name is provided, it will be used.
6
- * If this is an update, and qualified name is provided, it is an error if it doesn't match.
7
- * If this is an update and no qualified name provided, will try to use the display name
8
- * If this is an update and qualified name and guid provided, then the qualified name can be changed
9
-
10
-
11
- # Update Solution Blueprint
12
-
13
- ## Display Name
14
-
15
- Clinical Trial Management Solution Blueprint
16
-
17
- ## Description
18
-
19
- A description of how a clinical trial is managed in Coco Pharmaceuticals.
20
-
21
- ## Version Identifier
22
-
23
- V1.2
24
- ## Qualified Name
25
-
26
- SolutionBlueprint:Clinical Trial Management Solution Blueprint:V1.2
27
-
28
- ## <guid>
29
-
30
- ---
31
-
32
- # Update Solution Component
33
-
34
- ## Display Name
35
-
36
- Hospital Processes
37
-
38
- ## Description
39
-
40
- ## Version Identifier
41
-
42
- ## Solution Component Type
43
- String - valid value?
44
- ## Planned Deployed Implementation Type
45
- String - valid value?
46
- ## Solution Blueprints
47
-
48
- Clinical Trial Management Solution Blueprint
49
-
50
- ## Parent Components
51
-
52
- ---
53
-
54
- # Create Solution Component
55
-
56
- ## Display Name
57
-
58
- Lab Processes
59
-
60
- ## Description
61
-
62
- ## Version Identifier
63
-
64
- ## Solution Component Type
65
- String - valid value?
66
- ## Planned Deployed Implementation Type
67
- String - valid value?
68
- ## Solution Blueprints
69
-
70
- SolutionBlueprint:Clinical Trial Management Solution Blueprint:V1.2
71
-
72
- ## Parent Components
73
-
74
- ---
75
-
76
- # Create Solution Role
77
-
78
- ## Name
79
-
80
- ## Identifier
81
- str
82
- ## Description
83
-
84
- ## Scope
85
- str - valid values
86
- ---
87
-
88
- # Create Solution Actor Role
89
-
90
- ## Solution Component
91
-
92
- SolutionComponent:XXX q_name
93
- <required>
94
- ## Actor
95
-
96
- Actor:XXX -q_name
97
- <required>
98
- ## Role
99
- str - valid value
100
- <required>
101
- ## Description
102
-
103
-
104
- ---
105
-
106
- # Create Solution Linking Role
107
-
108
- ## Starting Solution Component
109
- q_name of soln
110
- <required>
111
- ## Wired To Solution Component
112
- q_name of soln
113
- <required>
114
- ## Label
115
- str
116
- <required>
117
- ## Description
118
- str
119
- ## Information Supply Chain Segment GUIDs
@@ -1,39 +0,0 @@
1
-
2
- # List Terms
3
- ## Output Format
4
- DICT
5
-
6
- # List Term Update History
7
-
8
- ## Term Name
9
-
10
- PDR
11
- ## Output Format
12
- DICT
13
-
14
- ___
15
-
16
- # List Term History
17
-
18
- ## Term Name
19
-
20
- PDR
21
-
22
-
23
- ___
24
-
25
- # List Glossary Structure
26
-
27
- ## Glossary
28
-
29
- Egeria-Markdown
30
-
31
- # List Categories
32
-
33
- ## Output Format
34
- LIST
35
-
36
-
37
- # List Glossaries
38
-
39
- ## Search String
@@ -1,154 +0,0 @@
1
- <!-- SPDX-License-Identifier: CC-BY-4.0 -->
2
- <!-- Copyright Contributors to the Egeria project. -->
3
-
4
- # Rules
5
- * If this is a create, and qualfied name is provided, it will be used.
6
- * If this is an update, and qualified name is provided, it is an error if it doesn't match.
7
- * If this is an update and no qualified name provided, will try to use the display name
8
- * If this is an update and qualified name and guid provided, then the qualified name can be changed
9
- => This needs work when the upsert methods are done
10
-
11
- # Create Solution Component
12
-
13
- ## Display Name
14
-
15
- Lab Processes
16
-
17
- ## Description
18
- Test to create component that doesn't exist
19
- ## Version Identifier
20
- 1
21
- ## Solution Component Type
22
- Should succeed
23
- ## Planned Deployed Implementation Type
24
-
25
- ## Solution Blueprints
26
-
27
- SolutionBlueprint:Clinical Trial Management Solution Blueprint:V1.2
28
-
29
- ## Parent Components
30
-
31
- ---
32
-
33
-
34
- # Update Solution Component
35
-
36
- ## Display Name
37
-
38
- Hospital Processes
39
-
40
- ## Description
41
- Test to Update a component that exists
42
- ## Version Identifier
43
- 2
44
- ## Solution Component Type
45
- Should succeed
46
- ## Planned Deployed Implementation Type
47
-
48
- ## Solution Blueprints
49
-
50
- SolutionBlueprint:Clinical Trial Management Solution Blueprint:V1.2
51
-
52
- ## Parent Components
53
-
54
- ---
55
-
56
- ---
57
-
58
-
59
- # Update Solution Component
60
-
61
- ## Display Name
62
-
63
- Dunga Din
64
-
65
- ## Description
66
- Test to Update a component that does not exist
67
- ## Version Identifier
68
- 3
69
- ## Solution Component Type
70
- Should fail
71
- ## Planned Deployed Implementation Type
72
-
73
- ## Solution Blueprints
74
-
75
- SolutionBlueprint:Clinical Trial Management Solution Blueprint:V1.2
76
-
77
- ## Parent Components
78
-
79
- ---
80
-
81
- # Create Solution Component
82
-
83
- ## Display Name
84
-
85
- Create-with-q-name
86
-
87
- ## Description
88
- Test to create a new component that does not exist with own qname
89
- ## Version Identifier
90
- 4
91
- ## Solution Component Type
92
- Should succeed
93
- ## Planned Deployed Implementation Type
94
-
95
- ## Solution Blueprints
96
-
97
- SolutionBlueprint:Clinical Trial Management Solution Blueprint:V1.2
98
-
99
- ## Parent Components
100
- ## Qualified Name
101
- TEST:Component:Create-with-q-name
102
-
103
- ---
104
-
105
- # Update Solution Component
106
-
107
- ## Display Name
108
-
109
- Update-with-existing-q-name-match
110
-
111
- ## Description
112
- Test to update a component that that exists and has a supplied q-name
113
- ## Version Identifier
114
- 5
115
- ## Solution Component Type
116
- Should succeed - but need to do real create to fully test
117
- ## Planned Deployed Implementation Type
118
-
119
- ## Solution Blueprints
120
-
121
- SolutionBlueprint:Clinical Trial Management Solution Blueprint:V1.2
122
-
123
- ## Parent Components
124
-
125
- ## Qualified Name
126
- TEST:Component:Create-with-q-name
127
-
128
- ---
129
-
130
- ---
131
-
132
- # Update Solution Component
133
-
134
- ## Display Name
135
-
136
- Update-with-q-name-mismatch
137
-
138
- ## Description
139
- Test to create a new component that does not exist with own qname
140
- ## Version Identifier
141
- 6
142
- ## Solution Component Type
143
- Should fail - but need real implementation to know
144
- ## Planned Deployed Implementation Type
145
-
146
- ## Solution Blueprints
147
-
148
- SolutionBlueprint:Clinical Trial Management Solution Blueprint:V1.2
149
-
150
- ## Parent Components
151
- TEST:Component:Create-with-q-name
152
- ## Qualified Name
153
- TEST:Component:Create-with-q-name:meow
154
- ---