Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advanced Search Page: include non dataset fields #330

Closed
eaquigley opened this issue Jul 9, 2014 · 9 comments
Closed

Advanced Search Page: include non dataset fields #330

eaquigley opened this issue Jul 9, 2014 · 9 comments
Assignees

Comments

@eaquigley
Copy link
Contributor


Author Name: Gustavo Durand (@scolapasta)
Original Redmine Issue: 3745, https://redmine.hmdc.harvard.edu/issues/3745
Original Date: 2014-03-20
Original Assignee: Kevin Condon


Right now the advanced search page only shows the datasetfields, and none of the dataverse or file level searches.

Advanced Search Behaviors:
-If a user puts a query in more than one object type, the query should be OR
-If a user only uses fields within in one object type, the query should be AND
-Users should be able to enter search terms into any number of fields (dataverse, dataset, or files sections) and get results that relate to those terms instead of advanced search only using one term entered in and ignoring all others.
-Users should be able to enter search terms into different sections (i.e.-one in dataverse, one in citation, one in social sciences & humanities, etc) and get results for any of those fields if there are relevant results to show

Things to look for during usability testing of Beta:
-Are users able to use advanced search to find specific content?
-Do users go more towards AND or OR advanced searching? (Currently in Beta, only AND works through the advanced search UI but can change to OR in the search query in the search box)


Related issue(s): #48, #390, #433, #530
Redmine related issue(s): 3455, 3805, 3848, 3945


@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Elizabeth Quigley (@eaquigley)
Original Date: 2014-04-07T19:29:36Z


Based off usability testing, I think we should have blocks for Dataverse, Dataset (which we already have), and Files so users easily can tell which section relates to each object. Additionally, the current blocks (Citation Metadata, Social Sciences & Humanities Metadata, Astrophysics Metadata, and Biomedical Metadata) should have Dataset added to the label so users know it is only for that object. I think this could ease confusion as to what fields relate to each object.

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-04-08T12:10:18Z


See also some discussion of the Advanced Search Page from yesterday: https://redmine.hmdc.harvard.edu/issues/3798#note-2

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-04-13T22:38:22Z


I'm aware that filetype searches are very strict right now (i.e. http://pdurbin.pagekite.me/?q=filetypemime_s:%22PNG%20Image%22) but I'll fix this (probably with a new schema.xml) as part of this ticket but highlighting works as of this commit:

6122b90 highlight on filetype #3737

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-04-13T22:52:16Z


I'm also aware that "dataverse affiliation" searches are very strict too (i.e. http://pdurbin.pagekite.me/?q=affiliation_ss:%22Trees%20Inc.%22 ) but I'll fix this in the same schema.xml change for filetypes I mentioned earlier in this ticket. Highlighting for "dataverse affiliation" fixed here:

5070b3c highlight on "dataverse affiliation" #3737

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-05-05T12:35:34Z


I made some progress on this last week:

stub out Dataverses and Files on Advanced Search #3745 · 81bae63 · IQSS/dataverse - 81bae63

By "stub out" I mean that the fields are there and work but I have not implemented the logic laid out in the description of this ticket. (I'll work on that next.) But if you search on name or description (for example) of a specific type, it should work.

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Gustavo Durand (@scolapasta)
Original Date: 2014-05-07T03:16:36Z


Fixed and cleaned up advanced search page.

Should be now working with the above logic.

@eaquigley eaquigley added this to the Dataverse 4.0: Beta 1 milestone Jul 9, 2014
@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-05-08T14:41:58Z


Stephen just pointed out to me that file descriptions were not searchable. I just committed a fix for this:

file descriptions were not searchable #3745 · 3b44dc2 · IQSS/dataverse - 3b44dc2

So testing search of file descriptions will require a new build and re-indexing of those files.

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-05-08T18:48:55Z


This may not be the right ticket to mention this but Gustavo and I just decided we'd like filetype_en to be searchable by basic search (not just advanced search). So you should be able to find the 50by1000.tab file by searching on words like "tabulardata" or "delimited". Here's how the field looks from the Solr perspective:

"filetype_en":[
  "Tab-Delimited",
  "tabulardata"
],

You'll need this latest schema.xml (and an index all) for this to work:

added filetype_en to catchall #3745 · 3981e65 · IQSS/dataverse - 3981e65

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Kevin Condon (@kcondon)
Original Date: 2014-05-16T21:54:53Z


Tested on 5/16 (and earlier)

All fields work, multiple terms,
OR between fields in an object type or block OR between terms in a field
All blocks work, all object types work
Searching finds results even if hits on each object/block.

Opened a minor ticket on var name/label.

Closing ticket

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants