CZOData / Search.CriticalZone.org

A repositiory for bug and issue tracking and for the http://search.criticalzone.org/ website.
BSD 2-Clause "Simplified" License
0 stars 0 forks source link

Help Tom make search.criticalzone.org more usable and appealing. #6

Open SRGDamia1 opened 8 years ago

SRGDamia1 commented 8 years ago

In order for visitors to find what they need and enjoy the experience, the site needs quite a bit more work on functionality and aesthetics

SRGDamia1 commented 8 years ago

Although it's nice to see such snappy search results and faceted navigation, we do have some ways to go before the site is usable and appealing. Some important functionality and content is inconsistent, confusing, or broken at the moment. You are probably aware of most of these issues, but it seems worth spelling them out so that we can prioritize, brainstorm solutions, and assign tasks to specific folks. For example, we need to explore ideas for better formatting of the Description/Abstract - adding returns, bolding, etc. And explore how easy it is to show different fields in the expanded/detailed views for a single record.

Some observations and initial ideas:

[--- Commented from Asana.com

commenter David Lubinski

---[aa]

SRGDamia1 commented 8 years ago

Oops, I'd meant to "at https://app.asana.com/0/15829753551253/15829753551253 " at the start of that last long comment. I'm sending another comment just to make sure Tom gets an email.

[--- Commented from Asana.com

commenter David Lubinski

---[aa]

SRGDamia1 commented 8 years ago

https://app.asana.com/0/15829753551253/15829753551253 , are you using git at all for search.criticalzone.org? If so, maybe I can peek around at the code and files (including angular, jeykll) ? Maybe make some changes for visual design myself?

[--- Commented from Asana.com

commenter David Lubinski

---[aa]

SRGDamia1 commented 8 years ago

As noted in an earlier comment for this task, it's worth trying out some longer-listed facets. They might just work with this interface after all.

One consideration is how well we can apply the facets to all records. Particularly tricky might be the non-CMS metadata, harvested or entered by other means at present.

We might want to try this list of options on the left rail: Search Keywords Map Locations (if we get it working ok) Observatories Disciplines Topics Field Areas Start/End Dates

TOPICS We should try Topics, especially because we already have a semi-controlled list of "Topics" and use them as a "Sort By" view in the CMS as well as dataset search results.

FIELD AREAS We should try Topics, especially because we already have a semi-controlled list of "Topics" and use them as a "Sort By" view in the CMS as well as dataset search results.

START AND END DATE YEAR As we talk about in the meeting on 11 Sept 2014, it would be helpful to be able to filter somehow by year, Start Date and/or End date. Maybe a way to select start and end years?


OTHER FACETS?


Additional facets require more consideration and adding them as new fields to the CMS datasets. They include:

VERTICAL EXTENT There is an ISO 19115 element for this. Maybe we could add max and min elevation fields to CMS datasets much like we do for field area?

SITE TYPE SiteType, which is a ODM2 CV that we are developing (includes sampling feature?) Landscape? Need a controlled list

SAMPLED MEDIUM Sampled Medium, which is a ODM2 CV that we are developing

DATA QUALITY Data Quality/Processing Level (raw, cleaned, gap-filled, smoothed, …)

CZEN SITE SEEKER CATEGORIES Currently they are optional attributes to CriticalZone.org “Field Areas” and would need to add them as attributes to Datasets: Lithology Soil type Biome Landuse

PRECIPITATION Approx mean annual precipitation mm/yr. this is an optional field for "field areas". We would need to add it as a new field/atttribute to Datasets.

TEMPERATURE Approx mean annual temperature C this is an optional field for "field areas". We would need to add it as a new field/atttribute to Datasets.

[--- Commented from Asana.com

commenter David Lubinski

---[aa]

SRGDamia1 commented 8 years ago

I'm moving this task to a lower priority, P2. The notes for this task capture a number of ideas, but they really are meant for a longer term followup project. These ideas need to combined with those of other folks, put into context and prioritized. For example, the one really clear need is to have a decent spatial, geographic based search. Which is ironic, given that this is a "geoportal". Further discussion can happen via github issues.

[--- Commented from Asana.com

commenter David Lubinski

---[aa]

SRGDamia1 commented 8 years ago

Actually, I'm moving it to even lower priority "possible future tasks"

[--- Commented from Asana.com

commenter David Lubinski

---[aa]

SRGDamia1 commented 8 years ago

@SRGDamia1 Hmmm... I'm a bit confused why this issue is listed under BiG-CZ and not CZOData. Seems like it should be in the latter, if not both?

[--- Commented from Asana.com

commenter David Lubinski

---[aa]