Open GoogleCodeExporter opened 9 years ago
Isnt this function covered in the biocache? In which case Im lowering the
priority.
If the users what to do in depth interrogation of the data: biocache, if they
want to model with species layers: SP. Thats how i rationalise the functional
breakdown.
Original comment by moyesyside
on 18 Jun 2014 at 4:26
If we expose the facets in the SP, they should be usable. I see very good
reason if we expose "Collector" then we are permitting someone to subset the
records on Collectors.
http://biocache.ala.org.au/occurrences/search?q=*:*#tab_mapView is no better.
Original comment by leebel...@gmail.com
on 18 Jun 2014 at 4:32
I thought there was a collector option in the advanced search for here:
http://biocache.ala.org.au/search#tab_advanceSearch
there is for AVH
http://avh.ala.org.au/search#tab_advanceSearch
so we'll add it here. Assigned to Nick
Regardless the "quick search" searches across the collector field, and so does
the search from the front page, so the functionality is covered in the Atlas.
Original comment by moyesyside
on 18 Jun 2014 at 4:48
Original issue reported on code.google.com by
leebel...@gmail.com
on 18 Jun 2014 at 4:13