Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As a user, I want to sync ESA PSA products from the Search API #135

Open
jordanpadams opened this issue Sep 28, 2024 · 2 comments
Open

As a user, I want to sync ESA PSA products from the Search API #135

jordanpadams opened this issue Sep 28, 2024 · 2 comments
Assignees
Labels

Comments

@jordanpadams
Copy link
Member

jordanpadams commented Sep 28, 2024

Checked for duplicates

Yes - I've already checked

πŸ§‘β€πŸ”¬ User Persona(s)

Data User

πŸ’ͺ Motivation

...so that I can have the ESA PSA products available through the Solr search

πŸ“– Additional Details

I think the easiest route to do this is to have a separate Python script to download the XML to a local archive, and then execute harvest to load it into the legacy registry

Acceptance Criteria

Given a Registry Search API loaded with ESA PSA context products
When I perform pds-sync-api --node-name psa --download-path /path/to/download/XML
Then I expect a python script to download the XML files to --download-path (if they do not already exist)

βš™οΈ Engineering Details

  • query Search API for all PSA context products, bundles, collections
  • paginate through the results
    • check if the LIDVID has already been loaded into the Registry or not
    • if not, check if the XML is already in --download-path (using file name and ops:Label_File_Info.ops:md5_checksum)
    • if the file does not exist, download to --download-path
    • execute harvest on those XML

This will be a two-part ticket since we will then need a bash script to be added to this repo to actually execute harvest on the downloaded data.

πŸŽ‰ I&T

No response

@jordanpadams
Copy link
Member Author

@nutjob4life not sure of the best place to put this script. it can either go somewhere here (with a requirements.txt), our operations repo (which contains a bunch of ad-hoc scripts), or ?

@tloubrieu-jpl
Copy link
Member

45.66666% done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Sprint Backlog
Status: ToDo
Development

No branches or pull requests

3 participants