jamlung-ri
commented
2 months ago Overall I am feeling pretty good about this. I had some comments in my review of this earlier today, and I've divided them up by person:
For @paynejd and @jamlung-ri :
- Overview:
- New attributes (e.g. CRMI attributes) might need to be placed here? Should we worry about that now? I lean towards no, but want to make sure. Might answer this on Friday’s Arch call. The attributes fit decently well into existing sections though.
- References:
- What filters are appearing in the Group by Source view? Are we filtering only by references, or by concepts/mappings, or both?
- The “Group by Source” view only seems to show concepts (which is probably fine?), but mappings also can come from a reference. Jon/Joe should think about this.
- Version Selector and Summary: For repos that have references, do we need to show the count of references?
- (Paul asked this up above) Is there a need for a more detailed 'list'? If so, could we capture the user stories below?
For @paulsonder :
- Expansion selector:
- Need to see this design - might be a light version of the Version selector but without Visibility or Status, but also has a way to view/summarize Parameters (might have OCL put tags or something
- Being able to compare Expansions, just like we do Repo versions, will be important
- Once an expansion is selected, should we somehow show that parameters are applied? Maybe just an icon that can be clicked on?
- Content > Concepts/Mappings: What ticket documents the different concept/mapping views we will support? The designs currently show “Hierarchy” and “Group by source”. What other views will we offer at launch?
- Concept List (i.e. the default for non-hierarchical sources)
For @snyaggarwal :
- Mappings:
- Just to check: How possible is this view from an API standpoint? Do we have Sunny’s approval for this?
snyaggarwal
paulsonder
Introduction
The visual architecture of the Repository layout and design in V3 aims to give users efficient access to the information they need most as well as visually distinctive patterns to represent owner information, metadata, content, versions, expansions and summaries.
The layout is designed to include the maximum amount of content a user may need to see when viewing a FHIR resource (part of OCL's drive to introduce new 'repo types' such as CodeSystems, ValueSets and ConceptMaps alongside the legacy 'Sources' and Collections'), meaning new thinking for attributes that V2 did not intuitively expose
Header
The header patterns allows a user to identify the Repo's Code, Type, Version, Name and Owner. A number of CTA's allow them to change the version, navigate to the owners Organization page and Follow, Export or Share the Repository. For users with Edit permissions, the menu on the top right of the header includes CTA's to manage the Repository.
Summary panel
To the right of the main content area in the template the user can find the Summary panel. It currently consists of three sections:
Chips: This panel includes chips to indicate attributes such as visibility, if the Repo is FHIR ready or it's content flagged as Experimental.
Summary: The Repository summary is below, which brings the V2 summary up front in the UI and could be extended to include counts of new Repository attributes, such as 'Custom Attributes'. Each attribute in the Summary may have additional information to be displayed using the Extended Tooltip component.
Contributors: The Repository contributors are listed below, visualised using their avatars, which are clickable and lead to their User profile page.
Overview
The primary content area of the Repository template is a tabbed view of the Repositories content, including the metadata and content itself (Concepts, Mappings, References).
The Overview serves to house the Repositories metadata and some content from the OCL 'legacy' repo's, such as About. If a particular attribute is not mandatory and has not been added by the author, 'Approval date', for example, then it will not be included in this section.
This section was modelled on the metadata attributes of a FHIR resource. The groupings in the page have been created by the OCL team. These are: Descriptions and Use, Publisher and contact and Reviews and approvals.
Content
The content of the Repository is organized into tabbed sections. These may change depending on the Repository Type. The tabs display content in tabular or card views. Tabs include:
Concepts: Both tables and cards can be filtered. The tabular display allows for a Hierarchical layout.
Expansions: You will notice that the Expansion picker is positioned closer to the content in the layout hierarchy. This proximity implies the relationship with the content and less the Repositories metadata and other versions. I'm interested to know what you think about this.
Mappings: The revised tabular view of mappings uses the 'Group by' design that emerged as a useful mode of understanding Mappings.
References: When a user views a Collection, they should be able to understand the composition of the Repositories content, even if it has not been expanded. Here we utilise a 'Grouped by' view, organised as default 'By source'.
Versions
The current method of navigating versions in V3 is via the Versions menu accessible in the header. This list enables a user to understand some high level information and is the entry point into the Comparison tool. The position in the page hierarchy is intentional and designed so that the user is aware that all data may change below it, should a different version be selected.
Question: Is there a need for a more detailed 'list'? If so, could we capture the user stories below?
Full screens for all the design above can be found here.