Instructions for importing a batch of DSM Data: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m →Instructions: cleanup |
Ttenbergen (talk | contribs) |
||
Line 25: | Line 25: | ||
== Known issues == | == Known issues == | ||
=== need to re-launch program | === 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 | 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. | ||
== Log == | == Log == |
Revision as of 18:19, 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
- copy files to local, they are large and won't work well on a share.
- 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
- Move DSM_Labs_Consistency_check.accdb back to its master location; it likely contains new group and lab info now.
- 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.
Log
eg copy/paste and fill in the following: * ~~~~~ - imported batch