Based on some feedback from @JoeCohen on #2160. Specific ideas include:
1) Improve navigation to the Field Slip Index page. One idea is to have a way to get a filtered list of field slips associated with a Project. In at least some cases, this will be somewhat redundant with the existing "Observations" tab, but it may still be enough different that it's worth it's own link.
2) Make the Field Slip index page table-like. Current it just leverages the show.html.erb. If the index page had the field slip code, the collector, the field slip id, and a link to any associated observation (with a thumbnail and current name if available) that would probably be sufficient. Any associated project might be interesting, but is largely implied by the field slip code. Maybe the page should have an autocompleter of projects with options for "All" and "Unassigned".
3) Index page should be sortable by at least one of the above columns.
4) Might consider filters per columns, but until there's some real data and we see how much this gets used it's probably overkill.
Based on some feedback from @JoeCohen on #2160. Specific ideas include:
1) Improve navigation to the Field Slip Index page. One idea is to have a way to get a filtered list of field slips associated with a Project. In at least some cases, this will be somewhat redundant with the existing "Observations" tab, but it may still be enough different that it's worth it's own link.
2) Make the Field Slip index page table-like. Current it just leverages the show.html.erb. If the index page had the field slip code, the collector, the field slip id, and a link to any associated observation (with a thumbnail and current name if available) that would probably be sufficient. Any associated project might be interesting, but is largely implied by the field slip code. Maybe the page should have an autocompleter of projects with options for "All" and "Unassigned".
3) Index page should be sortable by at least one of the above columns.
4) Might consider filters per columns, but until there's some real data and we see how much this gets used it's probably overkill.