Advanced Search as a separate module (Currently part of Islandora Core)

49 views
Skip to first unread message

Kirsta Stapelfeldt

unread,
Dec 9, 2022, 7:02:23 AM12/9/22
to isla...@googlegroups.com

Dear Islandora,

 

As part of current efforts in the slack channel #starter-dev to configure the new Islandora Starter Site, I’d like to propose we include the abstracted Advanced-Search module, based on the existing sub-module in Islandora core . An issue about this from December 9 2021  is here:

 

https://github.com/Islandora/documentation/issues/2001 and the module with documentation is available here: https://github.com/digitalutsc/advanced_search/tree/contrib

 

We are using this module in production at UTSC. I believe that this is a good option as it is more theme agnostic. I also believe that since it is an abstraction of a module currently inside Islandora Core as a sub-module, it is in line with our hope to modularize existing Islandora code. We’d be happy to transfer it to Islandora-Labs (or the main Islandora organization on GitHub) if that’s a good solution.

 

Please weigh in with any thoughts on the relevant ticket and/or let us know your thoughts on #starter-dev

 

Thank you,

 

Kirsta (wearing a UTSC hat today)

 

Kirsta Stapelfeldt (How I pronounce it)

Book a chat

Head | Digital Scholarship Unit
UTSC Library 

 

UNIVERSITY OF TORONTO SCARBOROUGH

Library | AC 275 | 1265 Military Trail, Toronto, Ontario, M1C 1A4

Follow @UTSCLibrary on InstagramTwitter and Facebook.

 

Noah Smith

unread,
Dec 12, 2022, 9:57:36 AM12/12/22
to islandora
Having this be a separate module definitely makes sense to me... ~Noah

Rosie Le Faive

unread,
Dec 21, 2022, 3:25:57 PM12/21/22
to islandora
We discussed this today at the tech call.

There is general support of the idea, but we want to figure out the following:

* How are existing users of advanced_search going to migrate to the new version? Is there a way to port old config settings, as well as take care of all block placements (which may have complex conditions)?
* (Which kind of conflicts) can we introduce this module, and deprecate the submodule, gradually?
* Can we do the transfer in a way that the new git repo starts at the current islandora commit, and then the additions are merged in, like as a pull request? (Ensuring preservation of islandora history as well as any changes made since the module was forked).
Reply all
Reply to author
Forward
0 new messages