Harvard University
Harvard University
Harvard University
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/d7cc6602-7f2c-4d41-9803-8a1f3a0fcee9%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/4eda0122-3cbd-4512-b850-60efb1cad86e%40googlegroups.com.
Hi Sherry,
I saw the issue in my local environment because I don’t drop my database as often as Phil does. The adding of parens to facets is not happening in the just released version 4.8. In order to completely fix the view of the facets you’ll need to upgrade to 4.8, drop your indexes and re-index.
If that’s a satisfactory solution please let us know.
Thanks
Steve
On Sep 26, 2017, at 3:04 PM, Sherry Lake <shla...@gmail.com> wrote:
Phil,
I haven't opened a github issue yet, but will. I tried to replicate this on phoenix, but the affiliation looks okay there.
Here's an observation of what we are seeing with a search on Harvard, go to this URL on Harvard:
Notice in the public search results display, datasets created since Aug 7th have parens around author affiliation AND contact affiliation.Datasets (in this list) created on Mar 19, 2017 and earlier do not have parens.
UVa just deployed 4.7.1 this week, so the bug was not introduced with that version. UVa went form 4.6.1 to 4.7.1 last week (up to 4.7 and then 4.7.1 yesterday). We were seeing the parens since I think 4.6.1.
--Sherry
On Tuesday, September 26, 2017 at 9:40:19 AM UTC-4, Philip Durbin wrote:I'm pretty sure this is a bug that was introduced* in Dataverse 4.7.1. Is the pattern that only datasets created since your deployed 4.7.1 are affected?
Nick or Sherry, can you please open a GitHub issue about this? I'm actually having trouble reproducing the bug on the latest code in the "develop" branch so if you can include the steps in the GitHub issue, it would be most appreciated. I doubt is was magically fixed in the latest code. I probably just don't know how to trigger the bug.
Thanks!
Phil* Perhaps the change from dsfv.getValue() to dsfv.getDisplayValue() in https://github.com/IQSS/dataverse/pull/3973 but I'm really not sure.
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/c53de90f-94ca-4284-999b-887c28c14290%40googlegroups.com.