Skip to content

Update deployment-end-type in GULLIVER studies #277

Description

@sannegovaert

From mails:

Stacy:

Before you start the download, Judy just pointed out to me that deployment-end-type is still a problem. The text in UvA-BiTS track_session.remarkscontains the word dead which sometimes refers to a dead bird and sometimes to a dead logger (=MB equipment-failure). We have 2 options here:

  1. ‎We do not use track_session.remarksto update deployment-end-type at all, i.e. deployment-end-type would be blank for all records.
  2. Judy updates the UvA-BiTS database. She would rephrase the text intrack_session.remarksso that the parsing works correctly. This would take her quite a bit of time which she doesn't have until July.
    The track session remarks in uva-bits include information about why a track session is closed. The word dead is never used without explicitly mentioning if it’s the bird or the tag that died first. However, we did not use the movebank terminology, so a crawl for text extracting on the word dead alone does not work well and introduces errors.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions