Feature/hide set defaults

[J4bbi]

• Issue: Hide fields and set default values #74

---

This PR hides the input controls for three fields and sets default values for them in the config.

TODO
An enclosing div is still rendered in the form. A horizontal gray line.

Developer Checklist

Developers should review and confirm each of these items before requesting review

• Code meets acceptance criteria from issue
• Unit tests are written and all pass
• User Test Scripts (if required) are written and have been run through
• Code documentation and related non-code documentation has all been updated

Reviewer Checklist

Reviewers should review and confirm each of these items before approval
If there are multiple reviewers, this section can be duplicated for each reviewer

• Code meets acceptance criteria from issue
• Unit tests are written and all pass
• User Test Scripts (if required) are written and have been run through
• Code documentation and related non-code documentation has all been updated
• Migation has been created and tested

Testing

List user test scripts that need to be run

List any non-unit test scripts that need to be run

[cc-a]

Thanks @J4bbi, looks good to me.

A thought occurred to me about the publication date field. We've decided to hide it but there is still going to be a value set (presumably the date when the draft is initially created). As I understand it Invenio's publication date field maps to publicationYear of the datacite schema. There is some specific guidance in the Datacite schema that:

If an embargo period has been in effect, use the date when the embargo period ends. In the case of datasets, “publish” is understood to mean making the data available on a specific date to the community of researchers.

This still doesn't feel like a value that the end user should be controlling so I don't think this affects our decision to hide the field but it might make sense for the value to determined more dynamically than just when the initial version of the draft is created. I'm going to create a new issue to track investigation into the current interaction with the Datacite schema but this is not something I anticipate being a priority in the near future.