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

Question about OV/VF checking #219

Open
robin-francois opened this issue Feb 7, 2023 · 2 comments
Open

Question about OV/VF checking #219

robin-francois opened this issue Feb 7, 2023 · 2 comments

Comments

@robin-francois
Copy link

Hello there!

I have tested the OV/VF checking in the current version. As I understand it, checking the VF needs to probe the OV.

However, I was wondering if it could be possible to check a VF with the results of the OV probing, but without the folder/files being available. In a context of digital preservation, you may have already archived the OV and you need to check later a VF. It would be very practical if retrieving the OV from the digital repository would not be necessary to perform the check of the VF, for example by storing the probing results in JSON format so that it can be reused later for checking the VF.

@remia
Copy link
Collaborator

remia commented Feb 15, 2023

Hi @robin-francois,

That's a good point indeed, I think it should be possible without too much trouble as this relink feature really just use the result of the DCP parse method which is already exportable as JSON file. The parser output is already pretty stable and tested in the CI so I don't expect big compatibility issue. PR welcome obviously, otherwise I might have a go but there is no guarantee as to when it will be ready.

@robin-francois
Copy link
Author

robin-francois commented Mar 10, 2023

Thanks @remia. I will probably not have any time available to look at it in the foreseeable future. I would happily test any implementation, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants