‹ Home
Exported

GEMS

https://gems.umn.edu/ https://gems.dev.umn.edu/
Robyn, Project Manager at Matogen DigitalIan Parsons, Head Chef at Matogen DigitalLaura Hurley, Designer, UX and Engagement Specialist at Matogen DigitalDavid Mundell, Developer at Matogen DigitalXoliswa Shandu, Matogen DigitalJohnny Sheridan, Sales Boss at Matogen DigitalPatience Kudyatasa, QA Specialist
From the list: Testing

✔ API Page reverts: Remove comparison button above the accordion & apply Phils feedback

Robyn added this on
Completed by Ian P.
Assigned to
Ian Parsons, Head Chef at Matogen Digital Ian P.
Due on
Notes
Test API pages and add headers - GEMS

There is a "View API comparison" button above the accordion, which needs to be removed:
image.png 14.2 KB • Download

Comments & Events

Robyn rescheduled this to-do
Was
Now
Notified 1 person
Robyn, Project Manager at Matogen Digital Robyn, Project Manager
Hi Robyn,
 
Many thanks for this. Great to see this getting close to release.
 
I don’t have a lot of open time right now, so this is just a quick reaction to keep this ball rolling towards going live. I follow with a few points:
 
  1. Is there a reason to have so much white space above the “Source Details” heading in each of the data products? It fails to visually tie the “Source Details” to the relevant “Data Specifications” material above it, at least to my eye. See, e.g., pasted in below taken from here. I’d recommend closing up the gap to perhaps match the gap between “Data Specifications” and the API Product heading above it.
 
 
  1. Ditto, to minimize scrolling a tad, would it make sense to reduce just a little the white space between each of the entries within each product e.g., between
 
Citation
Grid Level
Layers
etc

  1. Rather than alternate grey vs white blocks in the “Data Specifications” section, would it give more coherence for each of the data products to simply have the API Product heading embedded in a grey band and the product and source details al in white background.
 
  1. The API Product click through for Biotic Risk Geography here is missing the relevant API Product details (in this case, pest names that would be useful to see at a glance for possible users) that in other APIs are spelled out as part of the API Product headings. Note sure how best to do this. One suggestion is to keep the generic information in the immediate following
 
 
 
and then somehow associate each of the “Source Details” to their respective pest details taken from the column C details listed here.  Perhaps above each of the source details you could have a line that says
 
API Products: Common Name followed in brackets by the Scientific Name of each of the relevant pests that is linked to each of the specific sources (where the pest names are taken from the column C details listed here.)   
 
As it is now there is no association between the specific product (pest layer) and it’s respective source. Each of the API Products: Common Name followed in brackets by the Scientific Name headings could be embedded in grey with the source details in white to give the same look and feel to the other entries as proposed above.
 
But there may well be other options to better reveal a) what pests we have included in this API product ,and b) what source is associated with what pest.
 
Cheers,
Notified 2 people
Robyn rescheduled this to-do
Was
Now
Notified 1 person
Ian Parsons, Head Chef at Matogen Digital
Ian Parsons completed this to-do.