Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Registry UX punch-list 2021Q2 #236

Closed
10 tasks done
karlcz opened this issue Sep 8, 2021 · 0 comments
Closed
10 tasks done

Registry UX punch-list 2021Q2 #236

karlcz opened this issue Sep 8, 2021 · 0 comments
Assignees

Comments

@karlcz
Copy link
Contributor

karlcz commented Sep 8, 2021

We need to triage the UX review reprot and revise the registry catalog's UI hints...

Below is a list of all of the changes listed under the "Submission Page" heading in @ACharbonneau 's document.

Deriva UX changes:

  • Make the Submission System menu only available to CFDE admins, not users
    • greyed out for my test user

Changes to Submitted Datapackage recordset page:

  • change compact results "cardview" fields as in https://drive.google.com/drive/u/1/folders/1crbuUEujulc9Pze9zdDFH_6CToUhKUHu
  • Can drop “User Help” menu if needed for space in submission system
    • Seems fine, don't need to remove
  • Make palette match homepage. It’s using a different light blue
    • I think this was for the link text color. Looks fixed on app-dev
  • add tooltips for statuses
  • Give statuses red/yellow/green lights
    • Add class decorators to row name (spans)
    • css change to decorate the new classes

Changes to status table data

Changes to approve datapackage edit form:

  • Visible column list for "Edit Submitted Datapackage"
    • link to images
    • remove system columns
    • remove the content after DCC approval status column
      • Decision Time
      • EMRrest API URL
      • Browse URL
      • Summary URL
      • Diagnostics
  • Make palette match homepage. It’s using a different light blue
    • I think this was for the link text color. Looks fixed on app-dev

Changes not currently in scope that need further discussion have been moved to issue #238

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants