This almost keeps the revision metadata format as is. It sends the raw
metadata (xml instead of the parsed json before).
Questions:
- do we keep the raw metadata attached to the revision as it's currently done?
-> currently the deposit server now writes thosee raw metadata to the directory (during an update D4013), not on the revision as it cannot.
-> if we need to change that,it (attach the raw extrinsic metadata to the directory in the metadata storage), that's doable. It's a more involved refactoring though as the package loader does not allow it yet. that's a more involved refactoring that's needed since no loader writes to the directory right nowAnd this can be done as a next diff.
- revision: do we send one raw extrinsic metadata per xmlcolumn per raw xml received (the deposit allows this) file or one joined xml (as it is in the current diffthat's the current taken approach which match the task).
Let's discuss ^
Related to T2649
Related to D4100
Related to D4101