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

Meta-Issue: Transmission Fixity #867

Open
dannylamb opened this issue Jul 3, 2018 · 8 comments
Open

Meta-Issue: Transmission Fixity #867

dannylamb opened this issue Jul 3, 2018 · 8 comments
Labels
Subject: Drupal related specifically to Drupal, usually pointing somewhere on drupal.org Type: enhancement Identifies work on an enhancement to the Islandora codebase Type: Meta-issue Identifies multiple related tickets for ease

Comments

@dannylamb
Copy link
Contributor

We currently utilize transmission fixity from Drupal to Fedora, but don't support it on the initial upload into Drupal. We need to be able to provide it in the REST api as well as allow users to provide their own checksum when uploading through a form.

@jonathangreen
Copy link
Contributor

We also need some reasonable way in the UI to let the user know their fixity failed when adding objects. Both individual objects, and batches.

Would this functionality rely on the microservice we are talking about in #847?

@dannylamb
Copy link
Contributor Author

dannylamb commented Jul 3, 2018

I don't think it would. This is just to get it in before #847 's microservice can check it on demand.

@dannylamb
Copy link
Contributor Author

We also shouldn't forget about covering the use case of ingesting using the Migrate framework, since it's our batch replacement.

@mjordan
Copy link
Contributor

mjordan commented Sep 5, 2018

Related, we should be verifying checksums on migration (not just in general Migrate usage). In other words, get the checksum from Islandora 7.x, migrate the file, then confirm that the 7.x and CLAW checksums match. Report mismatches. Would only work on 7.x's where checksums were enabled. This use of transmission fixity is related to #917.

@ajs6f
Copy link

ajs6f commented Sep 5, 2018

@mjordan Definitely that's something that should be available, but it should be config'able for those sites for which fixity is a service that comes from well beneath the repository layer. For sites like that (like us 😁 ) recalculating checksums between two Islandora instances (of any version) is just extra grinding for no more trust.

@dannylamb dannylamb changed the title Transmission Fixity Meta-Issue: Transmission Fixity Sep 18, 2018
@dannylamb
Copy link
Contributor Author

Converting this to a meta issue to track development of a transmission fixity feature. Please refer to this issue in any subsequent issue to link them.

To further clarify the scope of this ticket, we're only concerned with providing a checksum when you upload a file, so that it can be verified once deposited in the repository.

@Natkeeran
Copy link
Contributor

Further discussion about providing a UI for file and media is found here: #1102

@mjordan
Copy link
Contributor

mjordan commented Aug 4, 2021

For those using Islandora Workbench, it now supports transmission fixity validation. Docs are at https://mjordan.github.io/islandora_workbench_docs/fixity/.

@kstapelfeldt kstapelfeldt added Subject: Drupal related specifically to Drupal, usually pointing somewhere on drupal.org Type: enhancement Identifies work on an enhancement to the Islandora codebase Type: Meta-issue Identifies multiple related tickets for ease and removed drupal labels Sep 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Subject: Drupal related specifically to Drupal, usually pointing somewhere on drupal.org Type: enhancement Identifies work on an enhancement to the Islandora codebase Type: Meta-issue Identifies multiple related tickets for ease
Projects
Development

No branches or pull requests

6 participants