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

Admin interface to allow to set which Solr field maps to which drush option #10

Open
DiegoPino opened this issue Sep 22, 2016 · 7 comments

Comments

@DiegoPino
Copy link

Not all sites use _t suffix fields for datastreams, etc. So having the option to map which Solr field maps to which drush option would be excelent

@mjordan
Copy link
Collaborator

mjordan commented Sep 23, 2016

@DiegoPino since this module only offers a drush interface, how would you envision implementing this? Or would adding a GUI be a better option, so the mappings persist across uses of the CLI?

@DiegoPino
Copy link
Author

@mjordan i would love and admin form to set this, even when drush. Even without UI access, having a form that uses drupal vars to define what Solr field you want to use could allow you to set those drupal vars via drush. E.g drush vset islandora_datastream_crud_solr_dssource
And if you re ok, this issue will be accompanied by an pull request in the near future . My idea is to make use of Solr search result (any arbitrary) one via UI and pipe it through your supper handy drush processing (but used as ajax batch processing)+ also keep drush. I will do this in a local fork, then share if you happen to like it!

@mjordan
Copy link
Collaborator

mjordan commented Sep 23, 2016

if you re ok

Indeed I am! PRs welcome!

@DiegoPino
Copy link
Author

@mjordan so many moons. Was before https://github.com/mnylc/islandora_multi_importer. Is this still relevant for you? I know there is already a UI around for your crud. if relevant on #52 let me know and i can get you something tomorrow for sure. I mean, what are 24 hours more in this contex? 👍

@mjordan
Copy link
Collaborator

mjordan commented Mar 15, 2018

@DiegoPino thanks for the offer but I am wondering it a simple, optional mapping in a config file is sufficient? Don't go to any trouble if you no longer have a use for a field config GUI.

@DiegoPino
Copy link
Author

@mjordan ok, will give it a shot.

@mjordan
Copy link
Collaborator

mjordan commented Mar 15, 2018

Sorry, I can do the mapping file, I didn't mean to imply that you do it. You're off the hook!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants