Broad issues

Suggestion	1. All info should be on one page with no requirement to scroll down to see all the home page.
Action	Split into 1024x768 pages (though issue with default font), and supply easy page navigation e.g. like Ben's. Minimal acceptable change a high priority.
Priority	H
SAPAC	Existing code can read in HTML header and footer files and handle new CSS for look and feel. But modifying screen layout will require some work and a web interface that is agreed by HISCOM. Having simple navigation and fitting into a single page will be difficult. Current AVH2 interface uses a table to fit all input information onto one page. Ben's proposed interface is simpler to navigate but requires scrolling.
Discussion	I disagree with this one, most web users understand how to scroll a page. Benr 15:01, 16 May 2008 (EST)

Suggestion	2. The links found on other pages (Home, Simple Query, Logon, Registration, Background, Participants & Copyright) should be added to the home page
Action	We want public to access AVH2 uncluttered with restricted access. We have talked before on HISCOM on having 2 URLs, the public getting a clean minimal look, general restricted access users getting data released by herbaria for their use on AVH2 (note AD has a "Release to AVH2" flag" which we use!). This might avoid FOI cases.
Priority	H
SAPAC	Need HISCOM to provide sample HTML specifying what they want.
Discussion	KW&GC: what does the comment in parentheses really mean?

Suggestion	3. The link, on the title, on the home page, links to a page ( http://www.chah.gov.au/avh/) that can only be accessed from the home page. NO other links were found to get to this page
Action	Add in link on other pages?
Priority	H
Discussion

Suggestion	4. The link, on title, on the page http://www.chah.gov.au/avh/ links to a different page: http://www.chah.gov.au/avh/avh.html. Standardise what the title on the page links to?
Action	Standardise
Priority	H
Discussion	KW: didn't we go through all of these in Darwin last year and send the list to the webmaster?

Suggestion	5. Not all the hyper links over the logo work!
Action	add new hyper link
Priority	H
SAPAC	Easy to fix if requirements (what logo, whay hyperlink) are specified.
Discussion

Suggestion	6. None of the function or boxes on the "Extended Data Search Interface" on "Page 5 (of 5)Herbarium curation data" returns any results. There are no column for any of these on the results page
Action	fix
Priority	M
SAPAC	In the final report on AVH it was pointed out that no mapping of these fields to AVH was provided for more than a year after the project was mean to be complete, and no data for these fields was provided until ~ 2 years after the project was meant to be completed. Only Adelaide currently provides this data. I suggested that this page be removed until most or all herbaria actually provide the data.
Discussion	KW&GC: Are these all useful query fields on this page?? And a general question: why are these called 'pages'? Is there a more intuitive word we could use for users? And can we change 'Output' on button to 'Search'? That is the term that users are used to clicking on for a query (in the MS world at least, and isn't that most of the world?!?

Suggestion	7. The results displayed on the "query results page" or "csv page" form an "Extended Data Search Interface' should be grouped by the pages they are found on, Example: all boxes found on "page 1 (of 5)Plant Name Data" will be grouped together on the query results page, and are displayed same order on the query results page as they appear on "Page 1 (of 5)Plant Name Data". Could these be subtly colour coded the help the user?
Action	fix
Priority	M
SAPAC	Easy to fix - it's in a config file.
Discussion	KW&GC: Querying on 'Replicates to' doesn't result in making it clear whether the displayed specimens are in their original herbarium or have been donated to another herbarium. For example, we searched on 'Cyperus semifertilis' collected in state of 'NSW' and dups sent to 'HO, PERTH'. All that were returned from that query were the original specs in hb NSW but it wasn't made clear to the user that there were no dups in HO or PERTH. This is another field that needs a Help Balloon/pop-up.

Suggestion	8. Simple input field validation should be performed before beginning the search, with appropriate message ("You have not filled in fields [ ]". Species without genus should not activate query etc.
Action	fix
Priority	H
SAPAC	HISCOM would need to provide clear specifications on any validation rules that are not simple type checking.
Discussion

Suggestion	9. Add support for auto wildcarding of left parts of dates and geocodes not specified, including date range queries.
Action	fix
Priority	H
SAPAC	Bug fix
Discussion

Suggestion	10.There are many examples where a help page would be useful, e.g. wildcarding, vagiaries of data (reasons why people's names aren't standardised; absences of data; variable accuracy and how to deal with this in queries and use of data). Also or on separate page, progress with the overall AVH (News) - e.g. lack of in validating our data, vision for future developments. Rex: a PayPal button for donations..
Action	Provide Help Page
Priority	M
SAPAC	Currently have some explanatory words on the pages - could add to this or have link to help page or documentation
Discussion	KW&GC: (Wishful thinking, Rex!) How about a pop-up balloon for each term rather than a page that covers all of them? That is easier for a user, in our view.

Suggestion	11. Consistency of field names in prompts and outputs is essential. Don't use ABCD concept names like unitID, but clear descriptors.
Action	fix
Priority	H
SAPAC	Need HISCOM to specify what names they want used. Current names are based mostly on the template that was provided to us.
Discussion

Suggestion	12. FIX HTML-output: There are no borders around some of the output boxes in the HTML table, eg. "Other collecters" boxes (Rex suggests add )
Action	fix
Priority	H
SAPAC	Bug fix
Discussion

Suggestion	13. Geocodes outputs should be accurate in restricted area. But should limit to 5 decimal places (this allows for accuracies to 1 m)
Action
Priority	H
SAPAC	Easy to fix
Discussion	KW&GC: This number of decimal places seems overkill for many of our existing records (maybe future specimens will have better geocode data with them). ??Can this number of dec. places be limited for records with less precise geocodes, to avoid false accuracy?

Suggestion	14. I would continue to argue that as most of us store our data in dms we should deliver and merge our data as dms. We can provide an optional output in dec. degrees, as we might do in our local herbarium, but this of course is not at all necessary - GIS users As a herbarium user I want it in DMS! Why do we develop a cringe here of herbaria conforming with GIS user needs!
Action
Priority	M
SAPAC	Easy to add if required. However note that ABCD only supports DMS as a string in a single field.
Discussion	KW&GC: So is there a problem allowing for both outputs, and the user then selects which they want (decimal or dms)?

Suggestion	What does %M% % remarkable% produce in the "Nearest named place" and "Locality text" boxes on page "Page 2 (of 5) Geographical search and delivery "?
Action	Should use %M%remarkable%
Priority	M
Discussion

Suggestion	Can you use AND / OR in the "Nearest named place" and "Locality text" boxes on page "Page 2 (of 5) Geographical search and delivery "?
Action	No. No Boolean key word searching available anywhere in AVH2.
Priority	M
Discussion