this feature would allow sites using the api to prepopulate drop down lists indicating which sols have data available.
this feature should not be limited to 25 rows, as it would cause excessive traffic to your site with repeated requests to the api. Rather it would be preferrable to cache the resultset from the database to disk for a period of time (I would suggest 1 hour) and return the cached data instead of hitting your database.
not all sols have photos. In this api it would be useful to have an API that returns the list of valid sols for the mission eg
https://mars-photos.herokuapp.com/api/v1/rovers/curiosity/manifest
and be able to filter the list by instrument
https://mars-photos.herokuapp.com/api/v1/rovers/curiosity/manifest?camera=fhaz
this should return a full list of sols like that at http://mars.jpl.nasa.gov/msl-raw-images/image/image_manifest.json
ie (depending on instrument) { "sol": 0, "num_images": 3720, "last_updated": "2014-08-13T22:27:14Z" }, { "sol": 1, "num_images": 20, "last_updated": "2012-10-01T20:49:14Z" },
this feature would allow sites using the api to prepopulate drop down lists indicating which sols have data available.
this feature should not be limited to 25 rows, as it would cause excessive traffic to your site with repeated requests to the api. Rather it would be preferrable to cache the resultset from the database to disk for a period of time (I would suggest 1 hour) and return the cached data instead of hitting your database.