<elocation-id>

[Melissa37]

Produces validation issues. Will not be provided by IJM content as it has page numbers and you cannot have both.

[gnott]

To overcome validation issues, when generating JSON from the XML file, I am inserting n/a as the elocationId. elocationId is required for the article to be valid, and using a placeholder seems to be an easy way around it.

The value is still displayed in some places, for which I am looking for suggestions of how to change it.

1. Top of the article page: cite as

E.g. (circled in red below)

Q. Could someone please suggest an alternative for this CITE AS area? Options include: remove it completely? change the value. Please keep in mind the JSON does not include the page numbers for any article, which would make displaying a value with pages numbers much more difficult than to remove it completely.

2. Citation downloads with elocationid

E.g. the .bib file includes this:

pages = {n/a},
citation = {eLife 2007;1:n/a},

The n/a in citation is the elocationid value

Options: Maybe these don't matter for the demo? Otherwise, the links to them could be removed from the drop down list.

3. More?

I thought the elocationId ended up in the meta tags, but I don't see any n/a in there. If anyone spots the value elsewhere you can please report it here.

[Melissa37]

@matteorichiardi would you be OK with what is displayed in the screenshot for the demo site?

There is plenty of other work we can focus on and we're just talking about the n/a value, not eLife.

I would prefer to ignore this for the demo site.

[matteorichiardi]

Hi Melissa, I am happy with setting the elocation-id to 'n/a' , for the time being.

Can you confirm that the demo site will display something like this:

CITE AS IJM 2007;1;n/a DOI: ….

?

More generally, we should have a conversation about how to cite articles at some point..... I see two possible solutions:] 1) use a progressive article number within the issue (e.g.: IJM 2007;1;1) 2) use the same progressive number as the DOI (e.g.: IJM 2007;1;00001)

It would probably be good for me to understand what is the technical issue behind the need to keep n/a for now - I need to understand a little bit more technical issues in order to provide you with more useful feedback, but if this is too complicated I am happy to simply follow your suggestions.... Matteo

On Wed, 8 May 2019 at 10:01, Melissa Harrison notifications@github.com wrote:

@matteorichiardi https://github.com/matteorichiardi would you be OK with what is displayed in the screenshot for the demo site?

There is plenty of other work we can focus on and we're just talking about the n/a value, not eLife.

I would prefer to ignore this for the demo site.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/microsimulation/ijm-xml/issues/17#issuecomment-490408448, or mute the thread https://github.com/notifications/unsubscribe-auth/ACOK4OD5HH2ICH3SXJGHSGDPUKJH7ANCNFSM4HE5ZSAA .

[Melissa37]

Thanks @matteorichiardi

The technical difficulty is that we're using Continuum and not Libero. Continuum was built for eLife only and has loads of baked in requirements that are specific to eLife.

Once you go to Libero for the live content, I see no reason with citing using the page numbers that you have for your content.

Here's an example of how a print publication will ask users to cite it. As you are using page numbers too, and not an elocation-id like eLife, this will be fine and Libero needs to support both.

Thanks!

@thewilkybarkid FYI

[matteorichiardi]

fine with me then...

On Wed, 8 May 2019 at 16:21, Melissa Harrison notifications@github.com wrote:

Thanks @matteorichiardi https://github.com/matteorichiardi

The techicial difficulty is that we're using Continuum and not Libero. Continuum was built for eLife only and has loads of baked in requirements that are specific to eLife.

Once you go to Libero for the live content, I see no reason with citing using the page numbers that you have for your content.

Here's an example of how a print publication will ask users to cite it. As you are using page numbers too, and not an elocation-id like eLife, this will be fine and Libero needs to support both. [image: Screenshot 2019-05-08 at 16 20 03] https://user-images.githubusercontent.com/6051876/57386844-27a64600-71ad-11e9-9a0f-e2a237ae0d03.png

Thanks!

@thewilkybarkid https://github.com/thewilkybarkid FYI

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/microsimulation/ijm-xml/issues/17#issuecomment-490530333, or mute the thread https://github.com/notifications/unsubscribe-auth/ACOK4OFVUSQN32FHWCPBU2LPULVXFANCNFSM4HE5ZSAA .

[Melissa37]

Great, thanks! M