-
Notifications
You must be signed in to change notification settings - Fork 4
Refactor from EDS profiles to EDS Facets #78
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
Conversation
|
Coverage remained the same at 100.0% when pulling a26f2b1831617bb1d7159db5f922ecf997813322 on di136_facetize into 4ff7499 on master. |
|
Coverage remained the same at 100.0% when pulling a26f2b1831617bb1d7159db5f922ecf997813322 on di136_facetize into 4ff7499 on master. |
|
Coverage remained the same at 100.0% when pulling e2bada5fc90a7a9b034430671fe6fb8d548b3a70 on di136_facetize into 4ff7499 on master. |
e2bada5 to
26c2a5e
Compare
|
Coverage remained the same at 100.0% when pulling 26c2a5e01c56ded06f72e26ee9b67ae288b2607a on di136_facetize into 4ff7499 on master. |
frrrances
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
What: * Moves from multiple EDS Admin configured profiles to a faceted approach that uses the source facet to segregate content into appropriate boxes Why: * EDS profiles would never allow us to create the boxes we were asked to create because we were basing the boxes on format of the material and profiles can't be created effective that way. * https://mitlibraries.atlassian.net/browse/DI-136 How: * Facets for the (currently 3) boxes are configured via the ENV settings. EDS_ARTICLE_FACETS, EDS_BOOK_FACETS, EDS_WHATNOT_FACETS Note: * The link to more like this is temporarily disabled as we look into how to deep link into pre-faceted result sets in EDS UI. That issue is tracked via https://mitlibraries.atlassian.net/browse/DI-143
26c2a5e to
8661217
Compare
What:
approach that uses the source facet to segregate content into
appropriate boxes
Why:
to create because we were basing the boxes on format of the material
and profiles can't be created effective that way.
How:
EDS_ARTICLE_FACETS, EDS_BOOK_FACETS, EDS_WHATNOT_FACETS
Note:
deep link into pre-faceted result sets in EDS UI. That issue is tracked
via https://mitlibraries.atlassian.net/browse/DI-143