<!-- For more information on how to populate this new feature request, see the PDS Wiki on User Story Development: https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Issue-Tracking#user-story-development --> ## 💪 Motivation ...so that I can be always be directed easily to the latest API specification (or a specific version) ## 📖 Additional Details <!-- Please prove any additional details or information that could help provide some context for the user story. --> ## ⚖️ Acceptance Criteria **Given** <!-- a condition --> **When I perform** <!-- an action --> **Then I expect** <!-- the result --> <!-- For Internal Dev Team Use --> ## ⚙️ Engineering Details <!-- Provide some design / implementation details and/or a sub-task checklist as needed. Convert issue to Epic if estimate is outside the scope of 1 sprint. --> Something we will need to figure out, we should be assigning DOIs for each API, not for the overall repo for gathering PDS APIs. How should we do this? * Create separate repos for capturing the search API / DOI API / etc. * Assign DOIs manually through some other means