pds-deep-registry-archive does not include all collections within a bundle in SIP/AIP files second round

[tbarnes4]

Checked for duplicates

Yes - I've already checked

🐛 Describe the bug

This may be related to the sweeper issue previously reported in #213 (and NASA-PDS/registry-sweepers#171) that we thought was resolved.

When I run the pds-deep-registry-archive tool (version 1.4 and now 2.0) on the latest version of a bundle, I have three new cases of it not picking up every part of the bundle. In once case only the bundle product was picked up, and the other other two, only the versioned collection and bundle products were picked up, excluding all non-versioned and thus unchanged collections.

Only bundle products and updated collections (including non-updated products):

• urn:nasa:pds:nh_swap::2.1 See [nssdca-delivery] urn:nasa:pds:nh_swap::2.1 operations#928
• urn:nasa:pds:nh_documents::4.3 [nssdca-delivery] urn:nasa:pds:nh_documents::4.3 operations#927

Only bundle product (should add two collections vs v1.0): urn:nasa:pds:nh_lorri::2.0

I have confirmed with @plawton-umd that all are registered and marked as archived.

🕵️ Expected behavior

I expected every collection LIDVID associated with a bundle LIDVID (i.e. specified in the bundle.{lblx,xml}) to be found in the manifest files.

📜 To Reproduce

Run the following commands:
pds-deep-registry-archive -s PDS_SBN urn:nasa:pds:nh_swap::2.1
pds-deep-registry-archive -s PDS_SBN urn:nasa:pds:nh_documents::4.3
pds-deep-registry-archive -s PDS_SBN urn:nasa:pds:nh_lorri::2.0

🖥 Environment Info

• pds-deep-registry-archive 2.0.0
• Operating System: macOS Ventura 13.7.8

📚 Version of Software Used

% pds-deep-registry-archive --version
pds-deep-registry-archive 2.0.0

🩺 Test Data / Additional context

No response

🦄 Related requirements

No response

⚙️ Engineering Details

No response

🎉 Integration & Test

No response

[jordanpadams]

This issue has been investigated and appears to be caused by the registry-api /members endpoint not returning all collections referenced in a bundle's ref_lid_collection field.

A new issue has been created to track the root cause:

• /members endpoint does not return all collections referenced in bundle ref_lid_collection registry-api#720

The problem affects multiple bundles where non-versioned (unchanged) collections are missing from the /members endpoint response, which prevents pds-deep-registry-archive from including them in SIP/AIP manifests.