Adding metadatablock files for The Negotiation Data Repository

[jggautier]

Closes #145

Adds the metadatablock TSV properties files to this GitHub repository's "metadatablocks" directory.

Note the block expects a Dataverse collection with alias 'NegotiationDataRepository' to exist. (on prod: https://dataverse.harvard.edu/dataverse/NegotiationDataRepository )

For this to be done, after QA, to sanity check the block, the last step is to load into production.

[scolapasta]

Looks fine. One thought I have is about the setup script (it's not part of this PR it just loads all). If the dv's don't exist it puts them at root. So I wonder if we should somehow have the script first add the dv's. Of course it would have to know what to give them for an alias in some way.... (this might be out of scope for this issue). Thoughts @jggautier @pdurbin ?

[jggautier]

Hey @scolapasta. I'm not too sure what the setup script does. Would this be how the metadatablock is added to a "production" server, like the Harvard Dataverse Repository? If so, so far whenever I've been involved in creating a metadatablock for only one collection, the collection's already created. But I think your idea wouldn't hurt.

If it's for testing/QA, I think your idea sounds helpful. I think that when @kcondon was testing, the fact that a collection with the right alias wasn't already created in the test server he was using was a bit of a hiccup.

[pdurbin]

I'd say the script is out of scope. To me the current effort is about making the Negotiation Data fields available.

[scolapasta]

I do think we should change the code so that if a tsv file lists a dv alias and it is not found, the upload fails. That can be a separate issue that I will open: IQSS/dataverse#8675

[kcondon]

looks good, ready for deployment