hermes.commands.deposit.file
Attributes
Classes
!!! abstract "Usage Documentation" |
|
Base class that implements the generic deposition workflow. |
Module Contents
- class hermes.commands.deposit.file.FileDepositSettings(/, **data: Any)
Bases:
pydantic.BaseModel- !!! abstract “Usage Documentation”
[Models](../concepts/models.md)
A base class for creating Pydantic models.
- __pydantic_decorators__
Metadata containing the decorators defined on the model. This replaces Model.__validators__ and Model.__root_validators__ from Pydantic V1.
- __pydantic_generic_metadata__
A dictionary containing metadata about generic Pydantic models. The origin and args items map to the [__origin__][genericalias.__origin__] and [__args__][genericalias.__args__] attributes of [generic aliases][types-genericalias], and the parameter item maps to the __parameter__ attribute of generic classes.
- __pydantic_parent_namespace__
Parent namespace of the model, used for automatic rebuilding of models.
- __pydantic_fields__
A dictionary of field names and their corresponding [FieldInfo][pydantic.fields.FieldInfo] objects.
- __pydantic_computed_fields__
A dictionary of computed field names and their corresponding [ComputedFieldInfo][pydantic.fields.ComputedFieldInfo] objects.
- class hermes.commands.deposit.file.FileDepositPlugin
Bases:
hermes.commands.deposit.base.HermesDepositPluginBase class that implements the generic deposition workflow.
TODO: describe workflow… needs refactoring to be less stateful!
- map_metadata() dict
Map the given metadata to the target schema of the deposition platform and return it.
When mapping metadata, make sure to add traces to the HERMES software, e.g. via DataCite’s
relatedIdentifierusing theisCompiledByrelation. Ideally, the value of the relation target should be of the respective type for DOIs in your metadata schema, with the value itself being the DOI for the version of the HERMES software you are using.- Returns:
The mapped metadata.
- Return type:
dict