10000 Enhance name lookup · Issue #508 · eprints/eprints · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Enhance name lookup #508

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.

Sign up for GitHub

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

Jump to bottom
Open
dennmuel opened this issue May 6, 2019 · 4 comments · May be fixed by #509
Open

Enhance name lookup #508

dennmuel opened this issue May 6, 2019 · 4 comments · May be fixed by #509

Comments

@dennmuel
Copy link
dennmuel commented May 6, 2019 •
edited
Loading

Hi everyone,

as a feature, it would be nice, if cgi/users/lookup/name would look through all kinds of contributors and not just the creators. This way, someone who has already published as an author, will also be found by the lookup when they contributed as an editor, reviewer, translator etc. - and vice versa.

Maybe there could even be an archive level configuration option to set the fields that should be used in that lookup.

Best regards
Dennis
@drn05r
Copy link
Contributor
drn05r commented May 10, 2019

Anyone can write their own cgi/users/lookup/X to use as an autocomplete for a field in the EPrint workflow. Commonly people write ones that lookup against the user table to ensure you get a consistent creators (or editors. etc.) ID. I will see if I can find any example that you could use as a guide to build your own. As long as you have a basic understanding of Perl you should not find it too difficult to adapt an existing lookup script.

@drn05r
Copy link
Contributor
drn05r commented May 10, 2019 •
edited
Loading

In fact there is something that I think is it close to what you might need:

https://wiki.eprints.org/w/Using_Internal_IDs_for_Staff_Browse_Views#Add_Autocompletion_for_creators.2Feditors.2Fcontributors_fields

Remember that you will need to edit your cfg/workflows/eprint/default.xml to specify the input_lookup_url for to point at this URL for this CGI script.

@dennmuel
Copy link
Author

Thanks for your answers, David.

What we're trying to achieve is to also take editors or any other contributors in account, not just creators, thus creating a big pool of persons that are looked up, regardless whether they were creators, editors, translators or whatever.

I guess the fun really starts in the SQL statement when trying to join the eprint_creators_* and eprint_editors_* tables. I was just wondering if someone has already done some work on that, so that we don't have to reinvent the wheel and if we do invent it, if this would be of interest to others.

dennmuel added a commit to dennmuel/eprints that referenced this issue May 15, 2019
@dennmuel
Add lookup over all contributors (issue eprints#508)
25e0c4b
@dennmuel dennmuel linked a pull request May 16, 2019 that will close this issue
Open
@dennmuel
Copy link
Author

Please see the linked PR as a suggestion for such a lookup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add lookup over all contributors dennmuel/eprints
2 participants
@drn05r @dennmuel
0