```

• 1. What does this package do?
     An interface to the web service methods provided by the
     United States Department of Agriculture (USDA). The
     Agricultural Research Service (ARS) provides a large
     set of databases. The current version of the package
     holds interfaces to the Systematic Botany and Mycology
     Laboratory (SMML), which consists of four databases:
     Fungus-Host Distributions, Specimens, Literature and
     the Nomenclature database. It provides functions for
     querying these databases. The main function is
     \code{associations}, which allows searching for fungus-
     host combinations.
• 1. Paste the full DESCRIPTION file inside a code block (bounded by ``` on either end).

Package: rusda
Type: Package
Title: Interface to USDA databases
Version: 1.0
Date: 2015-06-25
Author: Franz-Sebastian Krah
Maintainer: Franz-Sebastian Krah <f.krah@mailbox.org>
Imports: XML, httr, plyr, foreach, stringr
Description: An interface to the web service methods 
provided by the United States Department of Agriculture 
(USDA). The Agricultural Research Service (ARS) 
provides a large set of databases. The current version 
of the package holds interfaces to the Systematic 
Botany and Mycology Laboratory (SMML), which consists 
of four databases: Fungus-Host Distributions, 
Specimens, Literature and the Nomenclature database. It 
provides functions for querying these databases. The 
main function is \code{associations}, which allows 
searching for fungus-host combinations. 
License: GPL (>= 2)
URL: http://www.usda.gov/wps/portal/usda/usdahome, 
http://nt.ars-grin.gov/fungaldatabases/index.cfm

• 3. URL for the package (the development repository, not a stylized html page)
     https://github.com/FranzKrah/rusda
• 4. What data source(s) does it work with (if applicable)?
     species vector (class: character)defined in R
• 5. Who is the target audience?
     Botanists; Mycologists; Plant pathologists; Plant protection; People interested in fungus-host interactions or associations;
• 6. Are there other R packages that accomplish the same thing? If so, what is different about yours?
     No.
• 7. Check the box next to each policy below, confirming that you agree. These are mandatory.
  • This package does not violate the Terms of Service of any service it interacts with.
  • The repository has continuous integration with Travis and/or another service
  • The package contains a vignette
  • The package contains a reasonably complete readme with devtools install instructions
  • The package contains unit tests
  • The package only exports functions to the NAMESPACE that are intended for end users
• 1. Do you agree to follow the rOpenSci packaging guidelines? These aren't mandatory, but we strongly suggest you follow them. If you disagree with anything, please explain.
  • Are there any package dependencies not on CRAN?
  • Do you intend for this package to go on CRAN?
    Yes.
  • Does the package have a CRAN accepted license? No. First rOpenSci
  • Did devtools::check() produce any errors or warnings? If so paste them below.
    Updating rusda documentation
    Loading rusda
    First time using roxygen2 4.0. Upgrading automatically...
    '/Library/Frameworks/R.framework/Resources/bin/R' --no-site-file --no-environ --no-save --no-restore CMD
    build '/Users/test/Documents/R/pkgs/rusda' --no-resave-data --no-manual
• checking for file ‘/Users/test/Documents/R/pkgs/rusda/DESCRIPTION’ ... OK
• preparing ‘rusda’:
• checking DESCRIPTION meta-information ... OK
• checking for LF line-endings in source and make files
• checking for empty or unneeded directories
• building ‘rusda_1.0.tar.gz’

'/Library/Frameworks/R.framework/Resources/bin/R' --no-site-file --no-environ --no-save --no-restore CMD
check '/var/folders/js/s5k7qtzd1kz2pt9t2p11z7600000gn/T//RtmpopOjFp/rusda_1.0.tar.gz' --timings

• using log directory ‘/private/var/folders/js/s5k7qtzd1kz2pt9t2p11z7600000gn/T/RtmpopOjFp/rusda.Rcheck’
• using R version 3.2.0 (2015-04-16)
• using platform: x86_64-apple-darwin13.4.0 (64-bit)
• using session charset: UTF-8
• checking for file ‘rusda/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘rusda’ version ‘1.0’
• checking package namespace information ... OK
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... OK
• checking for executable files ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking whether package ‘rusda’ can be installed ... OK
• checking installed package size ... OK
• checking package directory ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... NOTE
  Non-standard files/directories found at top level:
  ‘Readme.Rmd’ ‘Readme.html’
• checking for left-over files ... OK
• checking index information ... OK
• checking package subdirectories ... OK
• checking R files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... OK
• checking whether the package can be loaded with stated dependencies ... OK
• checking whether the package can be unloaded cleanly ... OK
• checking whether the namespace can be loaded with stated dependencies ... OK
• checking whether the namespace can be unloaded cleanly ... OK
• checking use of S3 registration ... OK
• checking dependencies in R code ... OK
• checking S3 generic/method consistency ... OK
• checking replacement functions ... OK
• checking foreign function calls ... OK
• checking R code for possible problems ... OK
• checking Rd files ... OK
• checking Rd metadata ... OK
• checking Rd line widths ... OK
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• checking for code/documentation mismatches ... OK
• checking Rd \usage sections ... OK
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking examples ... OK
• checking PDF version of manual ... OK
• DONE

Status: 1 NOTE

• 9. Please add explanations below for any exceptions to the above:
• 10. If this is a resubmission following rejection, please explain the change in cirucmstances.