Accommodate Typed Relation Display name Fields

[rosiel]

Link to Github issue or other discussion

For my new module, Typed Relation with Display name, we need to alter Workbench to allow it to do what's needed to populate and export these new fields.

What does this PR do?

Adds support for Typed Relation field

What changes were made?

Duplicate existing class for TypedRelationField
Duplicate existing function for splitting the field value
Duplicate all invocations that test whether the field is a typed relation field.

Just to note that Workbench fails silently (no logs, no errors, just doesn't write to the field) if the field type is not recognized. While there is documentation for what fields are supported (will need to be updated?) I'm not sure if failing silently is the best option here? Open to discussion, just wanted to mention this.

How to test / verify this PR?

• Install Typed Relation Display Name module
• add a Typed Relation Display Name field to Repository Item
• create a CSV with values such as: (first three equivalent to Typed Relation, since display name is optional)
  • "relators:aut:119"
  • "relators:aut:Rosie Le Faive"
  • "relators:aut:person:Rosie Le Faive"
  • "relators:aut:119~Le Faive, R.A."
  • "relators:aut:Rosie Le Faive~Le Faive, R.A."
  • "relators:aut:person:Rosie Le Faive~Le Faive, R.A."

Interested Parties

@mjordan_

---

Checklist

• Before opening this PR, have you opened an issue explaining what you want to to do?
• Have you included some configuration and/or CSV files useful for testing this PR?
• Have you written unit or integration tests if applicable?
• Does the code added in this PR require a version of Python that is higher than the current minimum version?
• If the changes in this PR require an additional Python library, have you included it in setup.py?
• If the changes in this PR add a new configuration option, have you provided a default for when the option is not present in the .yml file?

[rosiel]

No tests yet, this is a proof of concept.

[rosiel]

I tried to make this class as short as possible as it inherits from TypedRelationField. This Class could be much shorter if we made the "split into subvalues" function a parameter of the class. In the create() and update() functions, the ONLY difference is using my custom "split_typed_relation_display_name_string" function.