Skip to content

services: zenodo - metadata to pass [1d] #1952

Open
@pamfilos

Description

@pamfilos

Feature request

What is the expected behavior?
Now that #1941 will be merged, we need to check the data that we pass as metadata in the creation of the record

Minimum metadata list:

  • Upload type* (pick from list)
  • Publication date* (YYYY-MM-DD)
  • Title*
  • Authors.Name* (surname, first name)
  • Authors.Affiliation
  • Authors.ORCID
  • Description*
  • Version
  • Keywords (suggest “CERN Analysis Preservation” & the CAP ID for published analyses in the format “CAP.EXP.xxxx.yyyy”
  • Access right* (recommend Open Access)
  • License* (recommend Creative Commons Attribution 4.0 International)

We need to:

  • create serializers
      - [ ] ZenodoUploadPayload
            - [ ] should check above metadata
            - [ ] check if files to be uploaded exist in bucket of record (`record.files`)
      - [ ] ZenodoSeralizer, for `_zenodo`
  • return validation errors on the response
  • write test when passing random metadata to /upload (e.g additional properties)
  • write test when passing random metadata to zenodo (e.g additional properties)

What is motivation or use case for adding/changing the behavior?

How should this be implemented in your opinion?

Are you willing to work on this yourself?
yes

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions