Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some Movebank standard reference data fields not automatically recognized #4

Open
peterdesmet opened this issue Oct 25, 2018 · 1 comment

Comments

@peterdesmet
Copy link

@sarahcd Not sure if this is the right place to log data upload issues, but I wanted to document it none the less.

Steps:

  1. Create a csv in the Movebank standard reference data format
  2. Write all column names in lowercase + dashes (e.g. tag-id)
  3. Upload file
  4. All column names are automatically recognized and mapped, except for:
  • deploy-on-timestamp: maybe by design, to force user to check format + timezone
  • deploy-off-timestamp: maybe by design, to force user to check format + timezone
  • ring-id: suprising, given that it is a free text field
  • sensor-type: surprising, given that other controlled fields were mapped. Variations Sensor type, tag-type, Tag type are not recognized either.

These might be a reupload issues, as that is what I have been doing (overwriting existing deployments)

@sarahcd
Copy link
Contributor

sarahcd commented Nov 2, 2018

I've added a task for us to check which fields map automatically and fix it where they should, like for ring-id. As you mention, we would not want fields to map automatically if the user needs to confirm the format, units or mapping of values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants