1 / 13

Efficient Version Management in ebRIM 3.0 for Metadata Objects

Learn how to update metadata without submitting new documents, deprecate items without updates, and manage versioning effectively in ebRIM 3.0. Includes guidelines for logical IDs and object deprecation strategies.

gibbsj
Download Presentation

Efficient Version Management in ebRIM 3.0 for Metadata Objects

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ebRIM 3.0 Version Management

  2. Use Cases • Update metadata without submitting new document (version mgmt) • Deprecate without update • Delete

  3. Version Mgmt • Versioning of Documents and Metadata objects (separately) • Focus on versioning of metadata objects • ebRS 3.0 Section 5.7

  4. New Attributes • lid - logical id • versionInfo

  5. Logical ID Attribute • First version of object has lid = id • Second (and after) has • Same lid attribute • New id attribute

  6. versionInfo attribute • Maintained by Registry • Incremented for each version of an object

  7. Submitting Update • Use UpdateObjectsRequest • Would pass through Document Repository actor un-altered • Entire object is updated (XDSDocumentEntry for example)

  8. Packaging Update • XDS requirement that all submissions are bundled into SubmissionSet • Simplest update - of SubmissionSet object • Same lid as original • New id

  9. Packaging Update (2) • Update Document • SubmissionSet and Association with new lid • DocumentEntry with original lid and new id

  10. Query • Always reference latest version • Existing Stored Queries reference latest version • Add new Stored Query to get all versions of an object given parameter “lid”

  11. lid vs id conflict • Sometimes reference is to id • Submission Set HasMember reference to new version • Sometimes reference is to lid • Everywhere else • Rule • Submission Set HasMember reference is always to id • All others use lid

  12. Deprecate without Update • DeprecateObjectsRequest • Pass through Document Repository • Specify object(s) to deprecate via • ObjectRefList • Stored Query specification

  13. Delete • RemoveObjectsRequest • Pass through Document Repository • Specify object(s) to remove via • ObjectRefList • Stored Query specification • Problem: what to do about document in repository?

More Related