Auto-completion based on existing database values for the field Keyword.

[alejandratenorio]

Users in CIMMYT need to create a suggested vocabulary list to use them in auto-completion values for the field Keyword.
The community has proposed to add a similary functionality to metadata such as Authors or keywords using a lookup that would unfold in a button within the template, as exposed in #4772, unfortunately, we don't know the current state of this development.

Our list of requirements is as follows:

1. The autocomplete must automatically fill in the fields of:

• Term
• b. Vocabulary
• c. Vocabulary URL

2. Each term can have a main language and translations.
3. As administrators, we must manage the controlled vocabularies,

• a. Add new vocabularies to Dataverse using an easy-to-structure CSV file.
• b. Edit and delete vocabularies.
• c. List the controlled vocabularies
• d. Allow editing a vocabulary: add, edit and delete terms and translates
• e. Use of a controlled vocabulary from a Global Dataverse to a Sub-Dataverse

We have developed 60% of the requirements; however, the goal of CIMMYT is to contribute with this new module. We would like to share with you the design, tables and UI for feedback.
The following are some of the UIs we have
For example,

List of controlled vocabularies of a Dataverse

Add new vocabulary

Confirm before creating a vocabulary from a CSV file

Manage a previously created vocabulary

Editing a term

Create a new term

[jggautier]

Hi @alejandratenorio! Thanks for sharing! You wrote that:

The community has proposed to add a similary functionality to metadata such as Authors or keywords using a lookup that would unfold in a button within the template, as exposed in #4772, unfortunately, we don't know the current state of this development.

About the status of these similar developments, I just wanted to mention that #4772 is part of this larger github issue (larger in scope). In #6030 the thinking, I think, is to consider an approach that takes as many of these use cases and the approaches that teams have proposed and even developed, like yours, into account before changes to the core code are tested and made. This hasn't been done, yet. Just trying to help answer your question about the status of addressing these issues. :)

[alejandratenorio]

Hi @jggautier,

I understand, if we want to craft a code contribution for this issue, we should send you a proposal to resolve the #6030

[alejandratenorio]

@jggautier, For your comments, could we show you our prototype?
We would like to develop the global solution but i'm aware that this needs to be discussed

[jggautier]

Yes, I think we'd love to see the prototype. It'll really help move solutions forward. (And thanks for the screenshots!)

Could we get back to you next week? I think what we want to do is exactly what you've been doing by contacting people who are already working on aspects of this issue: Trying to collaborate with everyone who shares similar needs, and might have already forked Dataverse to solve those needs.

[alejandratenorio]

@jggautier,

Sure, we can show you the prototype, it's the same that @scolapasta saw. We'd be happy if you give us feedback and tell us the way to go on.

[pdurbin]

@alejandratenorio we have the ability to spin up arbitrary branches from forks of Dataverse if you'd like us to try that. The script we use is documented at http://guides.dataverse.org/en/4.16/developers/deployment.html#download-and-run-the-create-instance-script

[alejandratenorio]

@alejandratenorio we have the ability to spin up arbitrary branches from forks of Dataverse if you'd like us to try that. The script we use is documented at http://guides.dataverse.org/en/4.16/developers/deployment.html#download-and-run-the-create-instance-script

Hi @pdurbin,

Gerardo did the deploy,
http://ec2-34-235-131-178.compute-1.amazonaws.com:8080
dataverseAdmin
admin1

[pdurbin]

@alejandratenorio fantastic! When I look at http://ec2-34-235-131-178.compute-1.amazonaws.com/api/info/version I see dataverse-4.13-18cbbe6 and it looks like you're building from https://github.com/CIMMYT/Research-Data-Repository/commit/18cbbe6 . The odd thing about that repo is that it only has two commits, but I'll worry about that later. 😄

The password works fine but I didn't play with the feature or get any screenshots (I'm about to leave for the day) but @jggautier @TaniaSchlatter @mheppler @djbrooke @scolapasta or others might be interesting in playing around with the feature to get a better understanding of how it works. Thanks! 🎉

[djbrooke]

Hi @alejandratenorio, I got a chance to review this with @jggautier @scolapasta @TaniaSchlatter and @pdurbin earlier today. Thanks again for setting up the AWS instance for us.

I have some concerns about building a UI for the administration of this suggestion feature. While the UI that you've worked on so far may work for CIMMYT users, I'm concerned about the scalability of this interface for others that want to allow suggestions for metadata fields while users are adding or editing datasets. I think the better option would be to have the field suggestions managed through an API.

Generally, what we're thinking is:

• Add table(s) to the application that can be populated with suggestions for metadata fields/compound fields
• Add an API endpoint that can be used to populate those tables for the root dataverse or a specific dataverse (and possibly the sub-dataverses). We'd need to work with you on determining the format and @jggautier will have some ideas.
• Use our autocomplete component from Primefaces (@scolapasta can you point to this?) to provide suggestions based on what's in the table

There are still some details to be figured out and we're happy to discuss this with you. If managing the suggestions through a UI is a requirement, could we discuss building an external tool that uses the APIs to update the application?

Comments welcome!