This task is focused on providing a "search box" on administrative listings. This preferably done by a module. Its been a huge miss for the past few years, the inability to search pages like admin/content. The student has to have sufficient knowledge of core search, contrib and ability to abstract this into making it work on many listings.
Example search listings:
admin/content
admin/content/comment
admin/people
Visual example

Addition: Filter
Additionally given the complexity of the challenge to the student, the scope could be extended to include filtering of pages - which never made it into Drupal 7 - but very handy nonetheless. This means filtering as shown in permission page filter movie. This could be done as an extra module, or included as a package.
Example filter listings:
admin/structure/block
admin/structure/types
admin/structure/menu
admin/structure/taxonomy
admin/structure/taxonomy/x
admin/people/permissions
admin/modules
admin/config
Deliverable
A module that allows searching of content, people and comments.
(Possible) Filters of permissions/modules etc, abstracted to be applied in many places.
Resources
#497804: [meta] Search entities (nodes, terms, etc.) within the administrative interface
#102254: Add an administrative search feature
#396478: Searchable modules page
#229193: Incremental filter for permissions page
Primary Contact
The primary contact would be Bojhan, but additionally this task could require a development mentor due to the complexity.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | search-drupal-keywords.png | 108.32 KB | Bojhan |
Comments
Comment #1
Bojhan commentedComment #2
drummBojhan asked me to look at his in IRC. Implementation-wise this is almost two tasks, filters requiring AJAX and not.
I've done a few without AJAX, things to keep in mind are:
- Keeping searchable information in a JS variable is probably faster than scanning the DOM.
- There are speed differences between jQuery .hide(), and toggling classes.
- If filtering happens as typing happens, watch out for slowdowns with small search strings.
Overall, seems like a good idea. How does the UI need to be different for AJAX vs. non-AJAX implementations?
Comment #3
dmitrig01 commentedBojhan is mentor
Comment #4
ksenzeeAm happy to be a code mentor on this project along with Bojhan.
Comment #5
alex ua commentedMarking as RTBC...
Comment #6
cwgordon7 commentedSomeone has added this to the GCI site. Thanks!
Comment #7
Chudoantienchu commentedComment #8
wooody commentednice