Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Update publish plan resolver for EZID registration

Abierto
  • ¿Algo no está bien?
#32 3 comentarios 0 reacciones 1 asignado Ver en GitHub

@jupiter007 ya está trabajando en esto.

Desde el 7/7/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

The Apollo server's Plan model is already assigning a dmpID to the plan when it is created. We now need to make sure that the DMP id gets published to EZID. EZID then registers the DMP id (aka DOI) with DataCite.

For reference, here is an example of the entire workflow for a specific DMP:

  1. When the user clicks publish in the current Rails tool, the maDMP JSON record is generated in the DMP Hub
  2. A subset of the information from that maDMP JSON is sent to EZID for publication. See the EZID page
  3. EZID validates the JSON and registers the DOI with DataCite.
  4. Once the DOI is registered with DataCite the DOI Landing page becomes available (The DMP Hub currently hosts this in its CloudFront distribution)

For this ticket, we are only going to focus on step 2. What we will need to do:

  • Add some new ENV parameters and a new src/config/ezidConfig.ts
    • The necessary info (API URL, ID, Secret, etc.) to connect to EZID can be found in the AWS System Manager - Parameter Store. Search for /uc3/dmp/hub/dev/Ez.
    • For now add them to your local dotenv file for testing, we will need to get them into the dmptool-infrastructure repo when we're ready to push the PR
    • You can load them into the
  • Add a new datasource for the EZID API.
    • Do NOT submit to EZID if the plan has a default temporary dmp id (meaning the system couldn't create a unique DMP id, see this code). Return an error instead.
    • We want to use the "create" endpoint for the rebuild (the current Rails app is using the DMPHub lambda which is using "mint" endpoint)
    • Use the src/datasources/orcidAPI.ts as a reference. It has an Authorizer structure that we'll need to use.
    • Convert the existing DMPHub Ruby Lambda to determine how to construct the payload that EZID needs
    • Check with Jing, I think we might be able send them JSON now instead of XML
    • Make sure we use the EZID sandbox!!! https://ezid-stg.cdlib.org
  • Update the src/resolvers/plans.ts resolver to call the new EZID datasource to register the DMP id. If it is successful, call the plan.publish function on the Plan model.

Ping me when you get around to testing as well. I will get you the EZID credentials so you can login to their sandbox and review submissions.

Lenguaje dominante
JavaScript
Estrellas
0
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CDLUC3/dmsp_api_prototype

Todos los issues de CDLUC3/dmsp_api_prototype

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.