Skip to contents

etn (development version)

etn 3.0.0

Use etn on your computer 🎉

  • etn now connects to the ETN database with an API provided by the etnservice package (#280). This means you can use the package from your own computer. Note that this will be slower than running it from the VLIZ RStudio server.
  • etn will automatically switch to a local database connection when available (e.g. the VLIZ RStudio server). Use Sys.setenv(ETN_PROTOCOL = "opencpu") to override this behaviour and force the package to use the API (#398).
  • Queries via the API and the VLIZ RStudio Server will return the same results (#317).
  • When using a local database connection, etn will check if the installed helper package etnservice that is used to place these queries is up to date with the one deployed via the API. This is to ensure that queries placed via the API and via the local database connection always result in consistent results. If the installed version of etnservice is older, you will be prompted to install a newer version (#385).

Credentials

Breaking change! Action required

Your credentials (username and password) to connect to the ETN database are no longer passed via the connection argument. They are asked or retrieved from your .Renviron file every time you run a function.

Here is how you can migrate:

  1. Use the new RStudio server (https://rstudio4.vliz.be/). The LifeWatch RStudio server (https://rstudio.lifewatch.be) won’t work with this version of etn and will be discontinued.

  2. Follow the steps in vignette("authentication") to look up and store your credentials.

  3. Update your scripts:

    # Good
    get_animals(animal_id = 305)
    
    # Bad
    connect_to_etn()
    get_animals(con, animal_id = 305)
    get_animals(connection = con, animal_id = 305)

Accessing data

Changes for developers

  • New vignette vignette("options") describes some developer options (#398).
  • Contributors can change the default domain of the API to the URL of a test server via the environmental variable ETN_TEST_API (#383).
  • Tests make use of vcr to record and replay HTTP requests to the API. These results are stored in /tests/fixtures (#432).
  • Tests have new helper functions, including skip_if_not_localdb(), skip_if_http_error() and expect_protocol_agnostic(). The latter is used to compare SQL vs API calls in test-protocol_agnostic.R (#436).
  • Tests for download_acoustic_datasets() are updated for archival tags and SQL vs API calls and makes use of markdown snapshots (#366).
  • pkgdown website is now automatically build by a GitHub Action and is served from the gh-pages branch. The docs/ directory has been removed (#456).
  • vignette("acoustic-telemetry") is precompiled with vignettes/precompile.R, so it doesn’t run for every build (#473).

Miscellaneous

  • etn now relies on R >= 4.1.0 (because of arrow and vcr dependencies) and uses base pipes (|> rather than %>%) (#327, #384).
  • write_dwc() now invisibly returns the transformed data as a list of data frames (rather than a data frame) (#302).
  • Previously deprecated functions get_deployments(), get_detections(), get_projects(), get_receivers(), list_network_project_codes() are now removed.
  • vignette("etn_fields") was outdated and has been removed (#468).

etn 2.2.2

Bug fixes

Miscellaneous

  • Tests depending on local database connection are now skipped when it is absent on testing machine (#346).
  • Funder is updated and custom authors are removed (#311).
  • The README now has a Zenodo badge (#352, #355).
  • New CITATION.cff file (#337).
  • pkgdown website has been updated (#354).

etn 2.2.1

etn 2.2.0

etn 2.1.0

  • Funder and default README.Rmd are added (#247).
  • New function write_dwc() transforms acoustic telemetry data to Darwin Core that can be harvested by OBIS and GBIF (#257).

etn 2.0.0

This releases updates the package to make use of the new model and scope of ETN. Have a look at this milestone for all issues that are included.

  • tag_serial_number is now the primary identifier for tags. Tags can have multiple types, subtypes and sensors. Acoustic information is related to the acoustic_tag_id.
  • acoustic scope remains completely covered, but is now reflected in function names. This allows us to implement additional scopes (e.g. cpod) in the future.
  • Old function names are deprecated.
  • New vignette("acoustic-telemetry") showcases an acoustic use case.
  • Test coverage is increased.