Custom Query (2152 matches)
Results (1615 - 1617 of 2152)
Ticket
|
Resolution
|
Summary
|
Owner
|
Reporter
|
#1361 |
fixed
|
Simple search support
|
rgrp
|
rgrp
|
Reported by rgrp,
3 years ago.
|
Description |
Would be nice if CKAN could work out of the box without the need for SOLR (solr is great but complex and heavyweight to install).
Propose:
- ckan.simple_search config option
- If set:
- query via simple query to database backend
- do no specialized indexing
Remove
- TagSearchQuery? from lib/search (just do a search directly)?
- #1360: filter by downloadable and filter by open search options
(Probably future improvements)
- Re-introduce full-text search indexing where supported in e.g. postgres and use for querying
|
#1370 |
fixed
|
[super] Social sharing for datasets (and resources)
|
toby
|
rgrp
|
Reported by rgrp,
3 years ago.
|
Description |
Add a way to share datasets and see mentions of datasets on twitter (and elsewhere)
As a visitor I want to share a link to a dataset I have found. I also want to see how many others have shared this (or mentioned it).
- Sharing platform: simplest option is probably twitter but could generalize to e.g. sharethis system which supports, facebook, twitter etc etc.
- Will need a config option for relevant API key e.g. ckan.sharethis.apikey
- Location: Put this at top of sidebar on dataset view (a better suggsetion?)
- Should show how many mentions / shares there are. (very important!)
Discussion
- (Tom and Ira and ...): do we really want this, versus e.g. proper follow extension?
- What about bringing conversation back in to CKAN. E.g. show all times this dataset (i.e. its url) was mentioned on twitter. If we do this I think this should be definite +1.
- Also, given our users, I think just doing twitter (identica) may be sufficient (how many people want to share links to datasets on facebook?)
|
#1386 |
fixed
|
Disallow account creation via openid
|
rgrp
|
rgrp
|
Reported by rgrp,
3 years ago.
|
Description |
Superticket: #1343
Creation of accounts from OpenID causes large number of problems:
- No guarantee of other profile info
- Poor username (just from openid)
We therefore will:
- Require creation of user account via register (no auto-creation of accounts via openid)
- sidebar of register page should point to login page rather than openid signin
- Permit association of an openid with an account ...
- How: paste in your openid url (requires change to edit form to have this)
- won't work for google with their weird openid urls
- [future] Nicer way is to have login via openid while logged in (which association then happening in background)
- Migration (for 1+2):
- (?) Generate decent usernames for all existing accounts
- As this is nontrivial suggest instead we allow editing of usernames (by account owner and sysadmins). This is useful in its own right and is a reasonable 80/20 solution.
- This does present the problem of re-associating commits with the new username. Best solution to this would be to switch revisions to point to userid rather than username. See #1534
- [optional] Change display_name to always be username
- Change My Account to Username at top right of all pages (once we know
usernames are short ...)
- could do this straight away by truncating long usernames (e.g. truncate
at 20 chars ...)
- Also should we lose the icon?
|
Note: See
TracQuery
for help on using queries.