CCMDB Wiki

Instructions for importing a batch of DSM Data: Difference between revisions

← Older editNewer edit →
m →Instructions: header
mNo edit summary
Line 6: Line 6:


== Instructions ==
== Instructions ==
=== Prep ===
# copy files to local, they are large and won't work well on a share.
# copy files to local, they are large and won't work well on a share.
#* make a new local directory
#* make a new local directory
Line 11: Line 12:
#** [[Centralized_data.mdb]]  
#** [[Centralized_data.mdb]]  
#** [[DSM_Labs_Consistency_check.accdb]]
#** [[DSM_Labs_Consistency_check.accdb]]
#** [[DSM Labs data.accdb]]
#** not needed - [[PHI.mdb]] is not needed during import because it matches by D_ID
#** not needed - [[PHI.mdb]] is not needed during import because it matches by D_ID
# copy the newly received batch of data from [[DSM_Lab_Extract#File_Share]] to directory
# copy the newly received batch of data from [[DSM_Lab_Extract#File_Share]] to a '''different local directory that contains '''only those files'''
# '''add the same header''' as in the first file to all other files
 
=== Check for new labs ===
# Open [[DSM_Labs_Consistency_check.accdb]]  
# Open [[DSM_Labs_Consistency_check.accdb]]  
# Set the start and end date of the time range for which you requested and received the file you are about to import
# Click the "Check DSM .csv for new labs " button
# click the "Import DSM .csv" button  
# pick the directory with the new data files
# pick the newly received file
# wait for the check to complete, about half an hour
# follow instructions; the import takes about 5 minutes to run now during which the program will not respond to further interaction. There will be a progress indicator at the bottom right of the window, as long as it is going the program is still working. When the program is done it will display a message box to say so, and indicate how long it took.  
# if the program tells you there are new labs, review them and ask Trish or Allan if any of them should be considered as part of our counts
#* If so talk to Tina, we can document that process when it next happens. It involves editing table s_mapping_labs or s_group to accommodate the new data.


('''once out of testing''')
=== actual data import ===
# Move [[Centralized_data.mdb]] back to master directory
If the above listed no new labs, or the new labs were resolved, click the "Import DSM .csv" button and follow essentially the same steps as above to import the actual data.
# Move [[DSM_Labs_Consistency_check.accdb]] back to its master location; '''it likely contains new group and lab info now'''.
 
=== Cleanup ===
# Move files back to their master directories
#** [[DSM_Labs_Consistency_check.accdb]] - only need to move if new labs were found
#** [[DSM Labs data.accdb]]
# enter import date in log below
# enter import date in log below


== Integrity checks after import ==
== Integrity checks after import ==
Tina has a task for additional checks that might be set up.  
Please note here if any are needed.  


=== D_IDs in CFE for which no DSM labs exist ===
=== D_IDs in CFE for which no DSM labs exist ===
Line 40: Line 48:
=== Duplicate RequestNo ===
=== Duplicate RequestNo ===
Should never happen due to how import works, but can check anyway.
Should never happen due to how import works, but can check anyway.


== Known issues ==
== Known issues ==
=== need to re-launch program after every few imports import ===
None at this time
If something goes wrong during one import enough garbage is left in the file that subsequent imports won't work unless the program is closed and re-openend, which triggers a compact-repair.


== How does it work ==
== How does it work ==
Line 53: Line 59:
  <nowiki>* ~~~~~ - imported batch</nowiki>
  <nowiki>* ~~~~~ - imported batch</nowiki>


* 17:47, 2018 April 9 (CDT) - imported batch 2016-10-17 and 2018-01-25


[[Category: DSM Labs Extract]]
[[Category: DSM Labs Extract]]
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Instructions_for_importing_a_batch_of_DSM_Data"