Repository navigation
Releases: odissei-data/dataverse-mapper
Release list
v2.1.0
v2.0.0
Image: ghcr.io/odissei-data/dataverse-mapper:v2.0.0@sha256:6119c149df871237ce67f3453e61707d80e0ee319790feac9f8f94d265490bfe
Release v1.2.0
What's new
This major version update introduces the addition of mapping the source fields to fields in the top hierarchical level of the dataverse metadata. In the past it was only possible to map to the metadata blocks in the datasetVersion dictionary in the dataverse template. Now it is possible to map to all fields. This addition also allows for mapping of the persistent identifier, making the older specific implementation for this mapping redundant. Therefore this implementation has been removed from the mapper.
The mapper now also has a submodule to all active mappings and templates. This is not only to always stay up-to-date and consistent with the workflow orchestrator, but also to allow for additional endpoints in future versions. These endpoints would implement existing mappings and templates, allowing the user to forgo having to send them along with their request.
Finally, the mapper now has a method to clean the template after the mapping is complete. This removes any fields which have a value of either empty string or empty list. This way there are no unexpected interactions when ingesting empty fields in to a dataverse instance.
In short
- Mapping to all fields in dataverse template is now possible.
- In use templates and mappings are pulled in by using a submodule.
- Added a template cleaner method that removes all empty fields.
- Bumped all package versions.
Full Changelog: v1.1.1...v1.2.0
Introduction of automatic testing
Features
- Split test and image push job.
- Added automatic testing on PR to main, merge to main and tag push.
- Minor bug fixes.
v1.0.1
Minor version
Minor version update to update the project information.
Release v1.0.0
Description
The first release of the dataverse-mapper. This service allows a user to map metadata to the JSON format used by Dataverse. The current version requires the user to submit a template of the expected dataverse fields and a mapping from fields in the input metadata to those fields in the template.
New features
- The querying of the objects from the source metadata has been refactored to use jmespath.
- It is now possible to map an entire object from the source metadata onto a compound in the template.
- The mapping file has been altered with new functionality to fit the above two features.
- Extensive documentation on the mapping file has been added to the README.
Alpha v0.1.0
Alpha v0.1.0
Description
The first Alpha release of the dataverse-mapper service. This service allows a user to map metadata to the JSON format used by Dataverse. The current version requires the user to submit a template of the expected dataverse fields and a mapping from fields in the input metadata to those fields in the template.