I&T Tasks for Sprints ending 10/20/22, 11/10/22, 12/1/22, 12/22/2022 I&T tasks

[tloubrieu-jpl]

🟢 Issues Ready For I&T

Information Model:

• As a user, I want to describe a relationship between an attribute in the model and the column of a table pds4-information-model#473
• Harvest skips path that is the root of a soft link  harvest#102

Registry & web API

• registry-manager won't set archive-status on some collections registry#97
• archive status value was not changed on bundle's contents registry#118
• observational end-point returns collections registry-api#202
• As a registry-tool/registry-user I want to ensure leading multiple forward-slashes in request paths are stripped out registry-api#208
• As a user, I want the API to support redundant / in the url registry-api#212
• As a user, I want query responses for empty results to be clearly documented pds-api#198
• Develop NASA/PDS Skin for Search API Swagger interface pds-api#194
• /all suffix returns a message which I don't understand registry-api#190
• ref_lid_collection error when ingesting data sets registry-mgr#57
• hits appears to be showing the current page count, not the overall number of its pds-api#199
• vnd.nasa.pds.pds4+xml format does not return information pds-api#215
• Harvest service sometimes skips collection inventory files registry-harvest-service#25

Validate

• Latest validate missing label extension warning validate#546
• Validate fails regression test on issue 188 validate#551
• --spot-check-data flag throws IOException validate#554
• pds4.bundle option seems to not travel through enough subdirectories validate#444
• Refactor content validation to more robustly handle intermingled Headers validate#425
• Validate does not calculate overlaps correctly when Header is not first object in file validate#480
• Validate should not check PDF/A validity if content validation is disabled validate#453
• Refactor getMessageCountBasedOnProblemType function using introspection validate#537
• NullPointerException when Table_Delimited is missing records attribute validate#473
• Fix uncaught exception error when validating an array object validate#155
• validate gives a error.table.bad_field_read error validate#544

DOI Service

• DOI Service does not accurately parse <author_list> and <editor_list> in XML labels doi-service#377
• As a publisher, I want to be notified when a new DOI has been minted or significant update to the metadata doi-service#283

📜 Test Plan / Procedure

⚙️ Automated Tests

[jordanpadams]

@viviant100 @tloubrieu-jpl combined all the tickets that I think we need test cases for since B13.0 I&T.

I think we need to come up with a more automated/refined process for this in the future. Maybe continuously generate an in-progress RDD. We could even update to not only have the I&T column to designate something that needs to be tested, but also an additional label to indicate testing complete (or at least test cases developed).

[viviant100]

@jordanpadams sounds good. A changelog will also be helpful for I&T to know what's fixed/updated during the I&T cycle.

[jordanpadams]

@viviant100 what changelog are we referring to here? changelog for the RDD?

[viviant100]

A changelog for the RDD would work, or anything that indicates what changes since last delivery to I&T so I&T can V&V those new changes.

[tloubrieu-jpl]

I would rather focus on developing better change logs for the repositories which could contain tags on tested features and have links to those change logs in a work document for I&t or by using the software summary of the snapshot build (which need to be updated more regularly but this has been broken since we cannot update on the main branch anymore). To me the primary software management tool is standard git repository based, the rdd is more a specific view for our 6 months build cycle.

[viviant100]

Test results are in https://cae-testrail.jpl.nasa.gov/testrail/index.php?/runs/view/20037&group_by=cases:section_id&group_order=asc