Re: [jats-list] anyone validated Wiley to JATS 1.3 archiving schema? What did you do with CoverDate and publicationMeta? Thank you

["Sproat, Eliza X esproat@xxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Many, many, many thanks Debbie. And Nikos too for ideas.
E

From: Nikos Markantonatos nikos@xxxxxxxxxx
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Monday, May 29, 2023 03:12
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: [EXT] Re: [jats-list] anyone validated Wiley to JATS 1.3 archiving
schema? What did you do with CoverDate and publicationMeta? Thank you

[Actual Sender is
jats-list-return-1775-esproat=cas.org@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list
-return-1775-esproat=cas.org@xxxxxxxxxxxxxxxxxxxxxx>]

But I fear this falls short in your case. Among other slight problems, this

leaves you with no way to include the start-date.

If I am guessing correctly, the @startDate attribute serves as a mere
machine-processable value for the textual date include as the value of the
<coverDate> element. If so, then JATS1.3 also offers @iso-8601-date attribute
for this exact purpose:



<pub-date publication-format="print" date-type="cover"
iso-8601-date="2023-05-08">May 8, 2023</pub-date>

Nikos
On 5/29/23 8:17 AM, Debbie Lapeyre
dalapeyre@xxxxxxxxxxxxxxxx<mailto:dalapeyre@xxxxxxxxxxxxxxxx> wrote:

1) Cover Date



<coverDate startDate="2023-05-08">May 8, 2023</coverDate>



The JATS Tag Library suggests that <pub-date> can descrber cover dates too:

      <pub-date publication-format="print" date-type="cover" ...>

But I fear this falls short in your case. Among other slight problems, this

leaves you with no way to include the start-date.





2) Publication Metadata



<publicationMeta level="unit" type="article" position="5380"
status="forIssue">





This can be translated precisely, but verbosely. I suggest <processing-meta>

to preserve the semantics as a direct replacement for <publicationMeta>.

<processing-meta> was designed for this type of material.



It won't be pretty, but the attribute values can be captured as

<custom-meta> name/value pairs:



 <publicationMeta level="unit" type="article" position="5380"
status="forIssue">



would become:



<procssing-meta>

  <custom-meta-group>

   <custom-meta>level</meta-name>

    <meta-value>unit</meta-value>

   </custom-meta>

  </custom-meta-group>

  <custom-meta-group>

   <custom-meta>type</meta-name>

    <meta-value>article</meta-value>

   </custom-meta>

  </custom-meta-group>

  <custom-meta-group>

   <custom-meta>position</meta-name>

    <meta-value>5380</meta-value>

   </custom-meta>

  </custom-meta-group>

  <custom-meta-group>

   <custom-meta>status</meta-name>

    <meta-value>forIssue</meta-value>

   </custom-meta>

  </custom-meta-group>

</processing-meta>



--Debbie





On May 29, 2023, at 12:17 AM, Sproat, Eliza X
esproat@xxxxxxx<mailto:esproat@xxxxxxx>
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx><mailto:jats-list-service@xxxxxxxxx
berrytech.com> wrote:



Hello,







Reaching out to brighter, more experienced b



Trying to validate a Wiley article (proprietary schema) against JATS 1.3
(archiving) and wondered if anyone has ideas about what JATS element might be
a good replacement for their coverDate and publicationMeta elements.







<coverDate startDate="2023-05-08">May 8, 2023</coverDate>







<publicationMeta level="unit" type="article" position="5380"
status="forIssue">







After updates errors reduced mistakenly thought I was close, but then
boombmany more errors hatched.







Thank you for any ideas. Or if you too want to grr with me, that might be a
helpful vent too. p	







Best,



E







Confidentiality Notice: This electronic message transmission, including any
attachment(s), may contain confidential, proprietary, or privileged
information from CAS, a division of the American Chemical Society ("ACS"). If
you have received this transmission in error, be advised that any disclosure,
copying, distribution, or use of the contents of this information is strictly
prohibited. Please destroy all copies of the message and contact the sender
immediately by either replying to this message or calling 614-447-3600.



JATS-List info and archive

EasyUnsubscribe (by email)



================================================================

Deborah A Lapeyre          mailto:dalapeyre@xxxxxxxxxxxxxxxx

Mulberry Technologies, Inc.  http://www.mulberrytech.com

Rockville, MD 20851             Phone: 301-315-9631 (USA)

----------------------------------------------------------------

Mulberry Technologies: Consultancy for XML, XSLT, and Schematron

================================================================





--
[https://www.atypon.com/atypon-signature/assets/_i/atypon-logo-sig-new-2x.png
]<https://www.atypon.com/>
Nikos Markantonatos | Atypon, Greece Operations Head
Leoforos Ethnikis Antistaseos 39A, 3rd floor, Nea Ionia, 14234, Greece
office +30 211-0133003 | nikos@xxxxxxxxxx<mailto:nikos@xxxxxxxxxx>
Time zone: (GMT +2:00) Kaliningrad, South Africa
[https://www.atypon.com/atypon-signature/assets/_i/atypon-wordmark-new-2x.png
]atyponb.com
CONFIDENTIAL: This email and any attachments may contain confidential and
legally privileged information for the exclusive use of the designated
recipients. Unauthorized review, use, storage, disclosure or distribution is
prohibited. If you are not the intended recipient, contact the sender and
destroy all copies of the original message.
JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/>
EasyUnsubscribe<http://lists.mulberrytech.com/unsub/jats-list/3507682> (by
email<>)
Confidentiality Notice: This electronic message transmission, including any
attachment(s), may contain confidential, proprietary, or privileged
information from CAS, a division of the American Chemical Society ("ACS"). If
you have received this transmission in error, be advised that any disclosure,
copying, distribution, or use of the contents of this information is strictly
prohibited. Please destroy all copies of the message and contact the sender
immediately by either replying to this message or calling 614-447-3600.