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

Feature request: checksum .md5 plus HH_MM in filename #65

Open
BleakleyMcD opened this issue Sep 21, 2024 · 3 comments
Open

Feature request: checksum .md5 plus HH_MM in filename #65

BleakleyMcD opened this issue Sep 21, 2024 · 3 comments

Comments

@BleakleyMcD
Copy link
Collaborator

  1. When creating whole file checksum, have av-spex create both a .txt version and a .md5 version simultaneously. (SI DAMS VFCU setup needs the .md5 to trigger pickup but the .txt version is able to be read in Mac "preview", which is handy.)
  2. Current whole file checksum name: JPC_AV_xxxxx_yyyy_mm_dd_fixity.txt and would like to have JPC_AV_xxxxx_yyyy_mm_dd_HH_MM_fixity for both .txt and .md5
@BleakleyMcD
Copy link
Collaborator Author

@eddycolloton also turn off creation of JPC_AV_xxxxx_report_csvs when not creating a report

@eddycolloton
Copy link
Collaborator

Do you want the .md5 file for SI DAMS to be named:

  1. JPC_AV_xxxxx_yyyy_mm_dd_HH_MM_fixity.md5
    or
  2. JPC_AV_xxxxx_yyyy_mm_dd_HH_MM.md5

@eddycolloton
Copy link
Collaborator

As of this commit, av-spex will output both JPC_AV_xxxxx_yyyy_mm_dd_HH_MM_fixity.txt and JPC_AV_xxxxx_yyyy_mm_dd_HH_MM_fixity.md5: d253864
Let me know if you want to drop the '_fixity' from the .md5.

The 'fixity check' (off in step1, on in step2) will look for md5 checksums in files that end in '_checksums.md5' or '_fixity.txt' and have date in either yyyy_mm_dd_HH_MM format or the 'legacy' yyyy_mm_dd format. Fixity check output is written to _qc_metadata folder with a similar naming convention: JPC_AV_xxxxxx_yyyy_mm_dd_HH_MM_fixity_check.txt

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

2 participants