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

From CCMDB Wiki
Jump to navigation Jump to search
m link
m Instructions: set date range
Line 15: Line 15:
# 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 directory
# 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 "Import DSM .csv" button  
# click the "Import DSM .csv" button  
# pick the newly received file
# pick the newly received file

Revision as of 18:39, 25 August 2017

Preliminary information, this is not active yet

see Instructions for requesting a batch of data from DSM for counterpart

We receive data from DSM that needs to be imported into our main repository.

Instructions

  1. copy files to local, they are large and won't work well on a share.
  2. copy the newly received batch of data from DSM_Lab_Extract#File_Share to directory
  3. Open DSM_Labs_Consistency_check.accdb
  4. Set the start and end date of the time range for which you requested and received the file you are about to import
  5. click the "Import DSM .csv" button
  6. pick the newly received file
  7. 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.

(once out of testing)

  1. Move Centralized_data.mdb back to master directory
  2. Move DSM_Labs_Consistency_check.accdb back to its master location; it likely contains new group and lab info now.
  3. enter import date in log below

Known issues

need to re-launch program after every few imports import

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

Log

eg copy/paste and fill in the following: 
* ~~~~~ - imported batch