feat: formats plan
This commit is contained in:
		
							
								
								
									
										26
									
								
								docs/formats.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										26
									
								
								docs/formats.md
									
									
									
									
									
										Normal file
									
								
							| @@ -0,0 +1,26 @@ | ||||
| --- | ||||
| layout: article | ||||
| title: API | ||||
| description: Viewing and Modifying SAS Formats in Data Controller | ||||
| --- | ||||
|  | ||||
| !!! warning | ||||
|     Work in Progress! | ||||
|  | ||||
| # Formats | ||||
|  | ||||
| SAS Formats are stored in Catalogs, and are used for in-memory lookup operations.  Some formats are available by default, others (custom formats) are maintained seperately. | ||||
|  | ||||
| Using Data Controller to manage formats means that it will no longer be necessary to maintain 'CNTLIN' datasets seperately to the main catalog. | ||||
|  | ||||
| Formats will be presented with a new icon (`bolt`), in the same library as other tables (in both the VIEW and EDIT screens): | ||||
|  | ||||
|  | ||||
|  | ||||
| Viewing a format catalog will always mean that the entire catalog is exported and displayed. | ||||
|  | ||||
| Filters will be applied after the export.  DDL / excel exports will apply to the export. | ||||
|  | ||||
| The MPE_TABLES for formats will need to be configured with a new LOADTYPE (FMTCATALOG) and specific CLOSE_VARS and BUSKEY values. | ||||
|  | ||||
| Edits to formats will follow the regular approval process, with changes logged in MPE_AUDIT. | ||||
| @@ -20,12 +20,17 @@ If you would like to see a new Feature added to Data Controller, then let's have | ||||
|  | ||||
| Where features are requested, whether there is budget or not, we will describe the work below and provide estimates. | ||||
|  | ||||
| There are currently four features requested: | ||||
| There are currently three new features in development: | ||||
|  | ||||
| * Ability to restore previous versions (estimate - 6 to 9 days).  Sponsor needed. | ||||
| * Ability to import complex excel data using Excel Maps (10.5 days) | ||||
| * Ability to make automated submissions using an API (6 days) | ||||
| * Include change tracking information in a transaction table | ||||
| * Ability to [view & edit formats](/formats.md) | ||||
| * Ability to restore previous versions | ||||
|  | ||||
| A further two are requested: | ||||
|  | ||||
| * Ability to import complex excel data using Excel Maps (10.5 days) | ||||
| * Ability to make automated submissions using an API | ||||
|  | ||||
|  | ||||
| ### Complex Excel Uploads | ||||
|  | ||||
| @@ -133,8 +138,8 @@ create table dc.mpe_audit_history( | ||||
| ``` | ||||
|  | ||||
|  | ||||
| - [ ] tidy up & define bitemporal outputs to include "base" records | ||||
| - [ ] update postdata service to include new outputs | ||||
| - [x] tidy up & define bitemporal outputs to include "base" records | ||||
| - [x] update postdata service to include new outputs | ||||
| - [ ] create macro to populate new audit tables if flag is set | ||||
|  | ||||
|  | ||||
|   | ||||
		Reference in New Issue
	
	Block a user