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
display bulk import file name as uploaded #372
Comments
I'd just like to clarify that we also need the original image file name to display accurately on the match results page where it is currently displayed over top of the annotated target image and the annotated match candidate(s). Same criteria as above for exports: Expected Behavior Per this post on the Community forum: https://community.wildme.org/t/underscores-dashes-no-longer-displaying-or-exporting-correctly/2721?u=acwadmin1 |
Excellent! Thank you for catching that, I'll get the requirement updated to include that |
@TanyaStere42 I would like to give a try could you please assign it to me |
Absolutely! If you find you need help with system setup or anything, checkout the discord (although we are heading into a long weekend) |
Context
Wildbook currently does filename processing to remove characters from bulk import file names
To allow for easy reconciliation between files in system and external to the system, we need to display the filename as it was originally uploaded, regardless of what preprocessing we do. This means that the original filename should be stored as a string and used for display.
(update to
parameters
json forImportTask
)Current Behavior
file
Caitlin_December_final.xlsx
displays asCaitlinDecemberfinal.xlsx
Expected Behavior
file
Caitlin_December_final.xlsx
displays asCaitlin_December_final.xlsx
Acceptance Criteria
Display is updated on the following pages to show the original file name:
/src/main/java/org/ecocean/servlet/importer/StandardImport.java
/src/main/webapp/imports.jsp
/src/main/webapp/import.jsp
Notes
Related to #267
Community link
https://community.wildme.org/t/underscores-dashes-no-longer-displaying-or-exporting-correctly/2721
The text was updated successfully, but these errors were encountered: