I am new to OJS, so please be kind if what I’m asking for may appear as obvious.
I am looking for a plugin that could allow me to upload a file in HTML only (instead of DOCX or JATS), and publish the html file as full text (below the abstract, embedded in the page).
Illustration :
I am asking your help after hours of seeking a solution through the World Wide Web & PKP forums.
What I tried :
Convert my HTML file to DOCX, then to JATS using docxConverter, then to full text HTML using JATSParser. The result weren’t good because the layout has been redefined, and I encountered some issues.
Install HTML Article Galley Plugin (did not succeeded to make it works)
Read the docs about embedGalley (from here), but I don’t have the PHP skills to transform this plugin from XML to embed to HTML to embed ;(.
I am pretty sure that a simple solution for that problem exist (a plugin maybe), but I didn’t found it yet.
If anyone have a solution to this, I’ll be more than happy !
I hope this allows for you to display the HTML in the way you are hoping, but please let me know if it does not, and there may be another answer or an opportunity to suggest a feature request.
I tried the embedHtmlArticleGalley that you mentionned in your post. However, it did not work. I installed the plugin, enabled it in the plugin gallery, and submitted a test article in HTML. In the production stage, I created an HTML galley for this file. However, once submitted, there is no inline HTML showing up…
There is not any hint during the submission/validation process that tells me that the plugin is working fine.
I also tried to use the inlineHtmlGalley plugin, which is pretty similar. I disabled embedHtmlArticleGalley before proceeding, but the result was the same :
No HTML and no hint that the plugin is working.
My linux server (a bridge-mode Ubuntu20Server virtual machine) apache log isn’t giving me any error, in both cases.
I may be missing a step, a button to click or a setting to turn on… Do you know any steps that I may have missed ?
Thanks a lot for your help ! Please forgive me if I skipped something that might appears obvious, I’m an absolute beginner in the OJS world !
In future version of OJS we hope to have the HTML or XML Content of an article captured directly as a property of the Article (per Issue #6279), and exposed to the UI and JATS metadata and other machine-accessible formats as well. So, please view this approach as a transition.
That said, the University of Pittsburgh is actively working on facilitating that transition by exposing the HTML Galley directly to the Article landing page, as the HTML/XML content property would eventually be exposed. We will be piloting this in the Goethe-Lexicon of Philosophical Concepts, first as a generic plugin (specific to the Bootstrap theme), and then as a Bootstrap subtheme.
All of this work depends on OJS recognizing the publication of the HTML Galley, and recognizing the generic plugin to display it. It seems something is still missing for you there. Did you install the embedHtmlGalley and inlineGalleyPlugins via the Plugin Gallery, or via the filesystem? I think the scenario you describe would happen if installed via the filesystem without running the upgrade.php or installPluginVersion.php script to register the plugin with the system.
I did take a look to your journal Goethe-Lexicon of Philosophical Concepts and it is really well designed, and nice to browse. You display the HTML as a separate page (when clicking on the HTML button) if I’m not mistaken. My goal is to display the HTML below the abstract, but I believe that embedHtmlGalley and inlineGalleyPlugins allows me to do that.
I believe having installed both plugins through the files system via git clone. However, I never interacted with any upgrade.php or installPluginVersion.php before (I’m new to OJS, so maybe I’m missing a thing).
I found on your GitHub page for inlineHtmlGalley the scripts that I may have missed. I will reinstall inlineHtmlGalley this way.
I also have a question : Is there any interface change or any specific behavior that I may expect ?
For example, JatsParser adds a “Full Text” section below the publication tab, and Texture adds a button below the XML files in order to edit them.
Does inlineHtmlGalley adds any button ?
We’ll be changing the layout of GLPC in the coming weeks; the plugin development for inlineHtmlGalley is still being wrapped up.
The inlineHtmlGalley plugin will reuse the existing HTML Galleys as uploaded, rather than presenting a new “Full Text” option in the UI. The new “Full Text” option is certainly the future direction, but the inlineHtmlGalley plugin is intended to be the bridge between the legacy use of the HTML Galleys, and the future usage of HTML/XML fulltext as a property of the article.
A little different in these two requests! We would prefer to fill out the fields as well as for title and abstract and add graphs/tables, without uploading a html file.
Converting a word or pdf document to html is not without defects, if it could be possible to add some fields to the landing page, it would be much more easy and accurate.
Dear ctgraham: Your site is wonderful (Form (Form) | Goethe-Lexicon of Philosophical Concepts) and probably what is required in newer forms of OJS. I am currently running a journal Archives of Surgical Research under the OJS 3.2 with Default Theme and did install your plugin to have inline HTML view on landing page but it has not worked for me. There is probably some linking issue for data harvesting from HTML upload or compatibility, I believe.
Would you like to advise in this regard.
Moreover, what tools are you using for the XML conversion for PMC submission?
Regards
Talat Waseem
Dear NateWr: Thank you for your wonderful work. Adding an HTML column in meta-data section for uploading full-text and the images, appeals me as a great idea instead of harvesting and converting from other formats, which is complex and probably unnecessary. I am currently running a journal Archives of Surgical Research under the OJS 3.2 with Default Theme and did install your plugin to have inline HTML view on landing page but it has not worked for me. What can I do in this regard?
XML generation for PMC or other indexing bodies is another issue.
Later this summer we plan on releasing a bootstrap3 subtheme compatible with 3.2 and 3.3 which implements the work we’ve done for Goethe Lexicon Philosophical Concepts publicly.
