Custom Query (2152 matches)
Results (763 - 765 of 2152)
Ticket
|
Resolution
|
Summary
|
Owner
|
Reporter
|
#1602 |
fixed
|
[super] Data Previewer / Viewer v2
|
rgrp
|
rgrp
|
Reported by rgrp,
2 years ago.
|
Description |
We already have first pass of Data Preview that was done as part of #1357. This is about v2 of this. Two main components:
- A new version of the separate Data Explorer library (now called Recline Data Explorer) - #1446 Est: 10-15d
- Why:
- Cleaner, backbone based solution.
- Provides editing support if wanted.
- Collaboration with Max Ogden
- Integrate this into CKAN (into resource view page) - see #1630 Est: 1d
- Improvements to Data Viewer / Previewer system in CKAN itself - Est: 2-3d
(Update Data Preview-er (View-er) to support images ...)
(WONTFIX here - (?) Update Data Preview-er to support geodata - #1151)
|
#1603 |
duplicate
|
Search query builder
|
zephod
|
rgrp
|
Reported by rgrp,
2 years ago.
|
Description |
Super ticket: #1745
Ability to build up search query using a nice javascript-y interface.
- Add facets by selecting attribute and adding -> search facet options in dropdown -> added to search (with 'x' to remove -- as we currently do).
- (a bit like the data.hri.fi)
- Some improvements to css
- Improvements to faceting
- Ability to configure faceting and number of items to show (?)
- Pure JS search implementation to make it easy to reuse across site
|
#1605 |
fixed
|
[super] Multilingual support in CKAN
|
kindly
|
rgrp
|
Reported by rgrp,
2 years ago.
|
Description |
Multi-language:
- dataset and resource metadata (and other objects such as groups?)
- Field values in taxonomy (e.g. country names - Eurovoc)
- #1665 Research into Eurovoc
- Display Taxonomy in different languages
- Field values not in taxonomy (e.g. title & description)
- Use extra fields e.g. _i18n_title_fr = Le data.
- (If lots of fields would need translating then would consider having a new package for each language, linked together with PackageRelationships?. But I think it is just title and description (resource description etc. are so minor, not worth translating?), so using extra field better.)
- EC extension (templates, form)
- Currently the pot file is just for CKAN core. New pot file for CKAN core and this extension? Or separate ones for extensions?
|
Note: See
TracQuery
for help on using queries.