Associated Authority Field Prefix

[mikejritter]

What does this do?

• Adds assoc prefix to associated authorities fields

Why are we doing this? (with JIRA link)
Jira: https://collectionspace.atlassian.net/browse/DRYD-1286

This helps with fields in the schema which may have the same name, e.g. chronologies_common.chronologyNote and assocCronlogyAuthGroupList/assocChronologyAuthGroup.chronlogyNote. By adding a prefix we're removing the possibility of this collision, as we will have assocChronlogyAuthGroupList/assocChronologyAuthGroup.assocChronlogyNote.

How should this be tested? Do these changes have associated tests?

• Using the PR from the application layer: Associated Authority Field Prefix application#275
• Run the devserver
• Verify that associated authorities can be saved

Dependencies for merging? Releasing to production?
None

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.44%. Comparing base (e04eb31) to head (0908f0d).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #201   +/-   ##
=======================================
  Coverage   95.44%   95.44%           
=======================================
  Files         555      555           
  Lines       10899    10899           
  Branches     1196     1196           
=======================================
  Hits        10403    10403           
  Misses        147      147           
  Partials      349      349           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ray-lee]

Looks good!