Refactor DataPackage to support both v1 and v2 system metadata
DataPackage needs to be refactored to use both V1 and V2 Sysmeta, handle mixed MNs
#4 Updated by Ben Leinfelder over 6 years ago
- Status changed from In Progress to Closed
- % Done changed from 30 to 100
There's now a corresponding DataPackage "convenience" class for supporting V2 types and APIs. In a mixed MN scenario, the D1Object does it's best to download an appropriate object from the ObjectLocationList it gets from the CN. As long as there is one replica of the object on a MN that supports the version of Datapackage being used, the package will be constructed as expected. If that is not the case (e.g., the object only lives on v1 MNs and we are using a v2.Datapackage) then the user will need to use a v1.Datapackage instead.