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

What fields should be facets? #15

Closed
ruebot opened this Issue Aug 18, 2017 · 6 comments

Comments

Projects
None yet
3 participants
@ruebot
Member

ruebot commented Aug 18, 2017

Current fields are:

  • General Content Type
  • Crawl Year
  • Public Suffix
  • Domain
  • Links Domain
  • Institution
  • Collection Name
  • Collection Number

Example
screenshot from 2017-08-18 11-31-05
screenshot from 2017-08-18 11-31-24
screenshot from 2017-08-18 11-31-44

These are the potential fields.

@ianmilligan1 @anjackson @greebie

Feel free to tag others.

@ruebot ruebot added the question label Aug 18, 2017

@ianmilligan1

This comment has been minimized.

Show comment
Hide comment
@ianmilligan1

ianmilligan1 Aug 18, 2017

Member

Probably add crawl_year as well?

Member

ianmilligan1 commented Aug 18, 2017

Probably add crawl_year as well?

@ianmilligan1

This comment has been minimized.

Show comment
Hide comment
@ianmilligan1

ianmilligan1 Aug 18, 2017

Member

Perhaps content_language – might be worth turning that on for a few test collections and seeing if it's useful or not.

Member

ianmilligan1 commented Aug 18, 2017

Perhaps content_language – might be worth turning that on for a few test collections and seeing if it's useful or not.

@ruebot

This comment has been minimized.

Show comment
Hide comment
@ruebot

ruebot Aug 18, 2017

Member

@ianmilligan1 crawl year is already there.

Member

ruebot commented Aug 18, 2017

@ianmilligan1 crawl year is already there.

@ianmilligan1

This comment has been minimized.

Show comment
Hide comment
@ianmilligan1

ianmilligan1 Aug 18, 2017

Member

There needs to be some sort of stupid face reaction.

Member

ianmilligan1 commented Aug 18, 2017

There needs to be some sort of stupid face reaction.

@anjackson

This comment has been minimized.

Show comment
Hide comment
@anjackson

anjackson Aug 21, 2017

I think content_language is a useful addition. FWIW, with Shine we attempted to start with a smaller facet set and allow users to add more facets if they wished. I'm not sure the implementation worked that well though.

Another way is to offer different views for different purposes. e.g. there are a lot of detailed format-oriented fields which are only of interest to a minority of users. They could be exposed via a separate controller specifically intended for folks interested in formats.

anjackson commented Aug 21, 2017

I think content_language is a useful addition. FWIW, with Shine we attempted to start with a smaller facet set and allow users to add more facets if they wished. I'm not sure the implementation worked that well though.

Another way is to offer different views for different purposes. e.g. there are a lot of detailed format-oriented fields which are only of interest to a minority of users. They could be exposed via a separate controller specifically intended for folks interested in formats.

ruebot added a commit that referenced this issue Sep 6, 2017

@ruebot

This comment has been minimized.

Show comment
Hide comment
@ruebot

ruebot Sep 12, 2017

Member

Resolved with a1a64ec.

Member

ruebot commented Sep 12, 2017

Resolved with a1a64ec.

@ruebot ruebot closed this Sep 12, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment