Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Update publish plan resolver for EZID registration

Aperta
  • Qualcosa non va?
#32 3 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@jupiter007 ci sta già lavorando.

Dal 7/7/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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.

Lingua principale
JavaScript
Stelle
0
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CDLUC3/dmsp_api_prototype

Tutte le issue di CDLUC3/dmsp_api_prototype

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.