Closed cthoyt closed 2 months ago
@tarleb I am a novice in latex and lua, maybe you can very quickly give me a pointer on why the combination of my lua filter and minor changes in default.crossref
aren't working properly
Very cool, thanks for this!
The "secret" for default.crossref
is that the raw strings in the metadata will not be written as-is, but will get escaped. To get the raw string, one must wrap the xml with pandoc.RawInline('html', xml)
in Lua. The CrossRef format basically uses HTML syntax for inline markup, so we use pandoc's HTML writer to produce the output.
If it doesn't work, then we could schedule a short call later this week. Just send me a mail in that case.
@tarleb I think this is done. It also appears that the JATS seems to be correctly sucking up the crossref metadata.
However, I have run make test
and am not sure what the protocol for updating the testing data is. I was able to manually check the JATS output is updated and correct, but it's not clear about the other test reference files. There appear to be non-related changes in the newly generated artifacts. Note - it appears make test
fails on the base repo, so maybe passing this isn't required.
@arfon your feedback would also be appreciated!
Super cool, thanks @cthoyt. If @tarleb is happy, I'm happy 😸
One cheeky request, once this lands, it would be excellent if you could open a PR for the example JOSS paper too 🙏 https://joss.readthedocs.io/en/latest/example_paper.html
Hey all, Amanda from ROR here. This is cool! I've added Open Journals to our list of ROR integrators at https://bit.ly/ror-integrations -- take a look and let me know if you'd like changes. cc @cthoyt
@tarleb did you see this one also?
We'll need to do a new release before it's fully live. Working on it.
Release v1.1.0 is out. I believe that @xuanxu may have to do some updates before it's used in production.
thanks @tarleb and everyone for taking a look at this and the nice feedback! looking forward to using this in my upcoming JOSS submission <4
Hi folks. I have a feeling that this change might have just broken the production pipeline for JOSS. See this error: https://github.com/openjournals/joss-papers/actions/runs/10718073016/job/29719156977#step:3:808
Error running filter /usr/local/share/***nals/data/filters/prepare-affiliations.lua:
...share/***nals/data/filters/prepare-affiliations.lua:11: attempt to index a nil value (field 'integer index')
stack traceback:
could this be because of a disconnect in the way affiliation indexes are written out? It seemed to me like Inara had thrown out the concept of using stringified lists for indexes
See potential fix in https://github.com/openjournals/inara/pull/77
I've pushed a temporary fix that ignores all errors in the new filter. Now we can do a proper fix (and add some appropriate tests).
Closes #71
This PR does the following:
ror
in each affiliation in a paper's frontmatterror
is available in PDF exportsdefault.tex
preprint.tex
default.crossref
so structured affiliations appear in Crossref metadata (with gracious help from Albert!)Note: there was a future PR after this one that fixed the ROR SVG typography in https://github.com/openjournals/inara/pull/90
Demos
Here's what the example PDF looks like now, with a clickable ROR logo that goes to the relevant page:
Here's an example of what the CrossRef XML looks like after running
make ARTICLE=example/paper.md crossref
:Here's what the JATS XML looks like:
It's in the README already, but here are the commands I ran after installing the hack font,
pandoc
, and some other stuff that already was on my computer:Notes
\protect
on both\href
and the TikZ commands to get them working in thedefault.tex
andpreprint.tex
templatesFuture Work
A few nice-to-have's (for future PRs):
orcidlink
default.context
. From what I understand, this is an experiment for Inara to adopt ConTeXt as a typesetting system instead of LaTeX since it has nicer features for PDF export. Since this hasn't been fully adopted by Inara/OJ, I won't make any changes here in this PR but will leave for later.)