Hey Eoin,
thank you very much for your answer! I think I might have expressed myself misleadingly
1)
It is indeed true that GlobalSearch uses Solr succesfully to find Glossary entries. But for doing so the User needs to use "Global Search" and NOT the "Glossary search" field in the Glossary-activity. This can be very confusing since the position of the Glossary-Search right under the Title suggests that this is the field to use if you want to search the Glossary....
To make myself clear i made a screenshot:
Is there any way to replace the glossary-search (red) with the global-search function (green) ?
Or can I at least somehow hide the misleading and irritating glossary-search-field so that the user goes the "correct" path and uses the global search field instead?
2)
Unfortunately my usecase requires to "link" the documents from nextcloud and not attach it. The reason is that I want to link a huge chunk of documents to many different glossaries and in case one of the documents gets updated in the repository (nextcloud) all "linked" documents (that means all glossary-linked-documents) should be updated immediately. So I would somehow need the Repository Plugin to index the "linked" documents as well.
Since my non-profit association is now just starting to implement Moodle I wonder if these urgend-needed funcitonalities described above are "very hard" or "impossible" to realize from a developers perspective? Since you Eoin are a Plugin-developer-yourself: what do you think? Can i forget it? Might there be any chance to get these "features" into the global Moodle-Development-Pipeline? Or might it be worth to look for a developer to let them be individually developed for our needs? Maybe I could organize some money for that purpose but I would need a raw notion of how elaborate and costly the development of such features might become?
Thank you for your help!
kind regards
Philipp