-
Notifications
You must be signed in to change notification settings - Fork 6
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
Exclude.list management #249
Comments
I suggest naming the exclude_list files like:
Including the parent directory name in the .xlsx file name will avoid confusion if multiple spreadsheets are opened in Excel. I suggest moving the button for the Load Log Output from the home page back to the header (undoing 4133a33 and 6415533) so that it's visible from all the other pages of the site. I often find myself on the missions or compilations page and want to check the load log for something is the way it is. It'd be nice to have simple hrefs with target='_blank' to the load log output and the exclude list in the header so that it's easily accessible from all pages on the site. |
On second thought I propose naming the exclude_list files like:
This is analogous with how the survey_tally files are named. I also propose using the same workflow as is done for the survey_tally files:
Once all of the .xlsx files are created from the .csv files I'll change the load.py logic to use them instead of the repo's smdb/config/exclude.list file. |
#254 has been pulled to production and executed with this output:
File |
The .xlsx -> load -> .csv workflow is now in place in production with the sorted consolidated exclude list written to https://smdb.shore.mbari.org/media/logs/exclude_list.txt |
The exclude.list, by which directories in SeafloorMapping get excluded from consideration by the SMDB load script, has become cumbersome, will only get longer, and must be managed by someone with a working SMDB Docker. This issue addresses changes to improve its management, by changing how: 1) the exclude.list is constructed, 2) additions/subtractions to the list are made, and 3) the list can be evaluated.
The text was updated successfully, but these errors were encountered: