Requirements for Re-Platforming: Difference between revisions

Created page with "This is an index for content relevant to the U of M IT team in proposing a solution for hosting our database. * 15-20 users on laptops * system of intermittently linked MS Access databases with a fair bit of automation * facilitated interfaces with Shared Health systems (we request and receive data in files that we import as either temporary or permanent data) * Approximately 1.1GB (core) + 200MB (PHI) + (1.2+0.36GB) (Labs) + est 500MB assorted legacy data * CCMDB_D..."
 
m Ttenbergen moved page Requiremens for Re-Platforming to Requirements for Re-Platforming without leaving a redirect: Text replacement - "Requiremens for Re-Platforming" to "Requirements for Re-Platforming"
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
This is an index for content relevant to the U of M IT team in proposing a solution for hosting our database.  
This is an index for content relevant to the U of M IT team in proposing a solution for hosting our database.  


* 15-20 users on laptops
== Repeated failure points we should address before going too far ==
We have had many [[:Category:Failed Re-platforming  | failed attempts at re-platforming]]. The technical change would be tedious but doable, the sticking points have always been around the following, so we should discuss these before planning too much further.
* governance of any implemented system
* data ownership
* support model
* our team's continued ability to change this as needed
 
== Relatively Hard Facts ==
* 15-20 users on laptops, sometimes working from home, sometimes not connected to the network due to lack if [[wifi]]
* About 2-2.5GB of data altogether as stored in various MS Access DBs (size may vary on other platforms)
* Has several highly customized front-ends that facilitates efficient and low-error data entry
** facilitates data entry from a daily dump received from ADT
* Data we need to store is in [[Auto Data Dictionary]]
** it is currently stored in [[CCMDB Data Structure]] - this structure could be stored differently but would cause large changes
* We have (and continuously improve) [[Data Integrity Checks]]
 
== Current Implementation ==
* system of intermittently linked MS Access databases with a fair bit of automation  
* system of intermittently linked MS Access databases with a fair bit of automation  
* facilitated interfaces with Shared Health systems (we request and receive data in files that we import as either temporary or permanent data)
* facilitated interfaces with Shared Health systems (we request and receive data in files that we import as either temporary or permanent data)
* Approximately 1.1GB (core) + 200MB (PHI) + (1.2+0.36GB) (Labs) + est 500MB assorted legacy data
* [[CCMDB_Data_Structure]]
* number of fields not necessarily relevant because of [[Entity–attribute–value model of the L Tmp V2 table]]
* number of fields not necessarily relevant because of [[Entity–attribute–value model of the L Tmp V2 table]]
* [[Auto Data Dictionary]]


Our questions:
== Related articles ==
* How would collectors enter the data, and would we be able to have the same high level of cross checks and fine-tuning of their environment as we do now? (ask us for examples)
{{Related Articles}}
* Who will be allowed to program and implement changes on this system, and what would the timelines be?
 


[[Category:Warehouse]]
[[Category: Re-platforming]]
[[Category:Data Repository]]