Platform and services
This documentation is structured around the tasks and goals you are likely to have. Use the table below to map your goal quickly to the corresponding guidance.
| Your goal | Start here | Typical access |
|---|---|---|
| Find an existing term, class, type, or symbol | Find and understand data (PCA Explore) |
No PCA role |
| Retrieve data for software or analysis | Use data in applications (PCA Consume) |
Reader |
| Create a library or extend content | Create and extend content (PCA Evolve) |
Creator |
| Save work and send it to review | Work with drafts and submit content | Creator |
| Assess a proposal and record an outcome | Review and approve changes (PCA Govern) |
Reviewer |
| Publish an existing collection through PCA | Publish your content (PCA Host) |
Collection owner and PCA onboarding |
| Learn, request access, or get help | Learn and get support (PCA Empower) |
Any user |
How the guides fit together¶
Start in the browser when you are learning the domain or checking what a resource means. Move to the API when you know which identifier, representation, or authoring workflow you need. Most documented flows and areas therefore provide both an interactive path through the PCA web application and a technical path through HTTP APIs.
Before an authenticated API call or any authoring task, read Roles, access, and content states. A role controls what you may do, while a content status tells you where a resource is in its lifecycle. The API endpoint and error reference then summarizes the supported Reader and Creator endpoint families.
These platform guides explain how to perform an action. Libraries and Standards explains the collections you are working with, and Governance explains ownership, review, and status. Check that context before treating a resource as suitable for operational use.