Skip to content

generate_registry_status_reports.py results incompleteΒ #471

@plawton-umd

Description

@plawton-umd

Checked for duplicates

No - I haven't checked

πŸ› Describe the bug

When I downloaded and reviewed the staged collections report, I noticed 6 collections that should have been listed were not listed. A check via OpenSearch queries confirmed they were in the registry with the archive_status value of staged.

πŸ•΅οΈ Expected behavior

I expected all staged collections to be listed.

πŸ“œ To Reproduce

  1. look at the staged collections report for collections in the bopps2014 collection, https://github.com/NASA-PDS/registry/tree/develop/docs/status. urn:nasa:pds:bopps2014:raw::1.0 is the only one listed in the file.
  2. run
    pds-registry-client -v -p -d '{"query":{"match":{"_id":"urn:nasa:pds:"}}}' '/sbnumd-registry/_search' where the list is
    bopps2014:biassub::1.0
    bopps2014:calibrated::1.0
    bopps2014:document::1.0
    bopps2014:groundcalibration::1.0
    bopps2014:raw::1.0
    bopps2014:scoadded::1.0
    bopps2014:status::1.0
  3. Check the archive_status of each
    ...

πŸ–₯ Environment Info

  • the files created in January
    ...

πŸ“š Version of Software Used

No response

🩺 Test Data / Additional context

No response

πŸ¦„ Related requirements

πŸ¦„ #xyz

βš™οΈ Engineering Details

No response

πŸŽ‰ Integration & Test

No response

Metadata

Metadata

Assignees

Labels

Type

Projects

Status

🏁 Done

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions