pyegeria 5.4.0.dev3__py3-none-any.whl → 5.4.0.dev6__py3-none-any.whl

md_processing/dr_egeria_inbox/data_test.md

@@ -1,179 +0,0 @@
-
-
-
-
-
-___
-
-Data Specification for the Teddy Bear Drop Foot Clinical Trial
-___
-
-# Create Data Specification
-
-## Data Specification
-
-Data Specification for the Teddy Bear Drop Foot Clinical Trial
-
-##  Description
-
-Principle data requirements for Teddy Bear Drop Foot clinical trial.
-___
-
-#  Create Data Specification
-
-## Data Specification
-Data Specification for the Werewolf Transformation Clinical Trial
-
-##  Description
-
-Principle data requirements for Werewolf Transformation clinical trial.
-
-#  Create Data Specification
-
-## Data Specification
-Test Spec
-
-##  Description
-
-for testing purposes only.
-
-
-
-#  Create Data Dictionary
-## Name
-Clinical Trial Data Dictionary
-
-## Description
-A data dictionary for clinical trial data elements.
-
-
-#  Create Data Dictionary
-## Name
-Pharma Data Dictionary
-
-## Description
-A data dictionary of elements relevant to the Pharma communities.
-
-
-___
-
-
-___
-
-TBDF-Incoming Weekly Measurement Data
-___
-
-#  Create Data Structure
-
-## Data Structure
-
-TBDF-Incoming Weekly Measurement Data
-
-## Description
-This describes the weekly measurement data for each patient in the Teddy Bear drop foot clinical trial
-
-## In Data Specification
-Data Specification for the Teddy Bear Drop Foot Clinical Trial, Test Spec
-
-
-## Qualified Name
-
-
-___
-
-WWT-Incoming Weekly Measurement Data
-
-#  Create Data Structure
-
-## Qualified Name
-DataStruct::WWT-Incoming Weekly Measurement Data
-
-## GUID
-
-
-## Data Structure
-
-WWT-Incoming Weekly Measurement Data
-
-
-##  Description
-A collection of data fields that form a data structure.
-Meow
-
-##  In Data Specification
-
-Test Spec
-Data Specification for the Teddy Bear Drop Foot Clinical Trial
-
-##  Qualified Name
-___
-
-
-
-# foo Create Data Field
-## Name
-PatientId
-## Description
-Unique identifier of the patient
-## Data Type
-String
-## Position
-0
-## Min Cardinality
-1
-## Max Cardinality
-1
-## In Data Structure
-> initially a data field must have at least one place it is part of and can update
-
-TBDF-Incoming Weekly Measurement Data
-
-## Data Class 
-## Glossary Term
-GlossaryTerm::ClinicalTrialTerminology::PatientId
-## Namespace
-> forms part of qualified name
-## Version
-
-## In Data Dictionary
-Clinical Trial Data Dictionary
-
-## Qualified Name
-
-DataField::PatientId
-
-___
-
-#  foo Create Data Field
-## Name
-HospitalId
-## Description
-Unique identifier for a hospital
-## Data Type
-String
-## Position
-0
-## Min Cardinality
-1
-## Max Cardinality
-1
-## Parent Data Field
-DataField::PatientId
-## In Data Structure
-> initially a data field must have at least one place it is part of and can update
-
-TBDF-Incoming Weekly Measurement Data
-
-## Data Class 
-## Glossary Term
-GlossaryTerm::ClinicalTrialTerminology::PatientId
-## Namespace
-> forms part of qualified name
-## Version
-
-## In Data Dictionary
-Clinical Trial Data Dictionary
-
-## Qualified Name
-
-DataField::HospitalId

md_processing/dr_egeria_inbox/data_test2.md

@@ -1,376 +0,0 @@
-# Create Term
-## In Glossary
-Coco Pharmaceuticals Clinical Trial Terminology
-## Term Name
-Hospital Identifier
-## Description
-Identifies each hospital uniquely. Used within the PatientId field.
-
-___
-
-#  Create Data Dictionary
-## Name
-Clinical Trial Data Dictionary
-
-## Description
-A data dictionary for clinical trial data elements.
-
-
-#  Create Data Dictionary
-## Name
-Pharma Data Dictionary
-
-## Description
-A data dictionary of elements relevant to the Pharma communities.
-
-
-___
-
-# Create Data Spec
-
-## Data Specification 
-
-Data Specification for the Teddy Bear Drop Foot Clinical Trial
-
-## Description
-Principle data requirements for Teddy Bear Drop Foot Clinical Trial. Meow
-
-## Qualified Name
-DataSpec::Data Specification for the Teddy Bear Drop Foot Clinical Trial
-
-## Classifications
-
-## Guid
-
-
-___
-
-
-# Create Data Specification
-
-## Data Specification Name 
-
-Test Spec2
-
-## Description
-A test spec - Meow
-
-## Qualified Name
-
-## Classifications
-
-## Guid
-
-## Additional Properties
-{
-    "a prop" : "meow",
-    "another" : "woof"
-}
-___
-
-# Create Data Dictionary
-
-## Dictionary Name 
-
-dw
-
-## Description
-A data dictionary for dan..
-## Qualified Name
-DataDict::dw
-
-## Classifications
-
-## GUID
-
-
-___
-
-
-# Create Data Structure
-
-## Data Structure Name 
-
-TBDF-Incoming Weekly Measurement Data
-
-## Description
-This describes the weekly measurement data for each patient for the Teddy Bear drop foot clinical trial. 
-
-## Qualified Name
-DataStruct::TBDF-Incoming Weekly Measurement Data
-
-## Namespace
-
-## In Data Specification
-Data Specification for the Teddy Bear Drop Foot Clinical Trial, Test Spec2
-
-## Version Identifier
-
-
-## Guid
-
-
-___
-
-# Create Data Structure
-
-## Data Structure Name 
-
-WWT-Incoming Weekly Measurement Data
-
-## Description
-A collection of data fields that form a data structure.
-
-## Qualified Name
-DataStruct::WWT-Incoming Weekly Measurement Data
-
-## In Data Specification
-Test Spec2
-
-## Namespace
-
-
-## Version Identifier
-
-
-## GUID
-
-
-
-___
-
-# Create Data Field
-
-## Data Field Name 
-
-PatientId
-
-## Description
-Unique identifier of the patient
-
-## Qualified Name
-DataField::PatientId
-
-
-## Data Type
-
-String
-
-## Guid
-
-## Data Class
-
-## In Data Dictionary
-DataDict::Clinical Trial Data Dictionary, Pharma Data Dictionary
-
-## In Data Structure
-TBDF-Incoming Weekly Measurement Data
-DataStruct::WWT-Incoming Weekly Measurement Data
-
-## Glossary Term
-GlossaryTerm::ClinicalTrialTerminology::PatientId
-___
-
-
-
-# Create Data Field
-
-## Data Field Name
-
-HospitalId
-
-## Description
-Unique identifier for a hospital. Used in forming PatientId.
-
-## Qualified Name
-DataField::HospitalId
-
-## Data Type
-String
-
-## In Data Dictionary
-DataDict::Clinical Trial Data Dictionary
-
-## In Data Structure
-
-DataStruct::TBDF-Incoming Weekly Measurement Data
-DataStruct::WWT-Incoming Weekly Measurement Data
-
-## Position
-1
-
-## Min Cardinality
-0
-
-## Max Cardinality
-1
-
-## Glossary Term
-Term::Hospital Identifier
-
-## Parent Data Field
-DataField::PatientId
-
-## Journal Entry
-Just creating this term
-
-___
-
-# Create Data Field
-
-## Data Field Name 
-
-PatientSN
-
-## Description
-Unique identifier of the patient within a hospital.
-
-## Qualified Name
-DataField::PatientSN
-
-
-## Data Type
-
-String
-## Position
-2
-
-## Min Cardinality
-0
-
-## Max Cardinality
-1
-
-## In Data Dictionary
-DataDict::Clinical Trial Data Dictionary
-
-## In Data Structure
-DataStruct::TBDF-Incoming Weekly Measurement Data
-DataStruct::WWT-Incoming Weekly Measurement Data
-
-## Parent Data Field
-DataField::PatientId
-
-## Journal Entry
-Just creating this term
-
-___
-
-# foo Create Data Class
-
-## Data Class Name 
-
-ISO-Date
-
-## Description
-ISO 8601 standard date. A date of the form YYYY-MM-DD
-
-## Qualified Name
-DataClass::ISO-Date
-
-## Data Type
-Date
-## Position
-0
-
-## Min Cardinality
-0
-
-## Max Cardinality
-1
-
-## In Data Dictionary
-DataDict::Clinical Trial Data Dictionary
-
-
-## Containing Data Class
-
-## Specializes Data Class
-
-## Journal Entry
-Just creating this date
-
-
-___
-
-
-# Update Data Field
-
-## Data Field Name 
-
-Date
-
-## Description
-A date of the form YYYY-MM-DD
-
-## Qualified Name
-DataField::Date
-
-
-## Data Type
-Date
-
-## Position
-0
-
-## Min Cardinality
-0
-
-## Max Cardinality
-1
-
-## In Data Dictionary
-DataDict::Clinical Trial Data Dictionary
-
-## In Data Structure
-TBDF-Incoming Weekly Measurement Data
-DataStruct::WWT-Incoming Weekly Measurement Data
-
-## Parent Data Field
-
-## Data Class
-DataClass::ISO-Date
-
-## Journal Entry
-Just creating this date
-
-
-___
-
-
-
-# foo Create Data Class
-
-## Data Class Name 
-
-Address
-
-## Description
-Address Class
-
-## Qualified Name
-
-
-
-## Data Type
-
-String
-## Position
-0
-
-## Min Cardinality
-0
-
-## Max Cardinality
-1
-
-## In Data Dictionary
-DataDict::Clinical Trial Data Dictionary
-
-
-## Containing Data Class
-
-## Specializes Data Class
-
-## Journal Entry
-Just creating this date

md_processing/dr_egeria_inbox/dr_egeria_intro_categories.md

@@ -1,168 +0,0 @@
-# Demonstrating updates and additions  
-      
-This document was derived from the processing of the file dr_egeria_intro.md; All of the Dr.Egeria statements have been 
-preserved (including the generated attributes such as the unique GUIDs) and the explanatory text has been replaced.
-
-In this document we will add glossary categories, update existing terms to categorize them, and add some new terms that
-further explain dr.egeria.  This document is being written off-line (actually on a plane) - demonstrating one of the 
-intriguing features of dr.egeria - because its just text, it can be edited anywhere and anytime that there is a text 
-editor. Dr.Egeria files can be emailed, sent via text message, slack or maintained in a `git` repository. 
-It's just text with markdown annotations.
-
-Ok, let's get started. First, we have the `Update Glossary` command below. There is nothing new we need to add at this
-point so we can just leave it as-is. When this document is processed it will apply updates but if there are none, 
-It doesn't matter.
-
-      
-___
-
-Ok, now let's create a couple of glossary categories. They will be:
-
-* **Writing Dr.Egeria Markdown** - where we describe elements of the Dr.Egeria language as terms within the category.
-* **Processing Dr.Egeria Markdown** - where we describe the commands for processing Dr.Egeria.
- 
-
-Glossary categories have the following attributes:
-
-
-| Attribute Name  | Input Required? | Read Only | Generated/Default? | Unique? | Notes                                                                                                    |
-|:----------------|:----------------|-----------|:-------------------|:--------|:---------------------------------------------------------------------------------------------------------|
-| Category Name   | Yes             | No        | No                 | No      | A display name (informal name).                                                                          |
-| Owning Glossary | Yes             | No        | No                 | Yes     | This is the qualified name of the glossary that owns this category.                                      |
-| Parent Category | No              | No        | No                 | No      | Indicate parent category, if exists.                                                                     |
-| Description     | No              | No        | No                 | No      | A textual description of this category                                                                   |
-| Member Terms    | No              | No        | No                 | No      | A list of terms that are members of this category                                                        |
-| Qualified Name  | No              | No        | Yes                | Yes     | The qualified name can either be provided by the user or generated. If generated, a pattern is followed. |
-| GUID            | No              | Yes       | Yes                | Yes     | GUIDs are always generated by Egeria. They are meant for automation, not people.                         |
-| Table           | No              | Yes       | Yes                | No      | Under development                                                                                        |
-| Graph           | No              | Yes       | Yes                | No      | Under Development                                                                                        |
-Qualified Names can either be user specified or generated. If generated the following the form:
-`{local-qualifier}:{type}:{display name}`
-
-* Local-Qualifier is an optional string that can be useful to both disambiguate similar names and to add some local context. Local qualifiers could be set to organization names, functions, business context, etc. The settings for a local qualifier is set either by setting the environment variable `EGERIA_LOCAL_QUALIFIER` or by passing in a parameter when executing one of the Dr.Egeria enabled commands. This could also be set for a team by an Egeria administrator.
-
-___
-
-# Create Category  
-  
-## Category Name  
-  
-Writing Dr.Egeria Markdown  
-  
-## Owning Glossary  
-  
-Glossary::Egeria-Markdown  
-
-## Parent Category
-
-  
-## Description  
-  
-These terms describe the elements of the Dr.Egeria Markdown language and how to use them.   
-  
-## Member Terms
-
-## <Qualified Name>  
-  
-## <GUID>  
-
-
-___
-
-# Create Category  
-  
-## Category Name  
-  
-Dr.Egeria Actions
-  
-## Owning Glossary  
-  
-Glossary::Egeria-Markdown  
-
-## Parent Category
-
-Writing Dr.Egeria Markdown
-
-## Description  
-  
-The actions that Dr. Egeria can process.
-  
-  
-## <Qualified Name>  
-  
-## <GUID>  
-
-___
-
-# Create Category  
-  
-## Category Name  
-  
-Command Attributes
-  
-## Owning Glossary  
-  
-Glossary::Egeria-Markdown  
-
-## Parent Category
-Writing Dr. Egeria Markdown
-## Description  
-  
-Common attributes of commands
-   
-___
-
-# Create Category  
-  
-## Category Name  
-  
-Dr.Egeria Verbs
-  
-## Owning Glossary  
-  
-Glossary::Egeria-Markdown  
-  
-## Description  
-
-Kinds of actions Dr.Egeria can take.
-
-
-## Parent Category
-Writing Dr.Egeria Markdown
-
-## Child Category
-  
-Dr.Egeria Actions
-
-___
-
-# Create Category  
-  
-## Category Name  
-  
-Processing Dr.Egeria Markdown  
-  
-## Owning Glossary  
-  
-Glossary::Egeria-Markdown  
-
-## Parent Category
-  
-## Description  
-  
-These terms describe commands to process Dr.Egeria Markdown.  
-
-## Terms
-
-Command, Source, Directive, Display Validate, Process
-   
-## <Qualified Name>  
-  
-## <GUID>  
-  
-___  
-  
-# List Categories
-
-  
-