Standalone Harvest client application providing the functionality for capturing and indexing product metadata into the PDS Registry system (https://github.com/nasa-pds/registry).
...so that I can skip directories I do not want harvest to load
📖 Additional Details
From user:
We have non-archive files in our service directories to support serving the data. Things like DOI landing pages, for example, and pre-made bulk download files. The the loader is going to assume that everything in a directory is either a PDS4 label or something pointed to by a PDS4 label, it's going to choke. We could make an exclusion list of directory names, file names, and file extensions to ignore, if that would help.
Acceptance Criteria
Given a bundle_root/ directory with sub-directories root/subdir1 and root/subdir2, all containing PDS4 XML products
When I perform harvest run with dataPath = bundle_root/ and excludePath = root/subdir2Then I expect all the data from bundle_root/ and root/subdir1 to be loaded in to the Registry, but NOT data from root/subdir2
Checked for duplicates
No - I haven't checked
🧑🔬 User Persona(s)
Node Operator
💪 Motivation
...so that I can skip directories I do not want harvest to load
📖 Additional Details
From user:
Acceptance Criteria
Given a
bundle_root/directory with sub-directoriesroot/subdir1androot/subdir2, all containing PDS4 XML products When I perform harvest run with dataPath =bundle_root/andexcludePath=root/subdir2Then I expect all the data frombundle_root/androot/subdir1to be loaded in to the Registry, but NOT data fromroot/subdir2⚙️ Engineering Details
No response
🎉 I&T
No response