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

From CCMDB Wiki
Jump to navigation Jump to search
m (m)
Line 17: Line 17:
# 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.  
# 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''') Move [[Centralized_data.mdb]] back to master directory
('''once out of testing''')  
# Move [[Centralized_data.mdb]] back to master directory
# delete the working file? {{discussion}}


== Known issues ==
== Known issues ==

Revision as of 17:51, 2015 October 15

Preliminary information, this is not active yet

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 (need batch Template:Discussion).
  2. copy the newly received batch of data from DSM_Lab_Extract#File_Share to directory
  3. Open DSM_Labs_Consistency_check.accdb
  4. click the "Import DSM .csv" button
  5. pick the newly received file
  6. 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. delete the working file? Template:Discussion

Known issues

need to re-launch program for second import

If something goes wrong during one import enough garbage is left in the file that a second import won't work unless the program is closed and re-openend, which triggers a compact-repair.