Open paulsonder opened 12 months ago
In addition to the info above, here are the CTAs and User Stories relevant to Repositories:
Object + CTA | User Story | Requirements |
---|---|---|
Repository: View | View metadata and content list of a repository | About page viewer; Empty state for a repository that has no About section; summary statistics (see above); concept list with hierarchy, card, and table views; mapping list with map type-, source-, and target-focused views; repo version navigator |
Repository: Search | Find a specific repo using full text search or parameter-based search (e.g. any search param supported in FHIR spec or OCL API) | Support FHIR Search Parameters; support sorting and filtering by OCL attributes; repo list with card and table views |
Repository: Compare | See a comparison of two versions of a specified repository, including a summary of differences (e.g. stats) and a list of specific changes (e.g. "New concepts", "Retired concepts", etc. | Select two versions to compare, which shows summary of differences between repos as outlined in #1753 |
Repository: Export | Download an export of a repository in preferred format | OCL zip, csv, and JSON formats; FHIR resource format(s) available, based on repo type (e.g. value set can be downloaded as FHIR ValueSet, Classic Source can be downloaded as CodeSystem or ConceptMap) |
Repository: Bookmark / Star | Get notifications on selected repositories, e.g. new releases, new versions created. | Add repository to user's Bookmarked Repos list |
Repository: Operations | View a list of possible operations and supported parameters and a way to trigger the operation and see results | See #1624 |
Repository: Share | Share/copy a link to a repo | Copy repo link to clipboard |
@paulsonder I'm going to list out some details below for what information a user needs to see on a Repository, while trying to be generic with respect to the type of Repo.
Basic required info:
Secondary optional/helpful info (which would not be displayed primarily but should ideally be accessible and/or viewable):
GitHub-like attributes that we could someday try to leverage:
Info specific for a "Classic Source" that you need to see on a search results page:
Info specific to "Classic Collection" that you need to see on a search results page:
There is another requirement (detailed more in #1776) about the brief representation of Repositories via Chips. This should give a brief glimpse into the Repository, its owner, the version being pointed towards (if applicable), and some other information.