Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/ropensci/onboarding/issues/127 below:

googleLanguageR · Issue #127 · ropensci/software-review · GitHub

• What does this package do? (explain in 50 words or less):

This package contains functions for analysing language through the Google Cloud Machine Learning APIs

• Paste the full DESCRIPTION file inside a code block below:

Package: googleLanguageR
This package lets you call the 'Google Cloud Translation API' for detection and 
  translation of text.  It also allows you to analyse text using the 
'Google Natural Language API' 
  for analysing sentiment, entities or syntax.  
You can also analyse sound files and transcribe them
  to text via the 'Google Cloud Speech API'.

• URL for the package (the development repository, not a stylized html page):
  https://github.com/MarkEdmondson1234/googleLanguageR

• Please indicate which category or categories from our package fit policies this package falls under *and why(? (e.g., data retrieval, reproducibility. If you are unsure, we suggest you make a pre-submission inquiry.):

Data extraction for the translation and Speech to text API calls, text analysis for the entity detection API call.

• Who is the target audience?

Analysts working with sound files and/or text that need translation and/or text analysis such as sentiment, entity detection etc.

• Are there other R packages that accomplish the same thing? If so, how does
  yours differ or meet our criteria for best-in-category?

The Natural Language API is replicated by many R packages such as tidytext but it does offer a bigger trained dataset to work from than what an analyst can supply themselves.

The Speech to text I'm not aware of any R packages that do this, especially with the Google one as its pretty new. there may be other APIs that are called via R that do it.

The Translation API, the recently released cld2 does language detection offline (and was the prompt I came across rOpenSci again) and is recommend way to detect language first to see if its text that needs translation, but then the translation itself I'm not aware of any R packages, again I'm fairly sure none call the new Google Translate API as its fairly new - note this is the one that uses neural nets and not the older one used online and has been available for ages.

Confirm each of the following by checking the box. This package:

• [x ] does not violate the Terms of Service of any service it interacts with.
• [ x] has a CRAN and OSI accepted license.
• [x ] contains a README with instructions for installing the development version.
• [ x] includes documentation with examples for all functions.
• [x ] contains a vignette with examples of its essential functions and uses.
• [x ] has a test suite. (but only works locally at the moment due to authenticated API)
• [ x] has continuous integration, including reporting of test coverage, using services such as Travis CI, Coeveralls and/or CodeCov. (but see above, pending a fix around this)
• [ x] I agree to abide by ROpenSci's Code of Conduct during the review process and in maintaining my package should it be accepted.

• [ x] Do you intend for this package to go on CRAN?
• Do you wish to automatically submit to the Journal of Open Source Software? If so:
  • The package contains a paper.md with a high-level description in the package root or in inst/.
  • The package is deposited in a long-term repository with the DOI:
  • (Do not submit your package separately to JOSS)

• [x ] Does R CMD check (or devtools::check()) succeed? Paste and describe any errors or warnings:
  Tests fail online as not authenticated:
  OK: 0 SKIPPED: 0 FAILED: 3

  1. Error: NLP returns expected fields (@test_gl.R#7)
  2. Error: Speech recognise expected (@test_gl.R#20)
  3. Error: Translation works (@test_gl.R#34)

• [x ] Does the package conform to rOpenSci packaging guidelines? Please describe any exceptions:
  I haven't a short, lowercase name for the package name. This is largely due to a standard set for all the Google API packages I've written to help aid discoverability in Google search. I've been bitten by similar packages calling the Google Analytics API that were called rga and RGA...

• If this is a resubmission following rejection, please explain the change in circumstances:
  NA

• If possible, please provide recommendations of reviewers - those with experience with similar packages and/or likely users of your package - and their GitHub user names:

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4