I just found out that the Google Scholar Indexing Plugin was turned off in OMP. I could not remember why we had turned it off, but saw the reason right away when I turned it on again: All content in OMP went blank! All links led to blank pages, but when I turned it off again the problem was solved. Has anyone else experienced this? Has it been solved in version 3.4? We have not updated yet due to some technical issues, but are of course planning to do so.
Is there any chance that content from our OMP archive has been indexed in Google Scholar with this plugin turned off? What about Google Books? Much of the content in OMP are monographs.
Interesting. Would you mind noting your specific OMP version (e.g. 3.4.0-7)? Also, it would be advised to look at your PHP error logs for this to provide more clues about what is occurring.
“[04-Nov-2024 08:22:23 Europe/Oslo] PHP Fatal error: Uncaught TypeError: htmlspecialchars(): Argument #1 ($string) must be of type string, array given in D:\site\omp\plugins\generic\googleScholar\GoogleScholarPlugin.inc.php:87”
Currently we are using the repository (neliti.com) for archiving, and our books on this platform have been successfully indexed by Google: https://ebooks.borneonovelty.com/.
@asmecher My colleague was able to fix some code in OMP so that the screen doesn’t become blank any more, and now Google Scholar should also be able to find our content.
That being said, see message from @borneonoveltypublish. Are you really sure this has been fixed? Not just so that the system doesn’t break down, but so that Google Scholar actually harvest content from OMP? This is very important! The researcher we were in contact with were not impressed when finding out this didn’t work.
The Google Scholar indexing plugin causes OMP to present meta tags that Google Scholar can harvest the content. For example, on our testdrive installation, you can see the meta tags inside the <head> element:
If those are present, then the plugin is working. It’s up to Google Scholar to harvest and present the data; if that’s not happening, I’d suggest inquiring with them.
Thanks,
Alec Smecher
Public Knowledge Project Team
@asmecher I am the colleague John D mentions. We managed to fix the issue by borrowing code from the Google Scholar plugin from OJS version 3.3.0.17, and now the required meta tags are present in the html code.
We are still on version 3.3.0.11, but are planning on upgrading to version 3.4.0.7 soon.
