File revisions are currently silly for two reasons:
No metadata redo due to lack of relevant TEI->MODS xslt stylesheet.
No passing/storing of any key that would allow us to state that version.X of the content datastream corresponds to file revision x in the Drupal system. Not sure where this should be stored.
Pending that stylesheet and an answer to that question in 2 FileRevisionJob will need to be significantly updated.
File revisions are currently silly for two reasons:
Pending that stylesheet and an answer to that question in 2 FileRevisionJob will need to be significantly updated.