Instructions for importing a batch of DSM Data: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m m |
||
| Line 15: | Line 15: | ||
# click the "Import DSM .csv" button | # click the "Import DSM .csv" button | ||
# pick the newly received file | # pick the newly received file | ||
# follow instructions | # 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 | ||
Revision as of 16:50, 15 October 2015
Preliminary information, this is not active yet
We receive data from DSM that needs to be imported into our main repository.
Instructions
- copy files to local, they are large and won't work well on a share (need batch Template:Discussion).
- make a new local directory
- Put the following into the directory
- copy the newly received batch of data from DSM_Lab_Extract#File_Share to directory
- Open DSM_Labs_Consistency_check.accdb
- click the "Import DSM .csv" button
- pick the newly received file
- 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
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.