#409
- Created on2013-04-19 13:54
- Reported by
- StatusClosed
- PriorityNormal (3)
- Assigned to
- Plan LevelSubtask
- Estimate0.0
- Due Date-
Managing MyEuropeana Saved Searches
As a developer I would like to manage MyEuropeana Saved Searches via the Europeana API. I would like the Europeana API to support the following operations:
1. Retrieving the list of names of Saved Searches stored on MyEuropeana account.
2. Running one of the Saved Searches stored on MyEuropeana account and getting the results.
3. Registering a search profile as a new Saved Search on MyEuropeana account.
4. Deleting a search from the list of Saved Searches stored on MyEuropeana account.
1. Retrieving the list of names of Saved Searches stored on MyEuropeana account.
2. Running one of the Saved Searches stored on MyEuropeana account and getting the results.
3. Registering a search profile as a new Saved Search on MyEuropeana account.
4. Deleting a search from the list of Saved Searches stored on MyEuropeana account.
Leave a comment
on 2013-06-18 11:50 *
By
1. Retrieving the list of names of Saved Searches stored on MyEuropeana account.
2. Running one of the Saved Searches stored on MyEuropeana account and getting the results.
At the moment, this function is returning the saved searches completely.
So there is no seperate function to run one search only based on the name...
2. Running one of the Saved Searches stored on MyEuropeana account and getting the results.
At the moment, this function is returning the saved searches completely.
So there is no seperate function to run one search only based on the name...
See #406 for introduction to testing this:
The api-demo application supports listing and deleting saved searches
The JSON url's are:
list: http://preview.europeana.eu/api//v2/user/savedsearch.json
list: http://preview.europeana.eu/api//v2/user/savedsearch.json?action=LIST
delete: http://preview.europeana.eu/api//v2/user/savedsearch.json?action=DELETE&searchid=? (where ? = the id of the saved search given by the list function)
create: http://preview.europeana.eu/api//v2/user/savedsearch.json?action=CREATE&query=?&qf=?&start=? (where the ? params are similar to seach params on portal)
The api-demo application supports listing and deleting saved searches
The JSON url's are:
list: http://preview.europeana.eu/api//v2/user/savedsearch.json
list: http://preview.europeana.eu/api//v2/user/savedsearch.json?action=LIST
delete: http://preview.europeana.eu/api//v2/user/savedsearch.json?action=DELETE&searchid=? (where ? = the id of the saved search given by the list function)
create: http://preview.europeana.eu/api//v2/user/savedsearch.json?action=CREATE&query=?&qf=?&start=? (where the ? params are similar to seach params on portal)
on 2013-07-23 20:01 *
By renekok
Assigned to changed from renekok to login
Status changed from Testable to To Do
@wjboogerd@eledge.net
List of saved searches works OK. Only the results are in random order. For me it would make more sense if it would be in order of ID.
Delete works. Only thing is that the resultcode it gives back is always true, regardless if it actual deletes something or not.
Only leaving the ID empty results in a success-code "false".
List of saved searches works OK. Only the results are in random order. For me it would make more sense if it would be in order of ID.
Delete works. Only thing is that the resultcode it gives back is always true, regardless if it actual deletes something or not.
Only leaving the ID empty results in a success-code "false".
As order of result sets are up to personal preferences, I not gonna change that.
Some want it on ID, some on date, some on order of the query....
Nothing really changed here...
Some want it on ID, some on date, some on order of the query....
Nothing really changed here...
on 2013-08-05 17:15 *
By renekok
Assigned to changed from renekok to Breandán Knowlton
Status changed from Testable to Acceptance
If nothing changed then I am through with my testing of this ticket.
The decision about sort order and the resultcode is up to the Product Owner.
The decision about sort order and the resultcode is up to the Product Owner.
on 2013-08-05 18:15 *
By renekok
Assigned to changed from Breandán Knowlton to login
Status changed from Acceptance to To Do
When trying to save/create a search you get a HTTP400 error and the search does not get saved:
http://preview.europeana.eu/api//v2/user/savedsearch.json?action=CREATE&fotograaf
http://preview.europeana.eu/api//v2/user/savedsearch.json?action=CREATE&fotograaf
on 2013-08-13 12:45 *
By renekok
Assigned to changed from renekok to Breandán Knowlton
Status changed from Testable to Acceptance
I must have been sleeping.
Mission succeeded:
http://preview.europeana.eu/api//v2/user/savedsearch.json?action=CREATE&query=fotograaf
{
apikey: "testing",
action: "/user/tag.search?action=CREATE",
success: true
}
@BreandanKnowlton: When saving a search in the Portal it is not possible to save the same search more than once. In the API there is no such check to prevent duplicates.
Is a similar check desired in the API?
Mission succeeded:
http://preview.europeana.eu/api//v2/user/savedsearch.json?action=CREATE&query=fotograaf
{
apikey: "testing",
action: "/user/tag.search?action=CREATE",
success: true
}
@BreandanKnowlton: When saving a search in the Portal it is not possible to save the same search more than once. In the API there is no such check to prevent duplicates.
Is a similar check desired in the API?
Noticed a generic My Europeana bug. I saved this search http://preview.europeana.eu/portal/search.html?query=DATA_PROVIDER%3a%22Ateneumin+taidemuseo%22&utm_source=featuredpartner&utm_medium=portal&utm_campaign=Featured%2Bpartner and it looks as if it saves OK but both when looking in the API and in My Europeana the link has not been properly saved.
At first I thought it could be because of the GA campaign code but I git the same error with this query http://preview.europeana.eu/portal/search.html?query=who%3a%22Kunisada%22&rows=24
At first I thought it could be because of the GA campaign code but I git the same error with this query http://preview.europeana.eu/portal/search.html?query=who%3a%22Kunisada%22&rows=24
on 2013-08-26 23:59 *
By
@DavidHaskiya
Concerning the first link:
savedsearch.json?action=CREATE&query=DATA_PROVIDER%3a%22Ateneumin+taidemuseo%22&utm_source=featuredpartner&utm_medium=portal&utm_campaign=Featured%2Bpartner
will result in params:
query: DATA_PROVIDER%3a%22Ateneumin+taidemuseo%22
utm_source: featuredpartner
utm_medium: portal
utm_campaign: Featured%2Bpartner
the last 3 are not supported params by the API and therefore ignored...
(In portal happens the same, the utm* params are only used by google analytics)
Concerning the first link:
savedsearch.json?action=CREATE&query=DATA_PROVIDER%3a%22Ateneumin+taidemuseo%22&utm_source=featuredpartner&utm_medium=portal&utm_campaign=Featured%2Bpartner
will result in params:
query: DATA_PROVIDER%3a%22Ateneumin+taidemuseo%22
utm_source: featuredpartner
utm_medium: portal
utm_campaign: Featured%2Bpartner
the last 3 are not supported params by the API and therefore ignored...
(In portal happens the same, the utm* params are only used by google analytics)
on 2013-08-27 00:12 *
By
Assigned to changed from login to Breandán Knowlton
Status changed from To Do to Acceptance
concerning the second link:
http://preview.europeana.eu/portal/search.html?query=who%3a%22Kunisada%22&rows=24
In the json output of the API is clearly visable that this link is stored and returned correctly.
API-DEMO is not encoding the url's when displaying. so this is not a issue related to this ticket, and it will consume a bit too much time to fix this in the demo app.
@DavidHaskiya, @renekok
Please remember the demo app is a simple far from perfect example implementation which is not part of the official API functionality.
I told you both how to test the JSON output of the API itself, my opinion is that's the part that should be tested, not the demo.
For these tickets the demo app is completely out of scope.
I put this ticket back to acceptance, as there is nothing changed to test.
http://preview.europeana.eu/portal/search.html?query=who%3a%22Kunisada%22&rows=24
In the json output of the API is clearly visable that this link is stored and returned correctly.
API-DEMO is not encoding the url's when displaying. so this is not a issue related to this ticket, and it will consume a bit too much time to fix this in the demo app.
@DavidHaskiya, @renekok
Please remember the demo app is a simple far from perfect example implementation which is not part of the official API functionality.
I told you both how to test the JSON output of the API itself, my opinion is that's the part that should be tested, not the demo.
For these tickets the demo app is completely out of scope.
I put this ticket back to acceptance, as there is nothing changed to test.
on 2013-08-27 10:58 *
By David Haskiya
Ok. I created a separate ticket for the My Europeana bug (it's not only in your client the searches fail after having been saved) concerning Saved searches.
on 2013-09-06 21:08 *
By Breandán Knowlton
Assigned to changed from Breandán Knowlton to David Haskiya
Was unable to test for the moment, as I can't log in with the api demo.
on 2013-10-06 19:04 *
By David Haskiya
Tested, OK.
on 2014-11-11 11:50 *
By bramlohman
Tag changed from deployment_29_10_2013 to deployment_29_10_2013
Type changed from Story to -none-