Add get_archival_data_uuid() to fetch archival data file pointers#146
Conversation
…etnservice into 126-get_archival_data_uuid
test deployment; `get_archival_data_uuid()`
…into 147-up-minimum-r
Require R>4.1, switch to native pipes
Fix postman helper script: use magrittr for injection
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added get_archival_data_uuid() which fetches a table containing UUIDs that reference archival data CSV files hosted on lifewatch.com. This function allows filtering by tag serial number, animal project code, or animal ID.
tag_serial_numberis case insensitive. Invalid values are currently checked on the service side, this is slower but more robust for other code wrapping the API. It is also in line with the rest of the package.The test deployment was successful, I'm ok with this going to the development version on main and being pushed to the production deployment.
However, I don't actually need it deployed to production until after the developments on the etn R package are finished. This is no problem since deployments to production aren't triggered automatically but rather by an email to VLIZ IT.