[Spike - Frontend] Create the boilerplate of the Dataset section with Dataset title

[GPortas]

Overview of the Feature Request

Implement the UI for #58 .

What kind of user is the feature intended for?

Developers

What inspired the request?

• UI feature development process

What existing behavior do you want changed?

N/A

Any brand new behavior do you want to add to Dataverse?

N/A

Any open or closed issues related to this feature request?

• Create the boilerplate of the Dataset section with Dataset title #58.

[pdurbin]

As I mentioned during the meeting just now, as has been discussed elsewhere...

• Easier way to get dataset title dataverse#2110

... it's not super fun to get a dataset title from the native API. Here's how:

curl -s https://dataverse.harvard.edu/api/datasets/:persistentId/?persistentId=doi:10.7910/DVN/TJCLKP | jq '.data.latestVersion.metadataBlocks.citation.fields[] | select(.typeName=="title").value' -r

Open Source at Harvard

As discussed, this is why @JR-1991 created EasyDataverse. 😄

Oh and not as bad but to get the version (e.g. 4.0), you need to concatenate major and minor:

curl -s https://dataverse.harvard.edu/api/datasets/:persistentId/?persistentId=doi:10.7910/DVN/TJCLKP | jq '.data.latestVersion.versionNumber'

4

curl -s https://dataverse.harvard.edu/api/datasets/:persistentId/?persistentId=doi:10.7910/DVN/TJCLKP | jq '.data.latestVersion.versionMinorNumber'

0

Again, I think we should at some point take a look at the Semantic API @qqmyers created, though as I said I believe you need an API token to get even published datasets. It's probably a little friendlier. For now, starting with the native JSON API is fine.

[qqmyers]

FWIW: The API key is not required to get the latest version via /api/datasets/:persistentId/versions/:latest/metadata but for some reason /api/datasets/:persistentId/metadata defaults to getting the :draft version rather than latest published and therefore does require a key.