Delta Changes design

Current


Example data package

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More โ†’



Bagit-Tree representation

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More โ†’



Differential Versioning

  • Instead of creating entirely new data packages for each version, implement a differential versioning system. This system would only store the changes made between versions, rather than duplicating all files.
  • Each version would be a set of "deltas" or changes from the previous version. This approach significantly reduces storage requirements and indexing complexity.


Use Cases


UC01: Replacing file in a data package

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More โ†’



Compare

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More โ†’



UC02: Editing metadata

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More โ†’



Compare

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More โ†’



Observations
  • First version ORE
  • Metadata changes - reindex all documents relations
    • two way pointers
  • Inefficient for n/2 replacements