Skip to content
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

Manifest validation tool issues: file extension presence detection #2154

Open
elopatin-uc3 opened this issue Jan 22, 2025 · 0 comments
Open

Comments

@elopatin-uc3
Copy link
Contributor

elopatin-uc3 commented Jan 22, 2025

While working with UCI on their manifest-of-manifest submissions, we've noticed two issues in the validation tool:

  1. The need for file extension in the nfo:filename is not caught. For example, if the URL for a file specifies myfile.tif, the corresponding entry in nfo:filename should be myfile.tif ("myfile" without an extension, should be flagged as an error)

Requires file extension to be present (OK)
When submitting a CSV with checkm files in the line entries, the type of manifest generated should be a mrt-batch-manifest. Currently, the validator creates a mrt-single-file-batch-manifest, which is not ideal.

@elopatin-uc3 elopatin-uc3 changed the title Manifest validation tool issues: file extension and manifest type Manifest validation tool issues: file extension presence detection Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant