| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | datacite: get rid of schemaVersion | Martin Czygan | 2020-01-09 | 1 | -2/+1 |
| | | |||||
| * | datacite: reformat test cases and use jq . --sort-keys | Martin Czygan | 2020-01-08 | 1 | -13/+13 |
| | | |||||
| * | datacite: adding datacite-specific extra metadata | Martin Czygan | 2020-01-07 | 1 | -23/+26 |
| | | | | | | | | | | | | | | * 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: add conversion fixtures | Martin Czygan | 2020-01-02 | 1 | -0/+26 |
| 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 | |||||
 |
index : fatcat | |
| [no description] |
| aboutsummaryrefslogtreecommitdiffstats |