Hi Sam,
I’m actually working on a project right now that uses that type of ingest structure myself; I’ve got some obsolete file formats that Preservica can’t migrate so I came up with a manual migration to do in advance and then upload both the original file and derived file as two separate Generations of the same Preservation Representation to Preservica, doing all this with OPEX/PAX:
https://developers.preservica.com/documentation/open-preservation-exchange-opex
https://developers.preservica.com/blog/using-opex-and-pax-for-ingesting-content
This results in something that looks like this:
You don’t even need pyPreservica for this step, as it’s just all about structuring the files inside nested folders to conform with the OPEX/PAX standard, which you can script using just the os and shutil modules. Hope this helps!
John
Sam
--
You received this message because you are subscribed to the Google Groups "pyPreservica" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
pypreservica...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/pypreservica/812a51cc-9243-49c2-be88-7cdb9a78a425n%40googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.