Open diniangela opened 1 year ago
from meeting:
Started working on this in the OTN push code
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.
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.
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
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
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
compare dates, serials, naming