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.
What does this do?
Why are we doing this? (with JIRA link)
This brings in a few changes from QA which were identified in order to bring more consistency between the chronology field names and their default messages. In addition, the associated authorities block was seen as still needing more work before it's ready for production and as such has been removed from the chronology authority as well as having its vocabularies removed.
How should this be tested? Do these changes have associated tests?
primaryDateRangeStructuredDateGroup
spatialCoverages
+ subfieldsaltDateGroupList
+ subfieldsDependencies for merging? Releasing to production?
I opted to leave the associatedAuthorities extension in as opposed to the application layer which removed it. I added a comment to note that it is currently unused, and can remove the extension if desired.
Actually the associatedAuthorities block is still referencing vocabularies which have now been removed, so I should probably remove those before merging.
Has the application documentation been updated for these changes?
No
Did someone actually run this code to verify it works?
@mikejritter tested against a local instance