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

Request: ability to use remote and dynamic lists in properties such as author, contributor, producer, contributor #3622

Closed
edzale opened this issue Feb 3, 2017 · 6 comments
Labels
Feature: Metadata Type: Suggestion an idea User Role: Sysadmin Installs, upgrades, and configures the system, connects via ssh UX & UI: Design This issue needs input on the design of the UI and from the product owner

Comments

@edzale
Copy link

edzale commented Feb 3, 2017

I would like to use external data (for example data I get by querying my LDAP directory) to suggest authors and contributors names while leaving the possibility to the user to enter a name which is not from my list of suggestions. Same for producers and distributors. This is important to reduce typos and the time dedicated to the documentation of the datasets.
I must indicate that this request is related to a self-installed institutional instance of Dataverse.

@pdurbin
Copy link
Member

pdurbin commented Feb 3, 2017

@edzale it would be easier to implement autocomplete for authors that already have Dataverse accounts in your installation since they're right there in the database (in the authenticateduser table). Would that be of interest as a start? Or are you really only interested in LDAP for now?

@edzale
Copy link
Author

edzale commented Feb 15, 2017

Hi @pdurbin
Thank you for your answer. Your proposal sounds good. Is that something doable without forking the Dataverse project initial code? Do you know if some folks have implement this kind of autocomplete function before?

@pdurbin
Copy link
Member

pdurbin commented Feb 15, 2017

@edzale hi! Well, if you fork the code, we'd love to to get a pull request. 😄

There's some autocomplete code when assigning permissions. It looks like this:

public List<RoleAssignee> completeRoleAssignee( String query ) {
    return roleAssigneeService.filterRoleAssignees(query, dvObject, roleAssignSelectedRoleAssignees);                  
}

That's from https://github.com/IQSS/dataverse/blob/v4.6/src/main/java/edu/harvard/iq/dataverse/ManagePermissionsPage.java#L348 and called from https://github.com/IQSS/dataverse/blob/v4.6/src/main/webapp/roles-assign.xhtml#L28

The idea is that the query above is the thing you're typing and that's suggesting people.

I hope this helps!

@pdurbin pdurbin added Type: Suggestion an idea UX & UI: Design This issue needs input on the design of the UI and from the product owner labels Jun 23, 2017
@pdurbin pdurbin added the User Role: Sysadmin Installs, upgrades, and configures the system, connects via ssh label Jul 4, 2017
@pdurbin
Copy link
Member

pdurbin commented Nov 14, 2017

Related: #4282

@RightInTwo
Copy link
Contributor

RightInTwo commented Jun 22, 2018

Both options could be possible with the solution proposed in #4772.
A) Referencing dataverse users: Call the dataverse API
B) Referencing LDAP users: Call a custom API (that would have to be created and maintained outside dataverse) that queries the LDAP
C) ...another API that allows the identification of personen (ORCID and the likes)

@djbrooke
Copy link
Contributor

Closing in favor of #6030 to evaluate as part of a larger effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Metadata Type: Suggestion an idea User Role: Sysadmin Installs, upgrades, and configures the system, connects via ssh UX & UI: Design This issue needs input on the design of the UI and from the product owner
Projects
None yet
Development

No branches or pull requests

4 participants