Allow accessible values (keyword) for common content search crieteria
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
User Story
It would really help simplify our content searching if we could use more accessible values when searching for content. For example:
+languageId:es
or
+baseType:pages
or
moduser:will@dotcms.com
or
+conFolder:/about-us
or
+conHost:demo.dotcms.com
I think we can do this with backwards compatibility by using es's keyword mappings in these fields and providing multiple values to index.
Acceptance Criteria
These should work and not break existing implementations.
Proposed Objective
Technical User Experience
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by mapping the existing content-search criteria and keyword/index mappings, then identify compatibility coverage for languageId, baseType, moduser, conFolder, and conHost. Done means the accessible values work while existing search implementations continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100