Clarify role of abstract_archival_object schema #1424
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Minor tweak to clarify that abstract_archival_object is the parent schema for the four major archival record types: resources, archival objects, digital objects, and digital object components.
Description
Also includes small tweak to remove duplicative information from digital object component schema.
Related JIRA Ticket or GitHub Issue
Motivation and Context
It was not obvious by naming convention that this abstract schema applied to the four major record types.
How Has This Been Tested?
Confirmed no changes were noticeable within the application.
Screenshots (if appropriate):
Types of changes
Checklist: