As a VRO engineer
I want to explore the GitHub repository and any related documentation for the Package Manager’s Service API
So that we can inventory the metadata fields available for correspondence (especially distinguishing pre- vs post-2017) and assess feasibility for digital surfacing.
Acceptance Criteria
- I can locate the correct GitHub repo(s) containing API specifications, service contracts, or related implementation code for the Package Manager.
- I can identify and extract a list of metadata fields returned by the API for correspondence packages.
- I can distinguish if/where metadata differs between pre-2017 and post-2017 documents (or confirm if they are indistinguishable).
- I can document each field with the following:
Field name
Data type
Example value (if available)
Required/optional status (based on schema or usage)
- I note any authentication or access challenges required to hit the API or fetch live samples.
- I share my findings with the team
As a VRO engineer
I want to explore the GitHub repository and any related documentation for the Package Manager’s Service API
So that we can inventory the metadata fields available for correspondence (especially distinguishing pre- vs post-2017) and assess feasibility for digital surfacing.
Acceptance Criteria
Field name
Data type
Example value (if available)
Required/optional status (based on schema or usage)