Develop Tag Plugin System: Enhance Subjects page by Integrating Tags #8279
Labels
Lead: @mekarpeles
Issues overseen by Mek (Staff: Program Lead) [managed]
Needs: Breakdown
This big issue needs a checklist or subissues to describe a breakdown of work. [managed]
Needs: Detail
Submitter needs to provide more detail for this issue to be assessed (see comments). [managed]
Priority: 2
Important, as time permits. [managed]
Theme: Book Tags
Issues related to community book tags
Theme: Subjects
Type: Epic
A feature or refactor that is big enough to require subissues. [managed]
Milestone
Once the basic ability to CRUD (create, read, update, delete) Tags has been achieved in #7766 and basic infrastructure is in place to connect/associate subject strings and Tags, the next step is to create a generic schema / DSL (domain specific language) for Tags that lets librarians define metadata to enhance how the subject page renders.
@JaydenTeoh has drafted/prototyped a plugins idea in #7928 that lets librarians associate Tags with any number of plugins (which are ostensibly macros or templates). #7928 is an amazing proof of concept, which achieves the goal of extending the capabilities of subject pages by defining a list of plugins which the subject page integrates. The concept is close but I think we may want to abstract as much of the implementation/code logic out of the Tag document and into the subject page (as a means of defining an implementation of the relationships specified within the Tag).
At minimum, we want to be able to (a) add more named carousels to Subject pages and (b) present patrons with a few librarian-chosen facets (
related_tags
orrelated_subjects
) -- similar to the search page -- that the patron can click on to narrow their search.This issue has 3 parts, all of which are prototyped by #7928:
primary_query
for the Tag/subject (by default / if not specified is justsubject:whatever-the-subject-is
)related_tags
a patron might click to drill down and further narrow what is shown by theprimary_query
Notes
The text was updated successfully, but these errors were encountered: