...so that I can make both archival (Product_Metadata_Supplemental) and non-archival (e.g. external databases) supplemental metadata searchable and accessible from the registry
Additional Details
Acceptance Criteria
GivenWhen I performThen I expect
Engineering Details
Design Questions
How do we include this in the API? Should this be separate from properties? Maybe a separate supplemental area?
Or do we model this in some registry or supplemental discipline LDD, e.g. supplemental.Discipline.supplemental.field_name?
Motivation
...so that I can make both archival (Product_Metadata_Supplemental) and non-archival (e.g. external databases) supplemental metadata searchable and accessible from the registry
Additional Details
Acceptance Criteria
Given When I perform Then I expect
Engineering Details
Design Questions
properties? Maybe a separatesupplementalarea?registryorsupplementaldiscipline LDD, e.g.supplemental.Discipline.supplemental.field_name?