[to do] frontend updates to label empty "type" & empty "date" values

[christinklez]

This collection has 92 objects that have an empty "type" field:

• Collection landing page: https://calisphere-stage.cdlib.org/collections/6406/
• Collection landing page with the empty facet selected: https://calisphere-stage.cdlib.org/collections/6406/?q=&sort=a&type_ss=

This is a Nuxeo collection with 5 objects with an empty "type" field:

• Collection landing page: https://calisphere-stage.cdlib.org/collections/27116/
• Collection landing page with the empty facet selected: https://calisphere-stage.cdlib.org/collections/27116/?q=&sort=a&type_ss=

When you do a sitewide empty search, the frontend is still confused: https://calisphere-stage.cdlib.org/search/?q=

What are our options here?

Ideally, the records do continue to publish through to Calisphere, and perhaps:

• option 1: These records appear in the search results, but don't get listed on the "type" facets (which is how Calisphere currently handles in the frontend)
• option 2: These records assign an unknown type value? And instead of the blanks, they can be selected by type unknown
• other options?

[christinklez]

There are actually more records from a variety of collections with an empty type field. This link should get you to it: https://calisphere-stage.cdlib.org/search/?q=&sort=a&type_ss=

(Note that if you go here: https://calisphere-stage.cdlib.org/search/?q= -- the empty type will be visibly checked off, but the results will not reflect that.)

[christinklez]

Discussed that in the frontend, we could potentially update the javascript to display a custom label (something like unknown or not supplied). This would not touch the OpenSearch index.

[christinklez]

An FYI that we now have empty "date" values appearing in the facets: https://calisphere-stage.cdlib.org/search/?q=&sort=a

[amywieliczka]

Dev work on this is complete with #351 but I still need some proper language approvals.

[christinklez]

Thanks @amywieliczka! I see the new "date value not supplied" and "type value not supplied" labels--they both look great, and the functionality of the search/browse pages also look good.

@aturner--let's plan to touch base to discuss the labels. Thanks!

[christinklez]

Closing this work as done! The issue initially reported (frontend being confused by empty values) is resolved, and the dev work to prep to transform the blank values with labels looks good.

Opened a new issue to formalize the label, see #959.

Thanks!