What steps does it take to reproduce the issue? The advanced search page is slow to load and becomes unresponsive at times. This appears to be due to loading of the ~8K language entries. (The edit metadata page is slowed by this as well, but not as much due to a different widget (I assume).
A relatively simple work-around is to change the language field
|
language Language A language that the Dataset's files is written in text 36 TRUE TRUE TRUE TRUE FALSE FALSE citation http://purl.org/dc/terms/language |
to have advancedSearchField=false.
It might also not be too hard to switch to using the same widget as for metadata ed
Presumably any more complete fix will wait for the SPA.
Which version of Dataverse are you using?
6.4, develop
Any related open or closed issues to this bug report?
#10762
Screenshots:
No matter the issue, screenshots are always welcome.
To add a screenshot, please use one of the following formats and/or methods described here:
Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?
Not sure. QDR is using the work-around for now. I'd be happy to submit a PR with that change in the citation block if the default should change.
What steps does it take to reproduce the issue? The advanced search page is slow to load and becomes unresponsive at times. This appears to be due to loading of the ~8K language entries. (The edit metadata page is slowed by this as well, but not as much due to a different widget (I assume).
A relatively simple work-around is to change the language field
dataverse/scripts/api/data/metadatablocks/citation.tsv
Line 40 in 3aea148
to have advancedSearchField=false.
It might also not be too hard to switch to using the same widget as for metadata ed
Presumably any more complete fix will wait for the SPA.
When does this issue occur?
Which page(s) does it occurs on?
https://demo.dataverse.org/dataverse/demo/search
What happens?
To whom does it occur (all users, curators, superusers)?
What did you expect to happen?
Which version of Dataverse are you using?
Any related open or closed issues to this bug report?
#10762
Screenshots:
No matter the issue, screenshots are always welcome.
To add a screenshot, please use one of the following formats and/or methods described here:
Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?
Not sure. QDR is using the work-around for now. I'd be happy to submit a PR with that change in the citation block if the default should change.