saeid-p
commented
8 years ago In order to expand sorting to Author, Date Published, Repository, and Title, we need to have these fields in the mapping of all repositories in ElasticSearch. Currently, some of these fields are missing in some repositories and in some cases (Date Published), there is no consistency in the naming of the field. For instance, the publication date has been stored with different names in different repositories. The following are few instances:
- "releaseDate" in "arrayexpress_020916"
- "dateReleased" in "dataverse_022916"
- "dateAvailable" in "dryad_022916"
Generally, in order to utilize ElasticSearch sorting functionality, we need to have a consistent field for each of these fields, with consistent naming and model in the index mapping. If repository doesn't provide the field, it can be stored without value, but the mapping of the field should be exist in all repositories.
One workaround to fix this issue is to re-sort the results after running the search. This approach has been explained here. However, this solution will impact the performance of the search and increases application response time.
@jgrethe what's your opinion about this issue?
jgrethe
yul129
RuilingLiu
This feedback has been collected from survey feedback questionnaire form. In order to protect user's privacy, the personal information has been removed.
Sorting should be expanded to author, by date published, repository, title and we should be able to select the number of results I want to see per page. Additionally, export functions to citation managers is a good feature to have.