aboutsummaryrefslogtreecommitdiffstats
path: root/python/tests/files/datacite/datacite_result_09.json
Commit message (Collapse)AuthorAgeFilesLines
* wip: contrib, GH59Martin Czygan2020-07-101-1/+2
|
* datacite: get rid of schemaVersionMartin Czygan2020-01-091-1/+0
|
* datacite: reformat test cases and use jq . --sort-keysMartin Czygan2020-01-081-32/+32
|
* datacite: factor out contributor handlingMartin Czygan2020-01-081-0/+11
| | | | | | | Use values from: * attributes.creators[] * attributes.contributors[]
* datacite: adding datacite-specific extra metadataMartin Czygan2020-01-071-32/+37
| | | | | | | | | | | | | * attributes.metadataVersion * attributes.schemaVersion * attributes.version (source dependent values, follows suggestions in https://schema.datacite.org/meta/kernel-4.3/doc/DataCite-MetadataKernel_v4.3.pdf#page=26, but values vary) Furthermore: * attributes.types.resourceTypeGeneral * attributes.types.resourceType
* datacite: address raw_name index form commentMartin Czygan2020-01-021-1/+1
| | | | | | | | | > The convention for display_name and raw_name is to be how the name would normally be printed, not in index form (surname comma given_name). So we might need to un-encode names like "Tricart, Pierre". Use an additional `index_form_to_display_name` function to convert index from to display form, heuristically.
* datacite: add conversion fixturesMartin Czygan2020-01-021-0/+35
The `test_datacite_conversions` function will compare an input (datacite) document to an expected output (release entity as JSON). This way, it should not be too hard to add more cases by adding: input, output - and by increasing the counter in the range loop within the test. To view input and result side by side with vim, change into the test directory and run: tests/files/datacite $ ./caseview.sh 18