Page History
...
Alphabetic jump to (specific letter) in results listing
- Service
- Effort: 24h
To do
construct the Rest URL based on the params
parse the response
ensure everything gets cached properly
build remotedata objects for results
write tests
- StartsWithComponent
Effort: 16h
To do
- show letters as links
- show a startswith input
- handle the case for phone screens (too small to show the alphabet)
- call the service with the correct query
- links should work with js disabled
- component should be abstract enough to be used with any kind of list
- write tests
- Browse By Title Component
- Description
- has an alphabetic selector at the top
- shows an item list
- can be paged and sorted
- can be scoped by a community or collection
- can be filtered by a metadata field
- Effort: 8h
- To do:
- create the component
- configure the routes
- call the service with optional scope and metadatafield filters
- configure existing components for alphabetic filtering, object lists and pagination to work with the correct data
- write tests
- Description
- Browse By Metadata Field Component:
- Description
- has an alphabetic selector or a date selector at the top
- shows a list of metadata values
- can be paged and sorted
- links go to a browse by title view filtered by the scope and the metadatafield of this component
- Effort: 16h
- To do:
- create the component
- configure the routes
- configure existing components for alphabetic filtering, object lists and pagination to work with the correct data
- create a component to select by date
- reuse the search’s date widget?
- Create an object list entry for metadata values
- the metadatafield it works with should be configurable: title, author, subject, etc.
- this should reflect in the route e.g.
/collection/:id/browse/title
- and the i18n labels.
- It should work with or without a scope
- write tests
- Description
Build out Administrative Search/Browse tools (each of these tools is limited to Site Administrators)
...
Overview
Content Tools