We should consider swapping out lcsh_suggest for questioning_authority. Although lcsh_suggest works, and works just fine for our purposes, I've been informed by @awead that it is no longer under active development, while questioning_authority is. Moreover, according to its description, questioning_authority can be used to "query any controlled vocabulary of set authority terms". This would allow us to break apart metadata_editor into a number of smaller services to manage the controlled vocabularies, instead of having a monolithic service to manage them all, as we are doing now.
As a side note, I had to tweak the output of lcsh_suggest a bit to get it to work with Select2. It looks like questioning_authority's output would require slightly less configuration to work with Select2.
We should consider swapping out lcsh_suggest for questioning_authority. Although lcsh_suggest works, and works just fine for our purposes, I've been informed by @awead that it is no longer under active development, while questioning_authority is. Moreover, according to its description, questioning_authority can be used to "query any controlled vocabulary of set authority terms". This would allow us to break apart metadata_editor into a number of smaller services to manage the controlled vocabularies, instead of having a monolithic service to manage them all, as we are doing now.
As a side note, I had to tweak the output of lcsh_suggest a bit to get it to work with Select2. It looks like questioning_authority's output would require slightly less configuration to work with Select2.