MDS Schema 3 Deprecation Tasks.

[svogt0511]

Purpose

In MDS, creating/updating a DOI calls lupo which does the checking and sends back the appropriate error. That mechanism already exists.

The only task that needs to be done is to add appropriate tests.

Spec Documents

• Product Spec
• Technical Spec

closes: #70

Approach

Open Questions and Pre-Merge TODOs

Learning

Types of changes

• Bug fix (non-breaking change which fixes an issue)

• New feature (non-breaking change which adds functionality)

• Breaking change (fix or feature that would cause existing functionality to change)

Reviewer, please remember our guidelines:

• Be humble in the language and feedback you give, ask don't tell.
• Consider using positive language as opposed to neutral when offering feedback. This is to avoid the negative bias that can occur with neutral language appearing negative.
• Offer suggestions on how to improve code e.g. simplification or expanding clarity.
• Ensure you give reasons for the changes you are proposing.

[codycooperross]

Looks good to me :)

[jrhoads]

The code changes look good to me.
I think this PR could do with a rebase after #68 and #72.
Then the CI testing should work.