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

Avoiding hard coding of fields on advanced search page #137

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

Avoiding hard coding of fields on advanced search page #137

eaquigley opened this issue Jul 9, 2014 · 4 comments
Assignees
Labels
Type: Feature a feature request

Comments

@eaquigley
Copy link
Contributor


Author Name: Xiangqing Yang (@xyang02)
Original Redmine Issue: 3546, https://redmine.hmdc.harvard.edu/issues/3546
Original Date: 2014-02-12
Original Assignee: Kevin Condon


This request is from Phil.
Hi Xiangqing,

Gustavo and I just talked about how this might be something you could
help with, especially since you share an office with Stephen:

"Also, I'm hoping that I'll be able to pull the metadata for each
domain (astro, biomedical, etc.) programatically rather than hard
coding each domain's fields into the xhtml (hence all the FIXME's
about populating the fields). Ideally, when we add a new domain (i.e.
neuroscience) we won't have to touch the xhtml of the Advanced Search
Page. Ideally, the list of fields is retrievable programatically and
put in a JSF dataTable."

Right now we see...

  • Social Science Metadata (FIXME: populate with full list of fields)
  • Biomedical Metadata (FIXME: populate with full list of fields)
  • Astrophysics Metadata (FIXME: populate with full list of fields)

... at http://dvn-build.hmdc.harvard.edu/search/advanced.xhtml

Something to think about. :)

Cc'ing Gustavo and Stephen to keep them in the loop.

Phil

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Xiangqing Yang (@xyang02)
Original Date: 2014-02-12T21:29:22Z


Feature is added and the code has been checked in. Please test.

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Xiangqing Yang (@xyang02)
Original Date: 2014-02-13T15:47:20Z


The feature is implemented. But not all of the domain metadata are in the db yet. Phil suggested to test it until the data is all ready. So change the status back to dev.

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Gustavo Durand (@scolapasta)
Original Date: 2014-03-10T20:49:40Z


Passing back to QA. The advanced search page should now be working as data driven. You should see values where advanced search = true. To test, you can flip one in db and see that it either now shows (or does not show).

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Kevin Condon (@kcondon)
Original Date: 2014-03-12T23:32:33Z


Tested on 3/12

Yes, fields are dynamic/ data driven.

Closing ticket

@eaquigley eaquigley added this to the Dataverse 4.0: Beta 1 milestone Jul 9, 2014
qqmyers pushed a commit to GlobalDataverseCommunityConsortium/dataverse that referenced this issue Jan 14, 2022
…ulti-license

Fix error response/AdminITlicense tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature a feature request
Projects
None yet
Development

No branches or pull requests

2 participants