Create report of similar projects between ETN & OTN

[diniangela]

Create a report of projects in ETN & OTN that are similar. This can be checked by comparing the tag/receiver serials and years to see if they're the same. If they are, add issues to GitHub

• Create a script to compares the projects that are living on both database
• Make this into an API to make it available
• create scripts for:
  • Tags
  • Receiver
  • Deployments
  • Animals
  • projects

compare dates, serials, naming

[diniangela]

from meeting:

• As a diagnostic tool, a good idea to see when each was last reported, "this projects was once considered X", check for open deployments
• Push time works for us,
• Checks for overlaps:
  • Same researchers?
  • same gear in the water at the same approximate times?
  • Different gear in the water in the same place at the same time.
  • fuzzy project titles and abstract checking?
  • Nice visualization opportunity for this project.

[diniangela]

Started working on this in the OTN push code

[jdpye]

from meeting:

• As a diagnostic tool, a good idea to see when each was last reported, "this projects was once considered X", check for open deployments

• Push time works for us,

• Checks for overlaps:

  • Same researchers?
  • same gear in the water at the same approximate times?
  • Different gear in the water in the same place at the same time.
  • fuzzy project titles and abstract checking?
  • Nice visualization opportunity for this project.

We're currently running the above checks in our push process. The report that comes back can be shared with ETN, but -what- to do with this information remains to be determined.

[jdpye]

Create single report per push - list of possible alias projects, with a link to OTN or node project page, and a link to the IMIS page for the project.

[diniangela]

https://gitlab.oceantrack.org/otndc/otn_data_push/-/issues/537

[diniangela]

Started working on this, is this a good format or should there be a different format?

Similar contacts between OTN and ETN:
similar_contacts.csv

Similar tags between OTN and ETN:
similar_tags.csv

Similar receivers between OTN and ETN:
similar_receivers.csv

[diniangela]

For June push:

Similar contacts between OTN and ETN:
etn_similar_contacts_june2024.csv

Similar tags between OTN and ETN:
etn_similar_tags_june2024.csv

Similar receivers between OTN and ETN:
etn_similar_receivers_june2024.csv

[jdpye]

I mentioned this above, but I think we should operationalize this check-up between OTN and ETN. This ticket 'how to do it', appears completed. The need to repeat this process and make it a 2-way conversation that happens around OTN+Nodes push time can be a recurring task here or a more obvious formal exchange. If we (@diniangela , @CLAUMEMO @jdpye @jreubens ) can agree on how/where to do that, I would like to close this ticket.