hi,
I'm looking for info how to use Oak in a revision-/audit-proof manner to
archive versioned assets in a (read-only) repo. The only related document I've
found so far is the talk "Binary Data Management Features in Oak 1.8" from
Matt and Conrad. Any other sources or ideas?
Thanks,
O.
Hi Oliver,
Can you provide a bit more detail about what you are looking for?
I think what is unclear to me is whether you are speaking about multiple
Oak instances or just one. I’m guessing what you have in mind is something
like one Oak instance can write to a repo, and a second Oak instance ca
HI Oli,
while I let Matt and the other oak developers discuss the technical
aspects, I would like to point to a less technical aspect: certifications.
Oak does not have any certification in the area of "compliant archiving",
which rules out cases, where the business is willing to go for that risk.