When I ran the full process (outside of refresh_ipt_project_files() and refresh_ipt_project_files()) there was no confirmation that the functions were actually doing what I thought they were doing. Like, did create_new_ipt_project() actually create a new ipt dataset?
I made some massive assumptions that the functions worked and just moved forward.
The codebase should be updated to include some sort of validation routines to confirm that what we thought we were pushing is actually going across the interwebs to their appropriate destinations.
This was especially relevant when running the various button clicks for making the dataset public, publishing, changing pub org, and registering the project w/GBIF. In some cases, those functions didn't quite go through and the resultant dataset needed to be updated manually in the IPT. Tracking down which ones went through and which ones didn't was (and still is) a mess.
We need some type of response to confirm it worked.
When I ran the full process (outside of
refresh_ipt_project_files()andrefresh_ipt_project_files()) there was no confirmation that the functions were actually doing what I thought they were doing. Like, didcreate_new_ipt_project()actually create a new ipt dataset?I made some massive assumptions that the functions worked and just moved forward.
The codebase should be updated to include some sort of validation routines to confirm that what we thought we were pushing is actually going across the interwebs to their appropriate destinations.
This was especially relevant when running the various button clicks for making the dataset public, publishing, changing pub org, and registering the project w/GBIF. In some cases, those functions didn't quite go through and the resultant dataset needed to be updated manually in the IPT. Tracking down which ones went through and which ones didn't was (and still is) a mess.
We need some type of response to confirm it worked.