Promote 'Data Custodian' to top of data catalogue preview

[philipgrimmett]

Problem "Who is responsible for the quality and availability of this dataset?"

Exposing the chain of responsibility for federated data can be tricky. Casual visitors to the NationalMap frequently direct their data quality feedback to the data curator (NationalMap developers) rather than the data custodian, which is a missed opportunity (actionable, crowd-sourced QA for data custodians). It also means the map itself is perceived as the point of failure when a federated dataset is unavailable.

Proposed solution

• Promote data custodian metadata to the top of data catalogue previews, directly underneath the dataset title
• Include data custodian in feature info templates (position to be discussed)

Design reference:

[a-stacey]

Personally it feels a little backwards to have it before the description, but I do understand the use case and issues discussed.

I have made a commit for this, https://github.com/TerriaJS/terriajs/commit/6a3b16721c77457bbcdd16a0940402bb6c89992d.

The custodian appears first unless 'Disclaimer' is present (in which case that will take priority - if they are both metadataItem.info items - the code here is a little less then clean...) or a custom order has been specified for the catalog.

One issue identified is if the Data Custodian is long it seems less clean, example:

Happy to also look at adding to the feature info when you decide what should be done there @philipgrimmett.

[philipgrimmett]

@a-stacey (cc: @kring) good point re. longer data custodian entries. We might need to implement a generic 'show more' feature to improve scanability, maybe revealing only two lines by default?

[kring]

@meh9 since these long data custodian fields only show up in AREMI (AFAIK) could we perhaps just shorten them? We could add a longer "Data Custodian Details" in a later section if necessary with just a catalogue change.

[soyarsauce]

@philipgrimmett @kring so I've updated the PR @ https://github.com/TerriaJS/terriajs/pull/3022 including the suggested "Data Custodian Details" - are we happy to update the AREMI catalog through this addition section, or is a generic-show-more preferable, @philipgrimmett ? The additional section is more configurable, but adds extra metadata work for catalog items. It's feasible but we just have to chop off sentences in a haphazard-ey way.

Sample

[philipgrimmett]

@soyarsauce so the split would involve a human manually going through the AMEMI catalogue and pulling out custodian names from longer descriptions?

[soyarsauce]

@philipgrimmett Yes.

[philipgrimmett]

@soyarsauce in that case we might need to discuss in sprint planning. I still think it's worth doing, but I'm reluctant to commit to grunt work without getting team buy-in first (sorry!)