Click here for Wireframes - Search Results
We should add fields to the advanced search for "record modified by" and "modified date."
Design 1 shows what appears to be the option to choose multiple record types (check boxes). Since we are not yet supporting this, option 2 would be better (drop down). On the other hand, eventually we will support search across multiple record types, so design 1, if changed to radio buttons for now, could go back to multiple choice (check boxes) laterr.
On the other hand, overall I find design 2 easier to follow
Will we be able to add custom fields or extensions to the list of searchable fields on a record? For example, in the natural history collections, they will expect to see Scientific Taxonomy name or determination on the search. That field will in fact be in an official CollectionSpace schema, but what about ones that are added only for a specific tenant (e.g., NAGPRA code for PAHMA)? We do not need a UI to add fields to advanced search. It is OK if a programmer does it somewhere in the CollectionSpace stack.
We need to be able to compose advanced search strings using Boolean operators (including brackets) or a similar approach, not just in keyword searches, but also in field based searches. In principle all fields (whether CS Core or extensions) should be searchable across record types. And each field should be allowed to appear more than once in an extended search string.
Are the predefined fields in the Field-based Search determined by CollectionSpace, or could they be configured to the needs of each institution, or better yet each end-user?
Walkthrough with Mal Ahern, MMI
Powered by a free Atlassian Confluence Community License granted to LYRASIS. Evaluate Confluence today.