Requesting Data



 

 

 

Tips for easy use:

The Data Services Lab provides many services to faculty and students of the University of Oregon including data extraction, scanning, and cd-rom pressing. Since most of our services are time consuming, there are a few things that lab users can do to reduce the amount of time it takes us to get your data to you. Here are a few steps that you can take to ensure quick, efficient service:


1. Know what data you will need and possible sources for getting it.

Before we can extract your data, we need specific guildelines as to what you are looking for. You can help the process by investigating data sets that you would like to use. If possible, take a look at the codebook (you may be able to view it on the web , or if it is on a cd in DSL's CD collection, view it in the lab). If you are not sure where to look, try the ICPSR or send a note to Adam Lake for some suggestions.

Once you have the codebook for the data you would like to use, pick out your variables. Keep in mind that the more variables you use, the larger your final data set will be. This may slow down any data processing that you want to do to the final file. It is better to have too many than too few, but beware of how much time it could cost you in the end.

 

2. Please plan ahead!!It is vital that you allow enough time for the work to be completed! You need to leave plenty of time for the data extraction process. DSL offers its services to the entire university, so we are not always able to immediately begin work on new projects. We complete work as it comes in, so the amount of time it takes varies according to the current workload.

 

Send your request to DSL via email and make an appointment time to meet with us. By sending your request to us early, we can make sure that we understand what you are asking for and estimate how long it will take to complete the job. It is important that we understand what you are asking for. Setting an appointment time will allow us to discuss your request without interrupting other work (or being interrupted!). Tell us how you would like the final file format to be. If you only use accounts on specific servers, we may need to make adjustments (For instance, Darkwing is a UNIX server while Oregon is a VMS server. Programs such as SAS need different header infor mation in the files to operate correctly.)