-
Notifications
You must be signed in to change notification settings - Fork 1
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
Labels
Comments
@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 ? |
45.66666% done |
jordanpadams
added a commit
to NASA-PDS/operations
that referenced
this issue
Oct 31, 2024
Sync ESA-PSA label files to a local directory
Converting this to an Epic because we have numerous other tasks to complete to make this a reality. |
π 12/2024 status: Script completed. Need wrapper script and setup cron to do this on a regular basis. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
--download-path
(using file name andops:Label_File_Info.ops:md5_checksum
)--download-path
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
The text was updated successfully, but these errors were encountered: