This file contains the list of prompts for the information to be included in the README that will be provided with your data products in the GBT Legacy Archive. Please fill in your answers in the associated README.md file which is in Markdown format.
Last updated: 2024-08-08

# Basic Survey/Project Information
- What is the title of your survey/project? 
- What is the abstract of your survey/project? If survey should match the one listed on [https://greenbankobservatory.org/science/gbt-surveys](https://greenbankobservatory.org/science/gbt-surveys).
- If you have one, what is the associated GBO webpage for your survey/project? 
- If you have one, what is the associated GBO data webpage for your survey/project? 
- What is the name of the PI?
- What receiver(s) did you use?
- What is the frequency range of the project? Please include units (MHz, GHz, etc.). In addition to the full frequency range of the project, if you observed a specific molecule(s), please include the rest frequency and molecule name and transition (e.g., 23694.5 MHz - NH3(1-1)). If you observed many molecules, please list them all. 
- If someone uses the data you provided, what work(s) should they cite? Please provide an ADS link and the bibitem. For the bibitem you can go to ADS -> Export Citation -> AASTeX. 

# Observing Information
- What is/are the associated project code(s) of your survey/project?
- What are the GBT observing sessions associated with the data that you are providing? If there are a large number of sessions, feel free to instead provide a separate file with the observing sessions.
- Are your observations mapping or single-pointing observations?
- What type of observation was used (spectral line, continuum, or pulsar)?
	- If the data is spectral line data which mode was used (total power or frequency switching)?
- (Optional) Is there any information about the technical setup for the observations (number of spectral windows, spectral resolution, polarization) that you would like to provide? For example, you could provide a typical configuration string from your Astrid scripts. 

# Data Information
A description of data products must be provided. This description should outline what the files are, how they were created, and provide a reference to the associated data paper(s). Please include the following information:
	- Which files are considered your main calibrated data products and which are considered ancillary? Many projects have files containing derived data products as well as the main calibrated science ready data products. Please include file names of your main products in your description to be clear as to what is a main product and describe ancillary naming in the section below.
	- All data files will need to follow a standard convention. Please describe the file naming convention and/or directory structure. It may be sufficient to describe only one frequency or transition if the subsequent files follow the same procedure and naming convention. An example is shown below:
		source_sci_freq_cube_xx.fits
		- "source" denotes the observation target or region of the sky.
		- "sci" denotes that this file is a main science product and "anc" denotes other data associated which may include derived data products.
		- "freq" denotes the frequency information in GHz. This can also be replaced by the transition if that naming convention is appropriate.
		- "cube" denotes that this file is a spectral data cube. "Cube" can be replaced with any appropriate descriptor for the data file.
		- "\_xx" denotes the number out of the total number of files with leading zeroes for that specific type of file.
	- Please be provide information about the units of the data products that you are providing (especially if that information is not in the headers). Note that for FITS images the `BUNIT` keyword is required (see https://www.gb.nrao.edu/GbtLegacyArchive/GBT_legacy_archive_file_keyword_requirements.md for more details).
	- Please describe how the data products that you are providing were created. One can simply provide a reference (with a link to this reference - e.g., ADS link) to the data paper(s). If you provide a reference, please detail the relevant section and paragraph numbers so that a user can easily find the relevant information. If there is no reference that provides reduction information, please provide a brief description of the reduction process here.
		- What pipeline/data processing did you use to use to produce your main calibrated data products. For example, did you use the GBT pipeline in your processing? If you used the GBT pipeline please say so and if you did not use the GBT pipeline, please say so and describe your pipeline.
	- If any tables are provided, please provide me a separate README.txt that describes the column names. 
	- What is the total data volume for this project?
		- What is the data volume of all of your main data products?
		- What is the data volume of all of your ancillary data products?
	- Is there any other information that you would like to provide about these data products (e.g., further data reduction notes or general notes)?