As usual, speechless! Awesome work. I activated and it works great. I am planning to show this as HTML directly, since few side stuff like how to cite does not work in XML.
Somehow, the abstract page doesnt have the references clickable (like when you click on reference  or  and it takes you to the reference) in OldgregG after installing this.
It started working once I removed this plugin
Yep, it is possible. When JATS Parser plugin is turned on, Old Gregg theme starts to use the JATSParser lib from this plugin, which has newer version. Some changes are associated with links parsing. Particularly, this part of a template should be rewritten: https://github.com/Vitaliy-1/oldGregg/blob/master/templates/frontend/parser/text.tpl#L23-L36
I am planning to update Old Gregg theme so it stay inline with update JATSParser library in September-October. It should move away from using Smarty templates as injecting full article’s HTML is much more easier approach.
Cool. Will await. I already started adding my modifications. Lol. Now have disabled it.
Hi Vitaliy, great work! It would be great to get a step by step example.
- how to install the jats xml to html / pdf plug in.
- how to modify the theme to get the display in a page with left / right columns
- a word 2016 document that is based on a typical template that journals would use to get authors to submit their work.
- the word 2016 document converted to jats xml
- the displayed html page
- the displayed pdf page
For those of us that are working through this step by step it would be very useful to get more examples to see if our existing journal word 2016 templates will work before we spend time to set this up.
- The installation process is described on the plugin’s Github page. It’s not different from such for other OJS 3 plugins: https://github.com/Vitaliy-1/JATSParserPlugin
- And what are you trying to accomplish? On the first glance, it looks like a work for a developer. The plugin displays JATS XML almost the same way as all other pages are displayed in OJS. So, customizing shouldn’t be harder than other parts of the system (and should be easier compared to Lens Viewer).
- It depends on how you perform the transformation process. And it can be done not only from DOCX format.
- The plugin hasn’t such aim as DOCX to JATS XML transformation. The possible options are presented in this post: Who is who in JATS? (2018)
- The example is included in the first thread’s post: http://ojsdemo.e-medjournal.com/index.php/jatsparser/article/view/8/8
- The example is also included in the first post: http://ojsdemo.e-medjournal.com/index.php/jatsparser/article/view/8/8?download=pdf
The plugin transforms JATS into HTML and PDF automatically. HTML and PDF are immediately injected into the page, there are no intermediates in this process. You can always ask additional question here or on the plugin’s Github page if you’d stuck on something specific.
Q3 is a key issue. Can you please provide a link to the word document that you used in the examples Q5 and Q6?
I would be greatful (and happy to pay or donate) if I could email a word document that is typical of what our journal uses and for this document to be converted to JATS XML and displayed as html and PDF. What I’m trying to do is to work out if this will work for us before I get custom pages made to have the html and PDF in the pages (with the normal OJS columns included)
I haven’t used Word document here. Only JATS XML. Moreover, I usually use Libreoffice or Google Docs as text editors.
If you asking about the journal where I’m working and an editor, it is DOCX2JATS converter: https://github.com/Vitaliy-1/DOCX2JATS
You can also find DOCX examples there. But the produced JATS XML is not ideal and requires additional manual correction. I’m working right now on a better version.
But once again, it is not relates to JATS Parser Plugin functionality.
Dear sir it is possible Displays html on article detail page like old jats parser
Thank you again, I have the JATSParser installed. The setting of JATSParser does load. What does the setting do?
The default behavior is to retrieve References from JATS XML and if there aren’t any, retrieve them from OJS (that was added as article meta and parsed by OJS). In the settings you can force to use reference list from JATS XML or OJS. The latter is good for those, who don’t want to spend time and and form JATS XML with references or who tend to use other the AMA citation style.
What else do I need to have this JATSParser V2 works. I have got the JATSparser install and enabled. In order to use it do I have to have another plugin installed? How can I get that nice full-text /HTML/XMLin the article landing page.
Plugin renders XML and outputs the result on the XML galley page. You need to upload XML to the production stage and, after publishing go that XML galley page.
Thank you. A PMC tagged xml file would work? or it has to be just JATS xml?
The plugin doesn’t provide any additional checks for the XML. As long as it has
/article/body and all standard elements inside all should be fine. But doesn’t support all JATS standard tags and their combinations.
I suppose, PMC tagged XML = JATS XML
You can see an example that we use here: https://github.com/Vitaliy-1/JATSParserPlugin/blob/master/example.xml
Keep in mind that metadata is displayed actually from OJS, not JATS XML, so, basically, are not required. References can also come from OJS, but by the default - from JATS XML.
I try to install this plugin and I haven’t succeeded yet. I noticed some differences. JATS Parser v2.0 looks like a theme not a plugin. Because as shown in the example link this doesn’t look like oldGregg theme and in the link after index.php jatsparser comes. “index.php/jatsparser”
I want to ask this. Also I use the oldGregg theme right now. After install this plugin is there an adjustment problem?
I decompressed the jatsParser 2.0 file and copy to plugins/generic folder. This is error message. What is the problem?
I think that this problem is due to the differences between old and new OldGreggThemePlugin.inc files.
Old plugin seems like this:
New plugin seems like this:
How can I solve this problem?
Now my journal website is off. May you help me about this urgently?
Thanks in advance
I don’t see any syntax related errors in the code. Can you confirm that you are using PHP 7.1+?