B13.1 Updates per CCB-Approved SCRs

[jordanpadams]

💡 Description

See sub-tasks for more details, but planned tasks include:

• PDS Annex products
• XML files as digital objects.
• Citation_Information class and doi metadata
• Access rights for PDS data – Licensing Information

[jordanpadams]

📆 January status: Delayed. No SCRs approved yet.

[jordanpadams]

📆 February status: Work ongoing. Numerous CCB approvals coming in the next week.

[jordanpadams]

All sub-tasks completed

[miguelp1986]

@jordanpadams how should we be testing these sub-tasks? Also, I do not have access to PDS Jira to look at the details. Not sure if I should have that or not.

[viviant100]

@miguelp1986 just send you the credential to access jira.

[jordanpadams]

@miguelp1986 do you have the ZenHub extension installed? you should see several tickets below the initial comment:

[jordanpadams]

and thanks @viviant100 for getting the credentials sent

[miguelp1986]

@jordanpadams I should've been more clear with my question, but some of the tickets say to search for a specific value from an attached PDS4 Information Model Specification and to verify that it's there. Here's an example: https://github.com/NASA-PDS/pds4-information-model/issues/599

Is this that's all that's required to test those kind of tickets?

[jordanpadams]

for those tickets yes. for others (e.g. Product_External or new audio formats), you will probably want to (1) inspect that those new classes and recommendations from the DDWG included in the attached PDFs or on the JIRA ticket were completed successfully (e.g. the create a test product and see if it works in Oxygen or with Validate. you will basically want to make sure the classes/attributes values are in the schema/schematron, and then (2) actually create 1 or more test products that include this information and try to validate them either using Validate tool or via Oxygen.