Deliver xml file at the publication to DG

[eliselavy]

In order to facilitate the availability of the DOI at the publication, we go to deliver an XML's file at the same time at the pdf. The DOI with crossref will be available after 24 hours.

2 block parts:

• journal-meta
• article-meta

journal-meta: fix part ISSN: 2747-5271 + jdh

article-meta:

ppbub: to discuss to define for JDH The publication date, for the printable version, in our case equal to epub.

<pub-date pub-type="ppub">
        <day>01</day>
    <month>09</month>
    <year>2021</year>
</pub-date>

epub: to discuss to define for JDH The electronic date , when the article is published online

<pub-date pub-type="epub">
    <day>12</day>
    <month>04</month>
    <year>2022</year>
</pub-date>

<pub-date pub-type="cover-date">
    <day>01</day>
    <month>09</month>
    <year>2021</year>
</pub-date>

cover-date: to discuss to define for JDH

[eliselavy]

The Cover Date is the date an issue is planned to be published according to the production calendar. => In our case what does it mean?

Cover date = epub of the first article of the issue @inactinique ?

from here: http://www.wiki.degruyter.de/production/files/dg_xml_guidelines.xhtml#pub-date-article

[inactinique]

Why epub? Just the publication of the first article on the JDH website, I would say?

[eliselavy]

@inactinique cover-date / ppub / epub are requested information by de gruyter, theses xml fields are requested in order to generate a proper indexation of their side.

epub in the date when the article has been published on our side my question is about cover-date , it seems it will be in our case the epub of the first article on the issue?

usually cover-date is for journal working with a fix number of issue per year, working with semester, ....

[inactinique]

I would say that cover-date = the date of the publication of the first article on our website, whatever the date of publication of the first epub is.

[eliselavy]

@inactinique I forgot to mention, for each article published, a xml 's file will be generated. An article belongs to an issue, for me the cover-date is not static date == to the publication of the first article on our website but If the article belongs to issue 3, the cover-date will be set to the date of the first article published of the issue 3, no?

[inactinique]

yes, exactly.

[eliselavy]

Copyright statement: © <AUTHOR or ORGANIZATION / FUNDER>. Published by De Gruyter in cooperation with the University of Luxembourg Centre for Contemporary and Digital History. This is an Open Access article distributed under the terms of the Creative Commons Attribution License CC-BY-NC-ND https://creativecommons.org/licenses/by-nc-nd/4.0/

[eliselavy]

@lwieneke this licence statement is the one included in the article itself :

De Gruyter on his xml made the distinction between:

• copyright
• licence

<permissions>
                <copyright-statement>© 2022 Louis Autin, published by Walter de Gruyter GmbH, Berlin/Boston</copyright-statement>
                <copyright-year>2022</copyright-year>
                <copyright-holder>Louis Autin, published by Walter de Gruyter GmbH, Berlin/Boston</copyright-holder>
                <license license-type="open-access" specific-use="rights-object-archive-dnb" xlink:href="http://creativecommons.org/licenses/by-nc-nd/4.0">
                    <license-p>This work is licensed under the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.</license-p>
                </license>
            </permissions>

Exemple here:

I don't know where is this copyright-statement / copyright holder will be used.

I can ask to Bendix?

[lwieneke]

I think that the XML version of the statement is a more "machine-readable" approach. So the easiest solution would be to replace <copyright-holder>Louis Autin, published by Walter de Gruyter GmbH, Berlin/Boston</copyright-holder> with <copyright-holder>Louis Autin, published by Walter de Gruyter GmbH, Berlin/Boston in cooperation with the University of Luxembourg Centre for Contemporary and Digital History</copyright-holder>

However, we should discuss with Bendix if this is actually a good place for this addendum for the . Technically speaking it's information about the publisher but it's not related to the copyright holder itself.

[eliselavy]

About the seq

[eliselavy]

TO DEFINE need to be provided

[eliselavy]

In development

[eliselavy]

In production - mail sent to Bendix

[eliselavy]

Variable: {elocation-id}={article-system-creation-date-year} {article-counter-ID}

last 4 digits of the DOI

Concerning the elocation-id, it is defined as being comprised of the latter two elements of the article DOI, i.e. the year the article was created in the system plus the article counter. For the first article in the list you sent, this would be 20211004, see also http://www.wiki.degruyter.de/production/files/dg_variables_and_id.xhtml#elocation-id (this is the variable definition). The attribute @seq is only used for articles published in issues, but there it is required.

According to the table:

• ppub needs to be removed and issue added

<pub-date pub-type="ppub">
<day>19</day>
<month>01</month>
<year>2022</year>
</pub-date>
<pub-date pub-type="epub">
<day>19</day>
<month>01</month>
<year>2022</year>
</pub-date>
<pub-date pub-type="cover-date">
<day>19</day>
<month>01</month>
<year>2022</year>
</pub-date>

[eliselavy]

@bendix3 The changes have been deployed in production but still some question:

• I still don't know what to put for the seq <elocation-id seq="TO DEFINE">20211004</elocation-id> Example here from https://journalofdigitalhistory.org/prerendered/en/article/dg/WBqfZzfi7nHK

Now epub / cover-date / issue are in place

<pub-date pub-type="epub">
<day>19</day>
<month>01</month>
<year>2022</year>
</pub-date>
<pub-date pub-type="cover-date">
<day>18</day>
<month>10</month>
<year>2021</year>
</pub-date>
<pub-date pub-type="issue">
<day>18</day>
<month>10</month>
<year>2021</year>
</pub-date>
<volume>1</volume>
<issue>>1</issue>
<elocation-id seq="TO DEFINE">20211004</elocation-id>

[bendix3]

Hi @eliselavy, sincere apologies for the delay!

The seq attribute is only required for articles that are part of an issue. I believe the idea is to publish thematic open issues where articles are added when ready. In this case, you can give the first article the seq attribute value 1, but if you add an editorial later that is then supposed to precede the article that was published first, the value would have to be adjusted for proper presentation on degruyter.com – in case that matters.

[eliselavy]

@bendix3 a new version has been deployed in order to integrate the seq editorial is always on seq=1