Design abstract schemas for external info persistence

As an EDS Solution Architect I need a way to persist select external metadata properties retrieved in Fetch and Ingest that would otherwise be lost when we create our own records.

Current thinking: Create an abstract schema that can be applied to master data, work product component, and dataset schemas that can hold IDs or other metadata. See comments for a conceptual whiteboard mockup.

Acceptance Criteria

• Schema has properties that capture needed external attributes for master data, work product component, and dataset objects
• Schema is registered
• Development versions of affected master data, work product component, and dataset schemas are also registered.

Tasks

• Design abstract schema
• Register abstract schema
• Create new master data, work product component, and dataset schemas that have this new abstract schema as an optional property
• Register new master data, work product component, and dataset schemas