Requirements for Re-Platforming: Difference between revisions

Agarland (talk | contribs)
JMojica (talk | contribs)
No edit summary
Line 34: Line 34:
**Allowing our database personnel to transfer data into and out of the database, such as an export to file or import from file, ad hoc (5)
**Allowing our database personnel to transfer data into and out of the database, such as an export to file or import from file, ad hoc (5)
**To the maximum extent possible, maintaining an interface with the data that looks like, and has functionalities of, our current MS ACCESS interface (4)
**To the maximum extent possible, maintaining an interface with the data that looks like, and has functionalities of, our current MS ACCESS interface (4)
*** Has the ability to browse, search, sort, filter, create new variable  and export the data  from the  new platform itself (4)  --[[User:JMojica|JMojica]] 13:35, 27 March 2025 (CDT) 
{{Discuss | I think this can go, it's addressed above. }}
{{Discuss | I think this can go, it's addressed above. }}
**Maintaining the current [[Data Processing]] functionality for the [[data processor]], who often works remotely (5)
**Maintaining the current [[Data Processing]] functionality for the [[data processor]], who often works remotely (5)
Line 39: Line 40:
{{DJ|
{{DJ|
* I don't think you write from SAS, right? [[User:Ttenbergen|Ttenbergen]] 14:33, 17 March 2025 (CDT)
* I don't think you write from SAS, right? [[User:Ttenbergen|Ttenbergen]] 14:33, 17 March 2025 (CDT)
** I export the ACCESS table using SAS and then perform all the analysis by programing  in SAS.  --[[User:JMojica|JMojica]] 13:35, 27 March 2025 (CDT)
* I made this a (3) because the ability to export above would provide a work-around of copying data to local; open to discuss. [[User:Ttenbergen|Ttenbergen]] 14:33, 17 March 2025 (CDT)
* I made this a (3) because the ability to export above would provide a work-around of copying data to local; open to discuss. [[User:Ttenbergen|Ttenbergen]] 14:33, 17 March 2025 (CDT)
}}
}}
Line 59: Line 61:
* Ability for the following two things is necessarily interconnected, but listed separately to allow for some flexibility
* Ability for the following two things is necessarily interconnected, but listed separately to allow for some flexibility
** Ability ''for the CCMDB team'' to update that functionality to data collection and data processing by adding to or updating front end, queries and automation, without gatekeeping
** Ability ''for the CCMDB team'' to update that functionality to data collection and data processing by adding to or updating front end, queries and automation, without gatekeeping
{{Discuss | let's talk about this... is that a 5? It is to me.}}
{{Discuss | let's talk about this... is that a 5? It is to me.  
* Are all our existing queries will have a counterpart in the new platform? e.g. APACHE score and individual element score, Charlson Score, created variables, etc.  --[[User:JMojica|JMojica]] 13:35, 27 March 2025 (CDT)  }}
** Ability ''for the CCMDB team'' to modify the data structure (5)
** Ability ''for the CCMDB team'' to modify the data structure (5)
{{Discuss | let's talk about this... is that a 5? It is to me.}}
{{Discuss | let's talk about this... is that a 5? It is to me.}}