hermes.commands.deposit.file
Classes
Usage docs: https://docs.pydantic.dev/2.10/concepts/models/ |
|
Base class that implements the generic deposition workflow. |
Module Contents
- class hermes.commands.deposit.file.FileDepositSettings(/, **data: Any)
Bases:
pydantic.BaseModel
Usage docs: https://docs.pydantic.dev/2.10/concepts/models/
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__
Metadata for generic models; contains data used for a similar purpose to __args__, __origin__, __parameters__ in typing-module generics. May eventually be replaced by these.
- __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(command, ctx)
Bases:
hermes.commands.deposit.base.BaseDepositPlugin
Base class that implements the generic deposition workflow.
TODO: describe workflow… needs refactoring to be less stateful!
- map_metadata() None
Map the given metadata to the target schema of the deposition platform.
When mapping metadata, make sure to add traces to the HERMES software, e.g. via DataCite’s
relatedIdentifier
using theisCompiledBy
relation. 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.